Socket connections on ssl port
Have you compared it to the non-SSL version?
@Anton
Good suggestion, i was able to test it quickly on my local lan over http since traccar servers runs on my local lan and ssl port exposed to the internet.
The result is the same.
So the conclusion would be this is expected behaviour on a working socket connection ?
Socket in Pending and Timing in Stalled on the Network / WS tab in chrome dev tools.
Then yes, I think it's expected behavior. WebSocket should keep the connection open to send live updates.
Ok, i tested it outdoors also with my app and now finally my app stays connected with the socket connection. So for any future reading. I thought the issue might be with the way i have setup the internal proxy server to be able to use the Domain ssl connection with traccar server. Or that it had to with the custom app i am configuring. But now finally i found out that it was the QoS protection on my router that blocked the socket connection from the internet (while regular https request where working). Thanks Anton.
could you show your config QoS to see what changes you made currently the same thing happens to me I suffer from stagnation of the connections the browser freezes and I have 3thousand devices on a dedicated server...
I have been struggling for quite a while now with making socket connections work to my own traccar server as an ssl domain.
But it seems now that i got it working. I have a question to verify this. From dev console on the ssl domain i see these constant update flow of messages under: network / ws.
You can see the request url is ssl: wss
Timing Stalled
Status Pending
This seems correctly working to you ?
I wonder why the socket connection shows Stalled and status of the socket is in Pending while clicking on it it will show the updates under messages.
This setup is correctly working now ?