March 27, 20215 yr I've cleared my browser cache, but still cannot connect via noVNC using Firefox. I can connect using a third-party VNC client, so the problem seems to be in noVNC. Does anybody have any idea what the problem could be? It's a pain to have to fire up TigerVNC and find the correct port to connect to when you just want to verify something…
March 27, 20215 yr 1 hour ago, ElectricBadger said: Yup — right there in the first line of the post 😉 Sorry, read that too fast.
March 27, 20215 yr I'm afraid I don't recognise the screenshot, though from what I can tell it's indicating an error. Clearing the cache worked for me. Does using a different browser help or is it specific to Firefox?
March 28, 20215 yr Author After some digging, I found that the problem is due to Deluge setting a cookie whose value is longer (1819 bytes) than noVNC can cope with, hence the 403 Request Entity Too Large. Quite why it needs that much to list which columns should be shown, and in what order, I don't know! I don't suppose this is that easy to fix — I assume the limit is in upstream code somewhere? As a workaround I've changed the Deluge Docker container to provide http://«servername»:8112 as its web interface, so that the browser sees it as being a separate webserver from http://«ip», which is what the VNC Remote button uses, but if any Docker container that's been accessed via the server IP and a port can break browser VNC, it's not good…
Archived
This topic is now archived and is closed to further replies.