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

    Resolved The timeout specified has expired: AH01075: Error dispatching request to : - without URL in my logs - Error 502 - since php 8.2.13 - randomly

    Glad to hear that! ) Yes, I think #journalctl will help. I had a similar issue recently caused by Actomic Mod_Security. The Apache stopped working when the AUM updating the ruleset but your issue might be totally different.
  2. WebHostingAce

    Resolved Magento 2.4.2, Varnish in Docker and Getting 501 PURGE errors in NGINX

    Final words. You sound like ... [redacted]
  3. WebHostingAce

    Resolved Magento 2.4.2, Varnish in Docker and Getting 501 PURGE errors in NGINX

    Which part you are confused about? a one click away? So you are complain about one mistake I have made for the reply? This forum replies are not paid work! Also it should have worked without the 'http_cache_hosts" Just learn how to ask for support from the community in a forum. Dont talk...
  4. WebHostingAce

    Resolved Magento 2.4.2, Varnish in Docker and Getting 501 PURGE errors in NGINX

    This is completely wrong! Why would you request NGINX to PURGE /? This is nothing to do with NGINX. If you followed my instructions in the "Input" thread regarding the Varnish Docker for Magento 2, You do not have to specify http_cache_hosts in env.php. In my instructions, I have mentioned it...
  5. WebHostingAce

    Issue Enabling of HTTP/2 whilst LiteSpeed was in use has broken things

    By looking at this Litespeed installation guide - Configuring LiteSpeed Web Server with Plesk | LiteSpeed Documentation As Peter mentioned, I also agree It would be ideal to reinstall the server and restore from a backup. You can try to change the PHP Handlers to FPM etc.
  6. WebHostingAce

    Issue Enabling of HTTP/2 whilst LiteSpeed was in use has broken things

    How about if you try to disable HTTP/2, #plesk bin http2_pref disable
  7. WebHostingAce

    Resolved Move all mail to another disk/partition

    https://support.plesk.com/hc/en-us/articles/12377869111319--How-to-change-default-location-of-mailboxes-in-Plesk-for-Linux
  8. WebHostingAce

    Issue plesk does Server down?

    What is the actual error when you are trying to login to the server?
  9. WebHostingAce

    Issue Enabling of HTTP/2 whilst LiteSpeed was in use has broken things

    # plesk repair web domainname.tld should have fixed this issue as this command re-writes the default configuration files for the vhost using Apache and NGINX. Do you have any additional settings in Additional Apache directives or Additional nginx directives? Also please check the .htacess file.
  10. WebHostingAce

    Resolved Magento 2.4.2, Varnish in Docker and Getting 501 PURGE errors in NGINX

    In this case what is the purpose of call a vhost by IP? This is why use different ports. Actually its the Matches the PURGE request. I can confirm that instructions should work as it is working across many of our Magento 2 servers. Yes, It works with Plesk with a single IP.
  11. WebHostingAce

    Question Server Error 500 Plesk\Exception\Database

    https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-22-04
  12. WebHostingAce

    Resolved Magento 2.4.2, Varnish in Docker and Getting 501 PURGE errors in NGINX

    Please see - Instruction - How to Install Magento 2.4 on Plesk
  13. WebHostingAce

    Issue Enabling of HTTP/2 whilst LiteSpeed was in use has broken things

    Did you run? # plesk repair web domainname.tld Also what is the error now?
  14. WebHostingAce

    Resolved SUPER WEIRD port issue

    Eg - /etc/host 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 127.0.0.1 guest ::1 guest 127.0.0.1 SERVER.B.DOMAIN DOMAINNAME ::1 SERVER.B.DOMAIN DOMAINNAME 172.17.0.3...
  15. WebHostingAce

    Resolved SUPER WEIRD port issue

    Usually this is 127.0.0.1 (localhost)
  16. WebHostingAce

    Resolved SUPER WEIRD port issue

    No problem at all. Glad to hear your issue is solved.
  17. WebHostingAce

    Question scheduled task ERROR |

    Sorry, I have misunderstood issue. This is the Plesk extension/composer not related to the Wordpress.
  18. WebHostingAce

    Question scheduled task ERROR |

    Please go to Wordpress Toolkit and Detach this domain.
  19. WebHostingAce

    Issue Enabling of HTTP/2 whilst LiteSpeed was in use has broken things

    Please try, If you have completely removed the LiteSpeed, have you re-enabled the NGINX? Once re-enabled the NGINX, Please restart both NGINX, Apache and any FPM services in use under Tools & Setting > Services Management. Then, # plesk repair web domainname.tld
  20. WebHostingAce

    Question Server Error 500 Plesk\Exception\Database

    Please try to add under [mysqld] in my.cnf, innodb_buffer_pool_size = 256M and restart the MariaDB.
Back
Top