iodide stage server is intermittently giving 502 errors
Categories
(Cloud Services :: Iodide, task)
Tracking
(Not tracked)
People
(Reporter: wlach, Assigned: robotblake)
References
Details
It looks like the current iodide stage server (https://stage.iodide.nonprod.dataops.mozgcp.net) is intermittently giving 502 errors. Here's an example:
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>openresty/1.13.6.2</center>
</body>
</html>
:robotblake, any idea what might be happening? it seems to happen with both static and dynamic content, my guess it has something to do with the interaction between the nginx server and the django process
|
Reporter | |
Comment 1•6 years ago
|
||
We think this is caused by nginx trying to connect to the django container/pod before it is actually ready. Blake is going to open up a PR to add some dockerflow endpoints to iodide which should fix this.
|
|
Reporter | |
Comment 2•6 years ago
|
||
This issue is half-fixed. We added the necessary dockerflow endpoints, but we still need to configure nginx to not put them behind openidc (since the services which need to access them aren't authenticated):
curl -L https://stage.iodide.nonprod.dataops.mozgcp.net/__version__/
:robotblake, assigning this to you, whenever you have a chance to look into it.
|
|
Reporter | |
Comment 3•6 years ago
|
||
:robotblake fixed this!
Description
•