The Wiki Is Back Up

[z929669]

We know the wiki has been down for a couple of days now, and I apologize for the inconvenience. Our server administrator is AFK for the first time, and I have not been in a position to resolve myself until just a few minutes ago.

 

We will be making some changes for the better as a result. Please stay tuned, and thank you all for your continued support!

[silverbluemoon]

I am still showing it as down with "504 Gateway Time-out" and "Error 503 Backend fetch failed."

[TheLostExecutable]

I am still showing it as down with "504 Gateway Time-out" and "Error 503 Backend fetch failed."

Getting same issues, 504 and 503.

[silverbluemoon]

It is up now. Thank you.

[Mator]

Anyone who still gets error messages should try connecting from a different browser/device to verify it's not a caching issue.

 

EDIT: Down for me.  It seems like it's intermittently up/down.

[Stoltverd]

I bought a new PC yesterday, and visited STEP only today. 5 minutes ago in fact. It's down for me using chrome, firefox and edge.
Chrome shows me error 504, firefox error 502 and edge, error 504.

[Stoltverd]

The wiki is now UP for me too

[Redferne]

It's still down for me.

504 on Chrome, 503 on EDGE.

 

[z929669]

Please see my recent post on wiki issues

[sgensemer42]

I get these errors in Internet Explorer ver. 11 (Windows 7 Pro):

504 Gateway Time-out - (https://wiki.step-project.com/STEP:2.2.9.2) opening up in a new tab

Error 503 Backend fetch failed (https://wiki.step-project.com/STEP:2.10.0) opening it up in a new window

[z929669]

The first error is due to the length of time required to serve up content, which can be slow at busy times and/or times when really large guide pages are being edited. I have increased the timeout from 30-60 seconds to reduce the 504 errors (but load times may take between 30-60s now ... otherwise 504 again).

 

The second has to do with caching I think. I'm not messing with those params as of yet, but I did set some pool directives more appropriately.