Hi,
today I've tried Wapinator with user A on a Linux Mint 21.1 and with user B on the same PC. User A work fine, but user B didn't. I expected it to work, but it just showed me that there was some issue with the "protocols".
Actually I had no idea what is meant with that because in the UI there is no mention ( or setting) of a "protocol".
So I ran the debug and it told me that it failed to bind the IP with some GRPC something. At first I couldn't make something out of this either.
It took me quite a while to figure out that this is a multi user issue of concurrently running 2 Linux Mint user at the same time while having Warpinator also opened twice at the same time (once for each user).
In such a configuration one has to change the incoming ports for data transfer. After I've changed the ports to 42002 and 42003, it worked.
So maybe this can be documented and maybe there is a better way to handle this situation. Either by automatically changing the ports or by giving some more meaningful error messages in such situations.
Now that I know this , I'm fine but other Warpinator users may also run into this problem in the future.
Cheers
Hi, today I've tried Wapinator with user A on a Linux Mint 21.1 and with user B on the same PC. User A work fine, but user B didn't. I expected it to work, but it just showed me that there was some issue with the "protocols". Actually I had no idea what is meant with that because in the UI there is no mention ( or setting) of a "protocol". So I ran the debug and it told me that it failed to bind the IP with some GRPC something. At first I couldn't make something out of this either. It took me quite a while to figure out that this is a multi user issue of concurrently running 2 Linux Mint user at the same time while having Warpinator also opened twice at the same time (once for each user). In such a configuration one has to change the incoming ports for data transfer. After I've changed the ports to 42002 and 42003, it worked. So maybe this can be documented and maybe there is a better way to handle this situation. Either by automatically changing the ports or by giving some more meaningful error messages in such situations.
Now that I know this , I'm fine but other Warpinator users may also run into this problem in the future. Cheers