Skip to content

Connected but number of peers constantly 0 #137

@mihha

Description

@mihha

Hi,

I noticed that after the computer (both Win10 and Win 11) goes back from hibernation, ClipCascade client is apparently connected to the server, but the number of peers is always 0

Only if I quit the client and start it again, it connects to peer

This connection lasts for a short time and after that, the connection is lost again

Something is breaking this connection, but I can't debug what

Can you tell me how could I debug the problem to see what is going on?

Server is behind Apache reverse proxy with the following configuration

Protocols h2 h2c http/1.1

ProxyRequests Off
ProxyPreserveHost On

RequestHeader set X-Forwarded-Proto https
RequestHeader set X-Forwarded-Port 443

ProxyPass / http://localhost:8123/
ProxyPassReverse / http://localhost:8123/

RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule ^/?(.*) "ws://localhost:8123/$1" [P,L]

I can see the following in the logs when I restart the ClipCascade clinet

2025-11-29 06:38:02,049 - ERROR - scheme http is invalid - goodbye
2025-11-29 06:38:04,521 - ERROR - Failed to connect websocket: 'NoneType' object has no attribute 'close'
2025-11-29 06:38:06,546 - INFO - Login successful: 200
2025-11-29 06:38:08,475 - INFO - Server mode: P2P
2025-11-29 06:38:09,437 - INFO - STUN URL: stun:stun.l.google.com:19302
2025-11-29 06:38:10,035 - INFO - Websocket connected
2025-11-29 06:38:10,074 - INFO - Connection(0) Could not bind to 169.254.224.154 - [WinError 10049] The requested address is not valid in its context
2025-11-29 06:38:10,074 - INFO - Connection(0) Could not bind to 169.254.206.178 - [WinError 10049] The requested address is not valid in its context
2025-11-29 06:38:10,074 - INFO - Connection(0) Could not bind to 169.254.56.51 - [WinError 10049] The requested address is not valid in its context
2025-11-29 06:38:10,075 - INFO - Connection(0) Could not bind to 169.254.172.3 - [WinError 10049] The requested address is not valid in its context
2025-11-29 06:38:10,075 - INFO - Connection(0) Could not bind to 169.254.154.139 - [WinError 10049] The requested address is not valid in its context
2025-11-29 06:38:10,075 - INFO - Connection(0) Could not bind to 169.254.201.171 - [WinError 10049] The requested address is not valid in its context
2025-11-29 06:38:10,075 - INFO - Connection(0) Could not bind to 169.254.218.236 - [WinError 10049] The requested address is not valid in its context
2025-11-29 06:38:10,076 - INFO - Connection(0) Could not bind to 169.254.245.166 - [WinError 10049] The requested address is not valid in its context
2025-11-29 06:38:15,431 - INFO - Connection(0) Discovered peer reflexive candidate Candidate(L6CWFuPhc4 1 udp 1845501695 100.124.133.128 55283 typ prflx)
2025-11-29 06:38:15,432 - INFO - Connection(0) Check CandidatePair(('100.124.133.128', 64628) -> ('100.124.133.128', 55283)) State.WAITING -> State.IN_PROGRESS
2025-11-29 06:38:15,433 - INFO - Connection(0) Check CandidatePair(('100.124.133.128', 64628) -> ('100.124.133.128', 55283)) State.IN_PROGRESS -> State.SUCCEEDED
2025-11-29 06:38:15,433 - INFO - Connection(0) ICE completed
2025-11-29 06:38:15,455 - INFO - Connection(0) Discovered peer reflexive candidate Candidate(Qumy6foO1o 1 udp 1845501695 192.168.1.72 55283 typ prflx)
2025-11-29 06:38:15,456 - INFO - Connection(0) Check CandidatePair(('192.168.1.72', 64629) -> ('192.168.1.72', 55283)) State.WAITING -> State.IN_PROGRESS
2025-11-29 06:38:16,450 - INFO - Connection(0) Remote candidate "944b9afe-be0f-4a72-b9a7-ebcfb031374a.local" could not be resolved

Can you please help me to resolve the problem?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions