Custom 503 service unavailable not working

sarunazs

New member
Joined
Jul 14, 2021
Messages
4
Hi, i am trying to setup custom 503 page on my website which runs on Laravel framework, but it doesnt fire my custom template on live server. Works fine on local server which doesnt have DirectAdmin. I get:

Service Unavailable​

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

I have checked DirectAdmin custom error pages templates and there was none created for 503. In default folder too.
DirectAdmin runs on nginx_apache.

I think its some sort of default apache or nginx template. How can i disable those or change?
 
docroot home settings?!?

Mostly probelms, sometimes php config settings, rights, mysql versions en yes no strict ...

Wher to find look i don't know
 
As far as I know it's not possible to create a custom 503 page, it's integrated in Apache.

Look at it like this. The 503 page is shown when your site is down for some reason.
So if your site is down, how do you expect the browser to be able to load your custom 503 page?
 
As far as I know it's not possible to create a custom 503 page, it's integrated in Apache.

Look at it like this. The 503 page is shown when your site is down for some reason.
So if your site is down, how do you expect the browser to be able to load your custom 503 page?
Well thing is in Laravel when you turn on maintenance mode response code is 503. And i dont think it cant be changed its some sort of override issue i think as on my local apache server without directadmin everything works perfectly so it must be some sort of apache setting. I know you can set in apache ErrorDocument 503 /path/to_file.html and it will work but thats not the case it should be possible to avoid default or that custom error page set in apache.
 
Well thing is in Laravel when you turn on maintenance mode response code is 503. And i dont think it cant be changed its some sort of override issue i think as on my local apache server without directadmin everything works perfectly so it must be some sort of apache setting. I know you can set in apache ErrorDocument 503 /path/to_file.html and it will work but thats not the case it should be possible to avoid default or that custom error page set in apache.






for subdomains ... https://feedback.directadmin.com/b/feature-requests/custom-document-root-for-domains-and-subdomains/

For old apache itself was http://httpd.apache.org/docs/1.3/misc/custom_errordocs.html for 2.x i don't know
 
Last edited:






for subdomains ... https://feedback.directadmin.com/b/feature-requests/custom-document-root-for-domains-and-subdomains/

For old apache itself was http://httpd.apache.org/docs/1.3/misc/custom_errordocs.html for 2.x i don't know
if i wrote about that that is not solution for this issue thx for the effort. i dont need custom error page i need that default one would not be forced, like on simple local apache server where i do get the page i need. sorry but all of your links are out of topic
 
Back
Top