search

slowscript / warpinator-android

An unofficial implementation of Warpinator for Android
GNU General Public License v3.0
481 stars 29 forks source link

failed to start grpc server #56

Open Christian891 opened 3 years ago

Christian891 commented 3 years ago

Hello, when the app is starting I get the error message "failed to start grpc server". Is there anybody who knows this issue? thank you

slowscript commented 3 years ago

Hi, yes, I've heard about this already but I don't know yet what causes it. Could you please try installing this debug build and obtaining a debug log (as described in connection-issues.md)? It would be much appreciated.

psiska commented 2 years ago

Hello, from debug logs I can see 

java.io.IOException: Failed to bind to address ::/:::42000

Trying on xiaomi miui. Tested that 5353(udp) and 42000(udp) are reachable (from pc) 42000(tcp) is indeed not responding.

Will this help?

slowscript commented 2 years ago

Thanks, this does give me a little more insight. My initial guess is that something else is bound on that port (or the app crashed and OS still treats it as bound). Can you try changing it in the settings (anything between 50000 to 60000 should work)? Rebooting your phone can also help. Other than that, I think MIUI has an option to block network/internet access for some apps, which could also be causing the problem.

ErrorJan commented 2 years ago

I also had this Problem. I can confirm that changing the port or rebooting the device works! I have a Samsung Smartphone with Android 12 and OneUI-Version 4.1

Pentaphon commented 1 year ago

I think MIUI has an option to block network/internet access for some apps, which could also be causing the problem.

Motorola stock ROM phone here. I also had this problem when I upgraded to 1.6 but a reboot fixed it. However. A reboot shouldn't be necessary and if a port was being blocked somehow, a reboot wouldn't be enough. You'd have to change the port. There is more to this issue than we understand but I'm glad we still have an open issue for it.

anderood commented 1 year ago

Hello, when I updated to version 1.6, I had this problem. It was working normally before.

In any case, I followed my friends' advice to restart the device and everything worked again.