Companion with ip 0.0.0.0 not listening #79

Closed
opened 2026-10-27 09:32:03 +01:00 by adam · 2 comments
Owner

I added a companion with default wildcard-ip 0.0.0.0 and it is not reachable by any client-software.

After that I added a second companion with lan-ip 192.168.. and this one is reachable.

Because my pyMC-setup has more than one lan-ip it would be nice, if 0.0.0.0 works as expected.

I added a companion with default wildcard-ip 0.0.0.0 and it is not reachable by any client-software. After that I added a second companion with lan-ip 192.168.*.* and this one is reachable. Because my pyMC-setup has more than one lan-ip it would be nice, if 0.0.0.0 works as expected. <!-- github-sync-id:4291074805 -->
adam closed this issue 2026-10-27 09:32:03 +01:00
Author
Owner

EDIT: if I add another compation with 0.0.0.0 this one is reachable

EDIT: if I add another compation with 0.0.0.0 this one is reachable <!-- github-comment-id:4276088987 -->
Author
Owner

EDIT: I found the reason ...

the last companion selected in WebUI is "blocked" by Websession and not available from tcp-clients

EDIT: I found the reason ... the last companion selected in WebUI is "blocked" by Websession and not available from tcp-clients <!-- github-comment-id:4276214362 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/pyMC_Repeater#79