Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection timeout when trying to connect to LAN games #747

Closed
hgabreu opened this issue Jan 3, 2023 · 6 comments
Closed

Connection timeout when trying to connect to LAN games #747

hgabreu opened this issue Jan 3, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@hgabreu
Copy link

hgabreu commented Jan 3, 2023

Describe the bug
Can't connect to any multiplayer game. The games are shown on the friends list (same LAN), but when clicked to join, it times out after a while (around a minute) with a "Connection timed out. Unable to connect to world." message.

It's on the same LAN, running the same version: 1.19.51.01

To Reproduce
Steps to reproduce the behavior:

  1. mcpelauncher-ui-qt -v mcpelauncher-ui-qt.logs.txt
  2. Load load 1.19.51.01 and wait for the microsoft login to do its thing.
  3. Click Play, then the Friends tab, try a LAN game running the same bedrock version.
  4. After a while on the "Connecting to multiplayer game", it gives up with the error: "Connection timed out. Unable to connect to world."

Expected behavior
I expected to log into the game normally.

Screenshots
mcpelauncher-client.logs.txt

Desktop (please complete the following information):

  • OS: Archlinux 6.1.1-arch1-1

  • Version:
    mcpelauncher-linux-git v0.5.0.r3.g68ac253-1
    mcpelauncher-msa-ui-qt-git v0.3.4.r1.g41138a9-1
    mcpelauncher-ui-git v0.3.2.r6.g485df2e-1

  • Installation Type: built from AUR package builds

Additional context
Unfortunately it's quite hard to rollback my android versions on my phone to test this with previous bedrock versions. But I had LAN games working fine yesterday with version 1.19.41.01 and previous release of ng branch.
Local worlds work fine, it's just multiplayer that is failing.
I also tried removing my ~/.local/share/mcpelauncher but got the same issue.

@hgabreu hgabreu added the bug Something isn't working label Jan 3, 2023
@HighWingy
Copy link

Just wanted to add I'm having the same issue. I'm running Fedora 35 KDE using the FlatPak launcher.
I can connect to my local server with my phone and windoze PC without issue. But using this launcher it just sits at connecting, and then eventually times out.

@fragmuffin
Copy link

fragmuffin commented Jan 4, 2023

+1; me too, same symptoms

Minecraft Version: 1.19.51.01 (X86_64)

System Details
$ uname -orm
5.15.0-56-generic x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.1 LTS
Release:        22.04
Codename:       jammy
Flatpak Details
$ flatpak --version
Flatpak 1.12.7

$ flatpak list
Name                                 Application ID                               Version          Branch          Installation
Minecraft Bedrock Launcher           io.mrarm.mcpelauncher                        v0.6.0           stable          system
Mesa                                 org.freedesktop.Platform.GL.default          21.3.9           21.08           system
openh264                             org.freedesktop.Platform.openh264            2.1.0            2.0             system
Adwaita theme                        org.kde.KStyle.Adwaita                                        6.3             system
KDE Application Platform             org.kde.Platform                                              6.3             system

Changes over time...

Changes to login, and authorised access appears to change in strange ways when left for long periods.

Case 1) ~30min

  1. Open app, and allow it to login (avatar was incorrect ⛔, but username was correct ✔️ )
  2. After ~8min, avatar is replaced with loading animation.

 

  1. after 30min Fetching Realms... changes from blank, to loading animation

 

However, in this case, nothing changed after this time... no servers could be joined.
Although I didn't wait for...

Case 2) ~2hrs

  1. I opened Minecraft.... and clicked nothing for ~2hrs (forgot about it TBH).
  2. Clicked [Play], and my realms (or lack thereof) was detected... progress

 

  1. Clicked on [Friends], Joinable Realms is visible (instead of blank).

and finally...

  1. Clicked on my local server

 

✔️ SUCCESS

  1. Quitting, and joining again, works as well.

Joining the local server both times takes much longer than I expect, ~10sec until it's "Loading Resources".
My phone is much faster.

I understand this is quite clumsy debugging on my part... but I hope this is useful in some way.
Please let me know if you'd like any other information.


edit: It may also be worth noting that URLs don't open from the launched app, details in flathub/io.mrarm.mcpelauncher#90 . Which means I cannot login using to my Microsoft account using v1.19.51, instead I logged in using v1.19.40, then opened v1.19.51 which logged in automatically.

@are27
Copy link

are27 commented Jan 9, 2023

Same issue with v1.19.51

What doesn't work:
Connecting to a LAN server
Connecting to a friend's game (a world created on their device)

What does work:
Friend connecting into a world I've created locally on my device

Older versions used to connect to the server fine

@ChristopherHX
Copy link
Member

ChristopherHX commented Jan 9, 2023

Do you notice any difference in v0.7.0? This version won't be released as binary due to known issues, you can get a snapshot here https://github.com/minecraft-linux/mcpelauncher-manifest/actions/runs/3867378333

I made the xbox live http client async non blocking, previously it has been implemented as a simple blocking method.

  • The xbox live login button now responds much faster if you press login
  • The external server list loads much faster
  • The Achivements are no longer timeout if you open them for the first time after loading the game

I don't think this fixes timeouts while joining servers.

@fragmuffin
Copy link

Yes!, that's fixed it for me!

Tested x86_64-v0.6.0.9 (from the above snapshot link)... not sure about the v6 label... but it's definitely more recent than the last .AppImage I tried.

LAN Connection ✔️

Using saved session data, connecting to local server works 🎉

WAN Connection ✔️

Same auth as above, connecting to some random remote server works 🎉

Logout / Login ✔️

Logging out and logging works....
Then with new login, repeating the above LAN & WAN tests also work

Nice work @ChristopherHX 😁 , thank you.

@hgabreu
Copy link
Author

hgabreu commented Jan 14, 2023

It took me a while to get the new version working here, but I can confirm it fixed the issue indeed. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants