• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. L

    Issue SSL Certificate for emails

    Are the services still listening on the correct ports? You should see something like this .. # lsof -i :587 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME master 14357 root 106u IPv4 345192 0t0 TCP *:submission (LISTEN) # lsof -i :993 COMMAND PID USER FD TYPE DEVICE...
  2. L

    Issue Migrator ...

    Sorry, you don't access the server through the private IP. You have to use the public IP or connect to localhost. For further information see: VServer/en – Hetzner DokuWiki "With the CX models the IPv4 address of the virtual server is a private IP, which is configured 1:1 via NAT on the public...
  3. L

    Issue Migrator ...

    Thank you very much for your reply, but no, this isn't a firewall problem. As I have said SSH works perfectly from either side. The problem is obviously this: +|2018-02-08_15:53:03,452|I|MT|plesk.connections.target_connections|||Target Plesk host: 172.31.1.100 "Target Plesk" is either...
  4. L

    Issue Migrator ...

    Hi everyone! When trying to start a migration from a freshly installed Centos 7.4 Server with Onyx 17.5.3 I always get the error: Failed to connect to target Plesk Server by Plesk API: <urlopen error [Errno 110] Connection timed out> The debug.log states...
  5. L

    Issue Can't process products.inf3 404 File Not Found

    Btw, the issue seems to be "solved" here. One of my servers did indeed update plesk without errors. It was the only box with an entry for autoinstall.plesk.com in /etc/hosts. I simply used it temporarily for my others boxes and they all updated fine. This is on five different locations...
  6. L

    Issue Can't process products.inf3 404 File Not Found

    Same error here on SEVEARL plesk driven servers where updates fail for several days (or is it weeks?!). The requested output (even though it is clearly not a resolving issue since it undoubtedly says 404 file not found): wget http://autoinstall.plesk.com/products.inf3 --2016-10-27 11:55:27--...
  7. L

    /var/log/httpd/access_log logs local IP addresses not remote ones

    Hi @AlL! Currently I have two Plesk 12 Linux servers running. One of them uses apache only (a virtual server), the other (a bare metal server) has been "autoinstalled" and uses apache and nginx. Unfortunately the second server has a major security risk, since all attacks on the default domains...
View older results
Back
Top