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

  1. A

    Issue All Websites Down and Plesk Panel Not Reachable After Restarting Nginx. Have SSH Access, Plesk Repair Not Working

    Please disregard my message about wanting to edit the file directly, I am more interested in restoring it to how it needs to run properly for plesk.. thank you
  2. A

    Issue All Websites Down and Plesk Panel Not Reachable After Restarting Nginx. Have SSH Access, Plesk Repair Not Working

    root@dazzling-bell:/etc/nginx# ss -tulpn | grep nginx does not return nginx listening on ports What is the file that I would need to edit to re-add nginx configuration for listening to ports? i understand it is different than standard nginx conf. Thanks so much
  3. A

    Issue All Websites Down and Plesk Panel Not Reachable After Restarting Nginx. Have SSH Access, Plesk Repair Not Working

    It is working and so is apache, php-fpm, etc
  4. A

    Issue All Websites Down and Plesk Panel Not Reachable After Restarting Nginx. Have SSH Access, Plesk Repair Not Working

    AWS security group inbound rules are allowed and ACL is allowing Web server is not listening on port 80 or 443 since restart Firewall is disabled
  5. A

    Issue All Websites Down and Plesk Panel Not Reachable After Restarting Nginx. Have SSH Access, Plesk Repair Not Working

    See attached
  6. A

    Issue All Websites Down and Plesk Panel Not Reachable After Restarting Nginx. Have SSH Access, Plesk Repair Not Working

    Have gone through plesk repair many times over and it says all is OK.
  7. A

    Issue All Websites Down and Plesk Panel Not Reachable After Restarting Nginx. Have SSH Access, Plesk Repair Not Working

    I have my plesk panel set up on a domain name, and it does not connect using the .com on port 80/443. However it does work on port 8443 and I am able to access the plesk panel.
  8. A

    Issue All Websites Down and Plesk Panel Not Reachable After Restarting Nginx. Have SSH Access, Plesk Repair Not Working

    Ah, no , the site doesnt work on mobile. I cannot access, and my Domains page shows broken websites. I had a somewhat experienced sysadmin user try to find the solution for about two hours and was unable to so far. he believes it is a "plesk networking issue"
  9. A

    Issue All Websites Down and Plesk Panel Not Reachable After Restarting Nginx. Have SSH Access, Plesk Repair Not Working

    Thank you for your response, not sure exactly what you mean. Are you referring to my personal home IP address? here is the output of that: root@dazzling-bell:~# grep ********* /var/log/fail2ban.log 2023-09-25 11:53:01,152 fail2ban.filter [1008]: INFO [plesk-wordpress] Found...
  10. A

    Issue All Websites Down and Plesk Panel Not Reachable After Restarting Nginx. Have SSH Access, Plesk Repair Not Working

    Was using the SSH Terminal extension briefly as I could not connect directly, tested nginx with "nginx -t" and restarted nginx with "service nginx restart". This closed my connection to the SSH but now the Plesk panel is unavailable, along with my websites. I restarted my VPS and SSH'd in and...
See more
Back
Top