Pain point · Documentation · Blocks work
Admin console breaks after upgrade to 3.0 and reverse proxy paths are unclear
2 source threads · first seen 2016-05 · last seen 2017-02
Summary
After the API version change, the system console returns server errors and the admin cannot tell which API paths need websocket upgrade handling behind an Apache reverse proxy.
- Affects
- admins using Apache reverse proxy
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“After setting up a reverse proxy the log is full of those messages:”
“what API paths need the websocket upgrade”