Geyser: Stucked client at "Locating Server" in iOS and Android

[hlarrainq]

Describe the bug
The client of Minecraft in iOS and Android gets stuck when Geyser is hosted in a external MC Host without the port 19132.

To Reproduce

1. Get a Minecraft Host online (Issue tried in theminecrafthosting, server.pro and PebbleHost)
2. Start Geyser Server at a port different of 19132
3. Configure configs.yml with the java server
4. Reload geyser and connect a mobile client of Minecraft Bedrock
5. Get stucked at Locating Server (generating world)

Expected behavior
The client connects without issues.

Screenshots / Videos

Server Version
git-Spigot-0287a20-7560f5f (MC: 1.16.1)

Geyser Version
1.0.0 (git-master-c4db0e2)

Minecraft: Bedrock Edition Version
Tested with 1.16.0 and 1.16.1

Additional Context
The problem doesnt happen in Windows 10 edition of bedrock. This issue happens always in any java server. Using LAN in a local computer fix the issue.

[Tim203]

Have you tried looking at the common issues page?

[hlarrainq]

Yes. This problem is not listed, and it seems like a bug because W10 works pretty good in the same Geyser server.

[Tim203]

Is it a local hosted server?

[hlarrainq]

No. Sorry if there is a confusion. This happens only when Geyser is hosted in a MC Online Host. When i tried Geyser in my local network, it works fine in iOS and Android.

[D3ATHBRINGER13]

The same issue occurs on Xbox, and the current way to fix it, is to just cancel the connection and try again
I don't know if this is a bug that can be fixed or not

[JustBuddy]

Have the same issue, but only in my local network. Except Windows 10, no other version will connect no matter how often I retry.

On mobile, playing over data or a different network works, just not my home WiFi.
Seems like there is a specific network condition that hinders the connection to complete on non-win10 clients.
Since the server receives the connection and gets a username, something seems to lack in the reply delivery.
The "Recommended" Servers in the versions in question work just fine.

[D3ATHBRINGER13]

Yeah, I get the problem on my locally hosted server as well, though whenever I retry on any device it starts working

[DoctorMacc]

The problem Deathbringer is describing we should have fixed.

[D3ATHBRINGER13]

Am I describing a different issue then
Sorry for the confusion

[DoctorMacc]

For those of you having this issue: are you able to try a native Bedrock server in its place? What happens then?

[JustBuddy]

@DoctorMacc I do not own a custom Bedrock server, but as I wrote the ones Recommended work just fine. (With recommended I mean the Advertised ones.)

[DoctorMacc]

Can you try a Nukkit server?

[D3ATHBRINGER13]

I used to use a BDS and it this problem did not occur

[JustBuddy]

Can you try a Nukkit server?

I joined a random server from a mpe serverlist and it just works fine. I don't have a nukkit server outside my lan to test.
Joining that random server worked just fine.

[RednedEpic]

I recommend checking out the common issues page again as it likely has a fix that works for you. For future reference, issues like this should be discussed on Discord, not the issue tracker, as mentioned within the issue template. Please join us there if you haven't already 🙂. Closing.

[JustBuddy]

As stated before, common issues do NOT apply to this topic.
Discussion in discord are not viable for this issue, they get swept away by other inquiries easily, and if the issue is something in the way the replies are sent back to the client in certain circumstances, this should be an issue worthy of investigating here.

Please reopen this issue case.

As stated before closure, connecting to 3rd party servers works just fine.

[Heath123]

This does seem like a Geyser issue

[DoctorMacc]

Yes, this does not seem like a Geyser issue. The clients are connecting (so it's not a port forwarding issue), but not getting any farther in the world. And I believe the IPs in the config are set correctly. Some clients can connect if Windows 10 can. I'm reopening this - but I need more information. If you have this problem, do not hesitate to contact me (Camotoy) in the Development channel on Discord. this is an older error so please do not contact me about this specific error.

[Noahkemm]

Hello!

We have the same bug.
If i connect with the SAME Client-IP on mobile and computer to beta.neruxvace.net, the mobile cannot access the geyser proxy anymore.

If this happens i get the following output in the terminal:

[20:59:48 INFO] /95.223.***.***:22647 versuchte zu verbinden!
[20:59:49 INFO] Spieler ChickenPat4713 verbunden
[20:59:56 INFO] Bedrock Benutzter mit der IP /95.223.***.*** wurde getrennt wegen CLOSED_BY_REMOTE_PEER

With mobile network i can connect fine:

[20:59:58 INFO] /185.93.***.***:51260 versuchte zu verbinden!
[20:59:59 INFO] Spieler NeruxVace verbunden
[21:00:56 INFO] NeruxVace (eingeloggt als: Noaaah) ist jetzt mit dem Java Server unter der Adresse server.nerux.net verbunden
[21:01:01 INFO] Spieler bei 331,3 133 -397,3 erzeugt

Here you can see the dump of current Geyser-Proxy:
https://dump.geysermc.org/8ZHdAgw8nwcBd0Wcqp5uVaDkSqPzVCQ5

I hope you can help us out!
Thanks a lot for your great software.

[jackson-57]

Me and my friend are unable to connect to our server (Default port of 19132) with Geyser installed, on T-Mobile, Google Fi (T-Mobile only), or AT&T (using mobile hotspot on a Samsung phone), on our normal Android phones. Using a VPN does not fix this. We can connect fine over other networks, just not VPNs or cellular. When I tried connecting to the server using an iPhone 5 (iOS 10) with a Google Fi data SIM (also T-Mobile only), it surprisingly worked.

[jackson-57]

I just tested running a mobile hotspot on the iPhone 5 and connecting from my Android phone, I was able to connect to the server.

[hlarrainq]

Sorry for letting this issue for two days without more information. Today i was able to testing more about this problem.
First, i opened the server (in a MC host, not locally) and gave the ip of Geyser to some friends, they connected without any problems from iOS and Android.
So, i changed my router IP and tried to connect again from mobile but it didnt work, W10 still worked fine.
Then i used my 4G in mobile hotspot and i was able to connect from my iPad. Then i used my WiFi + VPN in US and i was able to connect in Android and iOS.
So, it seems like a problem from the client internet, not the server.
This never happened to me in another server from bedrock or java, so i still dont understand what is happening.
Also thanks for all the people who are trying to figure it out the issue.

[JustBuddy]

Seems like this is a really weird network specific issue.
From my network, only Windows 10 can connect to Geyser, Mobile and Consoles (over Phantom) are unable to connect. (Locating World, endless loop). It looks like Mobile/Console do not communicate like the Win10 version, and some condition of that network make the clients miss something from Geyser.

My best bet is that it could be something in the redirection department. In my case, I run my Java Server at PebbleHost, where I have to use the same port for Java and Geyser. The messages you see in OP's Error log in Post 1 might indicate that the Geyser "Proxy" receives the request as expected, but is not forwarding it for some reason. Or it is forwarding it, but the Java Server itself is unable to communicate with the client.

As stated, this issue only happens on certain network conditions, not sure how we would be able to pinpoint that issue.

[DoctorMacc]

If i connect with the SAME Client-IP on mobile and computer to beta.neruxvace.net, the mobile cannot access the geyser proxy anymore.

According to another user this is a limitation of the server that is being connected to.

[DoctorMacc]

With the help of RTM we were able to confirm the bug - however, the bug also happens with the new Nukkit rewrite/Cloudburst Server.

[DoctorMacc]

What does work:

• RTM connecting to a server (Cloudburst/Geyser) without a VPN on cellular Android

What doesn't work

• RTM connecting to a server (Cloudburst/Geyser) with a VPN on cellular Android

[MastoryMd5]

Can this be solved using something like nginx? I will try because it looks interesting and the problem happens to me too but with the port 19132.
It might be and ISP issue that blocks udp traffic or works in a weird way but i hope to fix this.
.

[jackson-57]

I was able to connect directly from my Android phone on cellular to a test server running on Windows, hosted on a different network, but on the same ISP. Maybe this has to do with the operating system being run on the host, or different networking equipment.

[DoctorMacc]

@jackson-57 thank you for the suggestion! RTM and I tried again tonight and Windows connected successfully in all instances.

[DoctorMacc]

Is this still an issue? RTM just tried today and all problems were magically fixed.

[JustBuddy]

Issue still persists on latest 20.07.2020 build of geyser.

[DoctorMacc]

Does the issue still persist with the latest build? Geyser hasn't done anything specifically to fix it.

[jackson-57]

Just updated Geyser and tested, the issue still persists.

[bundabrg]

Just to add slightly, using my bleeding build and an IOS tablet over wifi hotspot on my phone I can connect without issue to a non standard port on my hosted instance. Perhaps the "smoothness" pr helps at all?

[bundabrg]

Running BDS on same IP and port above works.

[DoctorMacc]

Could anyone with thus bug please try #656?

[jackson-57]

Could we please get a test server started up for #656, so others can quickly test this? I tried to connect to another PR's test server and it didn't work, so it wouldn't be a false positive.

[DoctorMacc]

On it.

[jackson-57]

Thanks!

[jackson-57]

My client was stuck at 'locating server' when trying to connect to the test server over cellular, but as this issue is so varied in results, others should give it a try as well

[DoctorMacc]

In #656 Jackson did successfully join the Java server.

[JustBuddy]

Tried to connect to the test server, still stuck at "Looking for Server".

[toinouH]

@JustBuddy Did you tried with your mobile connection or your wifi ?

[JustBuddy]

Home Wifi, the connection which I have this issue.
Mobile Data works fine on any server for me.

[toinouH]

@JustBuddy Do you used the max render distance value ?

[JustBuddy]

No, using the lowest actually.

[jackson-57]

@JustBuddy were you using a vpn on your home network?

[JustBuddy]

Just my regular home network, nothing fancy in between.

[toinouH]

I had the same issue on my mobile connection and on my wifi with the windows 10 edition (I guess it's because my connexion is really bad)

[SupremeMortal]

The connection issues described are likely the result of CloudburstMC/Network#8

[DoctorMacc]

@JustBuddy are you on our Discord server?

[JustBuddy]

@DoctorMacc Yes, Buddy#0001

[bundabrg]

I've tested servers and clients both with a variety of MTU. I can also confirm that java forces the DontFragment bit on so I don't think its necessarily related here (DF needs to be on for path discovery). Every test seems fine. The connection handshake basically sends a padded request from the largest size, reducing it until the client responds (thus the packet gets through, since with DF set the packet is dropped if its too big anywhere on the path).

What I need is someone who can replicate the issue doing either a wireshark or tcpdump of the connection ideally from both sides and saving them to a pcap file (this is readable again later by either program). If you're worried about IP's leaking in the file then encrypt and DM me a password.