05-06-2013 10:44 AM
WebSocket connection to 'wss://192.168.1.1/ws/stats' failed: Unexpected response code: 503
I still see the heartbeat.json requests succeeding. I have not restarted the ERL yet (I would imagine that it'll resolve the issue), @UBNT-stig, @UBNT-ancheng, is there any log or something that I should look at?
NOTE: That other than the stats, the ERL is functioning well.
05-06-2013 11:02 AM
No, there's nothing other than:
2013-05-06 12:17:01: (server.c.1230) logfiles cycled UID = 0 PID = 17587
And there's nothing in the previous log file (other than server starting).
05-06-2013 11:15 AM
Does the CLI window in the Web UI still work? Also is changing the configuration from the Web UI still working?
Yes, the CLI works and I can change settings still.
05-06-2013 11:29 AM
Since the CLI window in the Web UI still works, that seems to indicate the WebSocket module is still working and so is the backend daemon that supports the CLI window. Could be a bug in the Web server or the stats handling, hard to say. If possible, can you try restarting it and see if the problem persists?
05-20-2013 08:26 AM
OK we'll keep an eye on this issue then. Thanks for reporting it.
I am seeing something that's a bit similar ... I have seen it several times before.
Failed to load resource https://192.168.1.1/ Failed to load resource: the server responded with a status of 500 (Internal Server Error) https://192.168.1.1/api/edge/heartbeat.json
Interestingly, the pie chart *is* updating (although it's not obvious) and using the Network tab in Chrome I see the calls are continuing to /api/edge/heartbeat.json and to /.
There is nothing odd in the logs on the ERL and the CLI does still work. Clicking around the tabs doesn't fix anything, but if I refresh the page it does fix the issue. This is running the v1.1 release.