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

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.
See more
Back
Top