Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

How to enable custom error pages for a domain in Plesk

Follow

Comments

5 comments

  • Avatar
    Tony

    It'd be nice if these nginx custom error settings were automatic when the custom error messages box was checked in plesk. We've determined the nginx 502 error page is the one customers see when plesk changes are made to domains requiring rebuilding apache/nginx config and restarting...   It would be nice if we could easily globally set a prettier custom error page as a default server wide.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Tony,

    Thank you for sharing the idea.

    I have created a feature-suggestion: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/36231586-add-server-wide-custom-error-pages-configuration-v?

    If it becomes popular, it will be implemented. Feel free to vote for it.

    0
    Comment actions Permalink
  • Avatar
    Kathy Sechrist

    I followed the directions for the custom php error pages. It's showing the page, but without the php includes. Why?

    0
    Comment actions Permalink
  • Avatar
    julian bonpland mignaquy

    Hi Kathy Sechrist could you show us an example of how it looks and what is missing?

    0
    Comment actions Permalink
  • Avatar
    Motaz

    I followed the steps but it's not working with me, still seeing the default chrome page for 500 errors, also helpful to note that I don't have any custom .htaccess files on the root directory, what else might be causing the issue? could you please assist? thank you.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request