Style the nginx-side error message

[Paul Everitt]

Yesterday we were getting gateway timeout errors as a nice, white screen. That freaks out OSF. Would be nice to have styled error messages as we did before.

[Paul Everitt (paul-agendaless)]

We need to provide a page where we control the styling, that can be served statically by nginx. We did this for Apache/modwsgi but that ran on the same server. We'll need to negotiate a way with gocept to have nginx have access to a directory that we control via updates.

[Chris Rossi (chris-archimedeanco)]

I've created a standalone web page for gocept to use to substitute the normal 502 - Bad Gateway page. Assigning to Zagy for deployment.

[Christian Zagrodnick (zagy)]

Created a support ticket [gocept #77806] for us internally. Will update you here though.

[Paul Everitt (paul-agendaless)]

I forgot to mention, we had such a thing in our source tree:

src/karl/karl/views/static/down_for_maintenance.html

--Paul

On Jun 29, 2011, at 2:54 PM, Chris Rossi wrote:

> I've created a standalone web page for gocept to use to substitute the
> normal 502 - Bad Gateway page. Assigning to Zagy for deployment.
>
> ** Attachment added: "sitedown.tar.gz"
> https://bugs.launchpad.net/karl3/+bug/778165/+attachment/2184662/+files/sitedown.tar.gz
>
> ** Changed in: karl3
> Status: New => In Progress
>
> ** Changed in: karl3
> Assignee: Chris Rossi (chris-archimedeanco) => Christian Zagrodnick (zagy)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/778165
>
> Title:
> Style the nginx-side error message
>
> Status in KARL3:
> In Progress
>
> Bug description:
> Yesterday we were getting gateway timeout errors as a nice, white
> screen. That freaks out OSF. Would be nice to have styled error
> messages as we did before.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/778165/+subscriptions

[Christian Zagrodnick (zagy)]

It's in place now. See it at https://karl.soros.org/sitedown_gocept/maintenance.html

(It's sitedown_gocept to avoid name clashes with KARL)

[Paul Everitt (paul-agendaless)]

Christian, I think we have the "down for maintenance" covered already. We need something that covers 40* and 50* messages like gateway timeout, that aren't handled by KARL now. Perhaps Robert can give a better example.

[Christian Zagrodnick (zagy)]

That's wat it is now. For 502 and 503 currently. If you want more error codes, let me know. 40x is questionable, as karl has a decent 404 page for instance.

[Christian Zagrodnick (zagy)]

Oh btw: you can test that on karlstaging

[Paul Everitt (paul-agendaless)]

Ok, I agree then that this covers it.

[Robert Marianski (rmarianski)]

I think it might make sense to have something for 504 errors too. What is the nginx timeout for requests, 30 seconds? Maybe we should use a different page that is exactly like maintenance.html but has some different text there saying something like the request took too long, and to try the request again.