• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Search results

  1. D

    Resolved SUPER WEIRD port issue

    I can't mark this topic or a post as resolved btw.
  2. D

    Resolved SUPER WEIRD port issue

    That's the first line- looks like the installer from my hoster also adds that second line.
  3. D

    Resolved SUPER WEIRD port issue

    Oh my god it was in the /etc/hosts file: ### Hetzner Online GmbH installimage 127.0.0.1 localhost.localdomain localhost TEMPORARY.IP.ADDRESS SERVER.B.DOMAIN DOMAINNAME ::1 localhost.localdomain localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix...
  4. D

    Resolved SUPER WEIRD port issue

    My god FINALLY a hint, thank you so much! Within Plesk in "Tools & Settings > IP Addresses" there's an ipv4 address and an ipv6 address- which are both correct. I've also clicked on "Reread IP" and it seems fine. I've double checked the 01-netcfg.yaml and the other 10-plesk.yaml file and the...
  5. D

    Resolved SUPER WEIRD port issue

    @WebHostingAce (Un)fortunately no use of a CDN here. It was just an in-place replacement of the old server and keeping the old IP address. Maybe it'll help if I say what exactly we did: - We rented temporarily a server (which is Server B) in this case, to replace Server A - We've installed on...
  6. D

    Resolved SUPER WEIRD port issue

    (Un)fortunately no use of a CDN here. It was just an in-place replacement of the old server and keeping the old IP address. We've used the plesk migrator to migrate most of the files after a fresh install of the latest Ubuntu LTS version and installing Plesk over CLI with the one click...
  7. D

    Resolved SUPER WEIRD port issue

    As a last resorted I have contacted our Hoster (Hetzner Germany) for this, just in case there's something fishy going on in the background, but unfortunately that's not the case either. Feedback / Help very much appreciated.
  8. D

    Resolved SUPER WEIRD port issue

    I might be wrong about the PHP part- trying out telnet from the server itself on every common port besides 8080 also yields a connection refused. I've compared all kinds of settings from Server B with our other currently running Server C and couldn't find anything. I'm officially out of ideas now :)
  9. D

    Resolved SUPER WEIRD port issue

    After more tinkering: Port 465 is clearly open and I can send mails externally. I've come to the conclusion that perhaps for some reason PHP scripts are not allowed to send mails? I've used PHPMailer to try to send mails from Server B itself and the used same script from Server C (over...
  10. D

    Resolved SUPER WEIRD port issue

    And my latest insight: I ran a PHP testscript from both server B and server C about server B which look sas follows: <?php ini_set('max_execution_time', 0); ini_set('memory_limit', -1); $host = 'SERVER.B.DOMAIN'; $ports = array(21, 25, 80, 81, 110, 143, 443, 465, 587, 2525, 3306); foreach...
  11. D

    Resolved SUPER WEIRD port issue

    I cannot find any errors on any logs except for the shopsystem log: { "exception": "[object] (Zend_Mail_Protocol_Exception(code: 0): Connection refused at /engine/Library/Zend/Mail/Protocol/Abstract.php:273)" } This obviously works if I choose any other mail from any other server, so the...
  12. D

    Resolved SUPER WEIRD port issue

    Thanks for the quick reply and sorry for the late reply from my side- we had to switch to scenario 3 (from the image below) temporarily because of the current workload and I had no time to get back to you guys here. Take a look at this: I hope this is clear enough. The IP-addresses are of...
  13. D

    Resolved SUPER WEIRD port issue

    Running netstat -tulpn | grep LISTEN | grep 465 yields: So the ports are obviously open- but not for the applications on that very same server- somehow?
  14. D

    Resolved SUPER WEIRD port issue

    Hi there, I've migrated our old server to a new one, fresh install and all, but I've encountered an issue you guys hopefully will be able to figure out: My websites cannot send mail over SMTP on the same server- I always get a timeout. If I use an external SMTP server it works- what is weird...
  15. D

    Question ClamAV blocking .doc attachements?

    Hi there, ever since reinstalling Plesk Premium Mail our clients can no longer send .doc attachements- I have found them in quarantine in the Plesk E-Mail Security settings with the reason "INFECTED, message contains virus: YARA.docx_macro.UNOFFICIAL". However these documents do not contain a...
  16. D

    Resolved Seafile running- but "Failed to login: Internal server error" when trying to log in

    Hi Peter, yes, sadly I had to do something quickly because people (obviously) wanted their access back asap. All I can say is, that besides regular Plesk updates, there have been lately no manual changes in any configuration files on the server. But yes, removing and re-adding Plesk Premium...
  17. D

    Resolved Seafile running- but "Failed to login: Internal server error" when trying to log in

    Uninstalling Plesk Premium Email has immediately fixed the issue. Attempting to install Plesk Premium Email again now. I have managed to reinstall everything successfully, thank god nothing broke in the process. No idea what caused this, but I could safely uninstall and reinstall Plesk Premium...
  18. D

    Resolved Seafile running- but "Failed to login: Internal server error" when trying to log in

    Actually scratch everything, I've deleted both log files, restarted the services, and got fresh files with current data: seafile.log [08/16/23 16:16:01] socket file exists, delete it anyway [08/16/23 16:16:02] http-server.c(181): fileserver: worker_threads = 10 [08/16/23 16:16:02]...
  19. D

    Resolved Seafile running- but "Failed to login: Internal server error" when trying to log in

    Reinstalling the extension would maybe help, but I see no option for that within Plesk- is there a workaround for this?
  20. D

    Resolved Seafile running- but "Failed to login: Internal server error" when trying to log in

    Hi Peter, thanks for the quick reply- here are the results of both seahub.log and seafile.log where it seems a bit fishy: seafile.log: [02/18/22 17:14:47] http-server.c(181): fileserver: worker_threads = 10 [02/18/22 17:14:47] http-server.c(196): fileserver: fixed_block_size = 8388608...
Back
Top