Can't establish a connection to the websocket server

[EddyLuten]

I have the similar problem. The Edit button not responding.

Originally posted by @noeldum in #1 (comment)

[EddyLuten]

I'm unable to reproduce this locally. I'll leave this open in case anyone can supply me with some more information on how to repro or fix this.

[noeldum]

Using Ubuntu 22.04.3 LTS

[EddyLuten]

Hmm, I'm on Ubuntu 23.10 using Firefox 122.0. I was on 22.04.3 LTS until a few days ago and also didn't have any of these issues.

I don't have netstat, but when I run ss -ap | grep 8484 | sed 's/[[:space:]]*$//' I get this output:

Everything seems to be working as expected; there are no browser console errors, etc. Could you try overriding the websocket port and see if you still see the same error? You can do so by modifying your mkdocs.yml like so:

Where 8833 is any port you want that your process is allowed to open.

[noeldum]

same thing again. No change.

[EddyLuten]

Interesting. I don't see FF as a consumer of that connection in your screenshot at all. Can you verify that you don't see any issues when running a test here?

Also, do you happen to have another browser installed to see if it works there?

[noeldum]

all ticked green on websocketstests. Both using firefox and chromium. Both browsers behave the same.

[EddyLuten]

What might be happening is that the WebSocket tries to connect before it completes initializing on the server. I'm making a few improvements in 0.1.4 to connect after DOM loading is complete and a retry mechanism if the connection fails. I also won't show the controls until I get a signal from the server that the WebSocket connection is open and ready to accept connections.

Let me know if the issue persists in this new version, and I'll keep digging around.