• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Recent content by Bobby_Atlas

  1. B

    Upgrade problems

    Hi there, is there any update on my problem? I ask because its production server and i have to fix it asap...
  2. B

    Upgrade problems

    I also checked ngnix conf: server.conf: include "/etc/nginx/plesk.conf.d/ip_default/*.conf"; server { listen 94.242.222.199:80; location / { proxy_pass http://94.242.222.199:7080; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr...
  3. B

    Upgrade problems

    Here is attached logs. NGINX error.log: 2014/06/23 03:45:23 [emerg] 1242#0: open() "/var/www/vhosts/system/fiber-way.ru/logs/proxy_access_ssl_log" failed (13: Permission denied) 2014/06/23 03:45:23 [emerg] 1242#0: open() "/var/www/vhosts/system/fiber-way.ru/logs/proxy_error_log" failed...
  4. B

    Upgrade problems

    I see strange things there, but have no idea what is it: [root@LU1 pp12.0.18-bootstrapper]# ./bootstrapper.sh repair Started bootstrapper repair procedure. This may take a while. Certain actions may be skipped if not applicable. -- Warning: Skipping the data of table mysql.event...
  5. B

    Upgrade problems

    Hi Igor, yes, i did it, it show me that repair is finished, but no luck - it still doesn't work: 404 not found (nginx)
  6. B

    Upgrade problems

    Hi Scott I already rebooted server few times and restarted plesk processes also It doesn't help. What i can dig else to fix it?
  7. B

    Upgrade problems

    Hello all, i was upgraded my plesk on centos 6.4 from 11.5 to 12 version. After that i'm trying to access this by https://xxx:8443 and getting error 404 not found. What should i do to fix this issue? During upgrade was no errors so i have no idea whats going on.
Back
Top