• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Recent content by AaronClifford

  1. A

    Panel version 11.5.30 Update (could not bind to address 0.0.0.0:80)

    Any idea on the post above this Nikolay?
  2. A

    Panel version 11.5.30 Update (could not bind to address 0.0.0.0:80)

    It's these, having regular downtimes for 1m up to 10m and they correspond with the above errors. Any ideas?
  3. A

    Panel version 11.5.30 Update (could not bind to address 0.0.0.0:80)

    I restarted the server and didn't have the issue for around 11 hours, now it just happened again, the sites stopped working and when I restarted httpd I got the same error as above, Looked at the link you sent and this is the response I got: Is this correct?
  4. A

    Panel version 11.5.30 Update (could not bind to address 0.0.0.0:80)

    I upgraded to Panel version 11.5.30 Update #2 today and now six times my sites have become unaccessible. I then have to restart httpd to get it working but get this error five or six times before it starts again: Any ideas why this might be happening?
See more
Back
Top