Closed gjost closed 5 years ago
Actually this is a problem with Nginx configs. Nginx was not able to contact the ddrlocal
process. Nginx was configured to display /502.html
in the event of a 502 but was sending all requests to ddrlocal
, which didn't know what to do with that URL.
Commits 36ea29e and 0415bd6 fix this. The result is that regular Nginx 502 error gets displayed.
Problem: 502 error actually presents as a 404 error. Paths from urls.py are listed and it the bottom it says "The current path, 502.html, didn't match any of these."
Users mistake this for a 404 error. See https://github.com/densho/ddr-cmdln/issues/156