• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Custom error document - 414 - doesn't work

goobliata

New Pleskian
I've set up custom error documents, and am testing a few. They mostly work but for 414 - Request URI too long uses the default Apache document. I've tested this by going to <mydomain>/<1 million letters> using Chrome (some other browsers don't allow that many characters.)
 
Hello, can you provide an example how you configured custom error document (part of config file).
Can you confirm other error codes work as expected and you experience problem only with 414 error code?
 
Hello. I haven't edited any config files directly, I just ticked the checkbox under Hosting Settings (if you can tell me which config file I can check it.)

I've tested a few other error codes and they work as expected. I'm not sure how to trigger all of them, but the only one that I tested that failed was the 414.

Thanks!
 
Dear @goobliata
I confirm it's a bug in error document name, thanks for a report.
You can fix it manually (as a workaround) by open /var/www/vhosts/<your domain>/error_docs and copy file request-uri_too_long.html to request_uri_too_long.html
Copying will prevent failure when fix will be released.
 
Back
Top