Forum Discussion
Agathe_309970
Altocumulus
AltocumulusMaintenance page cannot be displayed
Hello,
I use the F5 BIG-IP as a reverse proxy. I have one entry which works fine. With this URL, we arrive on the right application. There is a NGINX between the F5 and the application server. This NGINX redirect the request to the right Web server. All works without problem in general.
When there is a production deployment, they use this NGINX to redirect to a maintenance page and they send a 503 error.
The problem is that this maintenance page doesn't work. In fact, I have all the HTTP request on the F5 (with the 503 errors) but the page cannot be displayed.
Before, they are on another reverse proxy and it was working without problem. I am not sure that the problem comes from the F5 configuration but I am not an expert in F5 so I prefere verify. Indeed, we checked all the configuration on all the equipment (servers, NGINX, F5, ...) and we don't find the problem. I have no more idea so I ask here if you have a solution.
Thank a lot in advance for your help.
Best regards,
Agathe
Leonardo_SouzaCirrocumulus
You need to provide the relevant part of the F5 configuration. How is the maintenance page configured in the F5?
Agathe_309970Thank you for your response.
This maintenance page is managed by the NGINX and not by the F5. Maybe there is something to do to allow this maintenance page (there is nothing configured on the F5 for the maintenance page). I think that the F5 can block this page because of the 503 error received from the server but I am really not sure.
amintejCirrus
Hello, NGINX is configured inside a pool in F5 ? Could you clarify the setup ? Maybe F5 marks down the nginx when maintenance page is enabled due to http monitor configured. What error do you recive when maintenance page is enabled ? TCP timeout = Please, note you can enable also maintenance page in F5.
Stanislas_Piro2Cumulonimbus
Hi,
if you want to allow NGINX to reply when there application is down, you have to remove all monitors on F5 except tcp or http. don't assign a monitor checking the application behind the NGINX!
if the monitor down, the F5 will not send request to NGINX.