Windows: Socket connection failed about converse-tauri HOT 9 OPEN

You have websockets active?

from converse-tauri.

Very odd, can you tell if there is anything running on that port ?

from converse-tauri.

You have websockets active?

Nope, first time trying to connect with Converse.js, sorry.

I know it's not the right place to mention this, but don't you think a user error should be shown when trying to connect and it doesn't work? I had to open the browser's console for that ;)

from converse-tauri.

Hang on, what did you change to make it work? The user shouldn't have to do anything but input a username and password

from converse-tauri.

Hang on, what did you change to make it work? The user shouldn't have to do anything but input a username and password

I didn't, because my server wasn't capable (but the GUI did not show this, no error was exposed to the user). Now it works, after I enabled Websocket support on my server :)

from converse-tauri.

Sorry, after setting up websocket support, I tested Converse Tauri using Linux (which works as expected). On Windows however, I still get

WebSocket connection to 'ws://127.0.0.1:10032/xmpp-websocket/' failed: Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received
_connect @ converse.min.js:2
connect @ converse.min.js:2
connect @ converse.min.js:2
wc @ converse.min.js:2
_c @ converse.min.js:2
login @ converse.min.js:2
converse.min.js:2 
        
        ERROR: Websocket error {"isTrusted":true}
log @ converse.min.js:2
error @ converse.min.js:2
J.error @ converse.min.js:2
_onError @ converse.min.js:2
socket.onerror @ converse.min.js:2
error (asynchron)
_connect @ converse.min.js:2
connect @ converse.min.js:2
connect @ converse.min.js:2
wc @ converse.min.js:2
_c @ converse.min.js:2
login @ converse.min.js:2
await in login (asynchron)
reconnect @ converse.min.js:2
await in reconnect (asynchron)
m @ converse.min.js:2
v @ converse.min.js:2
p @ converse.min.js:2
setTimeout (asynchron)
f @ converse.min.js:2
y @ converse.min.js:2
reconnect @ converse.min.js:2
onDisconnected @ converse.min.js:2
onConnectStatusChanged @ converse.min.js:2
_changeConnectStatus @ converse.min.js:2
_doDisconnect @ converse.min.js:2
_onClose @ converse.min.js:2
socket.onclose @ converse.min.js:2
converse.min.js:2 
        
        ERROR: Websocket closed unexcectedly

There doesn't seem to be any service listening on Port 10032 when Converse is not started. When it's started, I can see

  TCP    127.0.0.1:10032        0.0.0.0:0              LISTEN

from converse-tauri.

Yea your server shouldn't need WebSocket support, that's why xmpp-proxy is listening on that port.

So if the port is listening I'm wondering if the windows firewall is stopping it from being connected to, or making outgoing connections, is there a way to check that in windows?

from converse-tauri.

I tried both, without success:

• Adding explicit allow rules to the Windows Firewall
• Completely disabling the Windows Firewall

netstat -a lists Converse Tauri listening on port 10032.

Anything I can do to debug this?

from converse-tauri.

I just tried with Converse Desktop. It did not work right away. But after adding /.well-known/host-meta data, it actually connected. Converse Tauri on the other side still doesn't connect.

from converse-tauri.