So i accually got connected, dont know how, left it trying when i went shopping and it had the main page displayed when i got back, yay! Now there is defiantly some problem with the websockets, no idea what. Just to be sure i download your latest image and im running on that, also apt-get update, upgrade and npm update.
If you view the network data info in firefox/chrome i get this
Status 101 (Switching protocol) on /socket.io/?EIO=3&transport=websocket&sid=w5RgduPFC0Rtt29gAAAC
It seems it has a problem accually connecting too and/or keeping the websocket open.
If i try to make any changes once i finally get connected (marking a sensor hidden, deleting a sensor ect) nothing is saved, raw data log shows nothing. Reloading the page (after the 10-15mins to get the data) reverts all changes made.
-- i just checked back on the gateway tab i still have open and the sensor i marked to hidden 20mins ago is finally hidden, however the one i set right after is still not.
edit: Should the node process be using 100% cpu? That could account for the delays if there is just no CPU left to accually handle the websocket.