• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

About Custom Error Pages with css and js

Victor-SP

New Pleskian
Hello.
My server is an CentOs 6 with Plesk 12.

I designed a custom error page that includes a folder css, folder js and folder img another. But it does not work because do not load the files in those folders. I think it might be a problem of paths to the directories. It's posible?

Thaks so much
 
Hello,

1. apache will start to use custom error documents after several hours, when it is restarted during daily maintanence procedure.
2. check Error.log an you will see where apache looks for your custom files. Seems you use wrong path to your css,js and img folder in your custom error pages. Try to access files it that folders directly. Type in address bar http://your.domain.com/error_docs/img/img.jpg and you should see the picture if it is there.
 
Hello,

1. apache will start to use custom error documents after several hours, when it is restarted during daily maintanence procedure.
2. check Error.log an you will see where apache looks for your custom files. Seems you use wrong path to your css,js and img folder in your custom error pages. Try to access files it that folders directly. Type in address bar http://your.domain.com/error_docs/img/img.jpg and you should see the picture if it is there.
Hi smi
Thank you.
I think I've seen the problem: is with the paths. I was using relative paths as this <script src="js/test.js"></script>". I am now trying to fix with absolute paths such as "http://your.domain.com/error_docs/js/test.js"

Thx!!
 
Back
Top