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 -->
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 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
EDIT: if I add another compation with 0.0.0.0 this one is reachable
EDIT: I found the reason ...
the last companion selected in WebUI is "blocked" by Websession and not available from tcp-clients