• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by JanikoG

  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 : https://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.
Back
Top