• 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. J

    Question Change website listening port

    Unfortunately it's not exactly what I meant: I want to keep the 80/443 for all my sites except for one of them for which I want to set 1111/1112 for example. I could change it in /var/www/vhosts/system/<mydomain>/conf/nginx.conf but the configuration will be overwriten sooner or later.
  2. J

    Question Change website listening port

    Hi all, I want to change the http port for only one of my website. Example : I want to access to one website with http(s)://mywebsite:9999 instead of http(s)://mywebsite I know I can change manually the nginx config files, but that kind of update is not permanent for the config file is...
  3. J

    Update 12.5.30 #23 Error

    Got the same issue today. Symptoms : bad gateway while trying to access to panel (xxx:8443), unbelievable usage for services & cpu (http at 600%; cpu at 8350274.5%), and apt-get update/upgrade blocked. Now it looks better, except for CPU usage still in the sky.
  4. J

    SSL POODLE / SSLv3 bug

    The solution is here : http://talk.plesk.com/threads/new-plesk-12-install-has-poodle-unpatched.331094/#post-772948
  5. J

    Resolved DNS Problem (BIND) with CentOs 6.x

    Plesk-bind removes bind-chroot who is needed to start named service. So you can start named as a service by removing plesk-bind package and installing bind-chroot, but it's only a workaround.
  6. J

    Resolved DNS Problem (BIND) with CentOs 6.x

    Seems to be a conflict bw plesk-bind and bind-chroot. I'm looking for further information.
  7. J

    Resolved DNS Problem (BIND) with CentOs 6.x

    Well as to me, it's a fresh CentOS 6.4 install too and a 11.5.30 Plesk installation.
  8. J

    Resolved DNS Problem (BIND) with CentOs 6.x

    Here are the results :
  9. J

    Resolved DNS Problem (BIND) with CentOs 6.x

    When I start named manually with the right parameters, it seems to work : I'm looking further but seems to be a config/parameter matter.
  10. J

    Resolved DNS Problem (BIND) with CentOs 6.x

    Hi, same problem :
Back
Top