ViaProxy icon indicating copy to clipboard operation
ViaProxy copied to clipboard

Unable to join 1.21.3 bedrock realms server

Open Kurt6 opened this issue 1 year ago • 12 comments

Cant join 1.21.3 bedrock realms

  • When trying to join from 1.21 to a bedrock realm it just says unable to connect to backend server and doesnt allow you to join.

Kurt6 avatar Jul 25 '24 16:07 Kurt6

Upload the ViaProxy log (Advanced tab -> Upload log) after you tried joining

RaphiMC avatar Jul 25 '24 16:07 RaphiMC

https://mclo.gs/ENSnyVL

Kurt6 avatar Jul 25 '24 16:07 Kurt6

Can you record a video of the issue and all the steps you do in ViaProxy before joining

RaphiMC avatar Jul 25 '24 16:07 RaphiMC

Can you record a video of the issue and all the steps you do in ViaProxy before joining

https://github.com/user-attachments/assets/f1f4d38e-c123-4a79-8f07-e999461a654f

Kurt6 avatar Jul 25 '24 17:07 Kurt6

Try it with a vanilla client

RaphiMC avatar Jul 25 '24 18:07 RaphiMC

Try it with a vanilla client

Used a vanilla client and got the same exact error.

https://mclo.gs/O7rUg9B

Kurt6 avatar Jul 25 '24 18:07 Kurt6

Do you have a non macos computer you can try this on?

RaphiMC avatar Jul 25 '24 18:07 RaphiMC

Do you have a non macos computer you can try this on?

Yes, let me make an attempt and I will get back to you, have to install mc + software.

Kurt6 avatar Jul 25 '24 18:07 Kurt6

Do you have a non macos computer you can try this on?

I tried a fresh install of Windows on 1.21, and it connected and worked; I will try a fresh install of Java and the game on Mac and see if it solves the problem.

Kurt6 avatar Jul 25 '24 18:07 Kurt6

Do you have a non macos computer you can try this on?

I tried a fresh install of Windows on 1.21, and it connected and worked; I will try a fresh install of Java and the game on Mac and see if it solves the problem.

Fresh install of MacOS and minecraft and ViaProxy, getting the same error as before and not connecting to the backend server.

Here is the log file from the latest version with a fresh install: https://mclo.gs/ZpuHdEa

Kurt6 avatar Jul 25 '24 23:07 Kurt6

Can you install wireshark and let it record the packets ViaProxy sends (After starting wireshark, select your main network interface to start recording, then use ViaProxy and stop the packet recorder after you get disconnnected). After you are done go to the filter field of wireshark and filter for raknet (press enter to submit). Make a screenshot of the full window and send it (you can dm it on discord if you want: rk_01)

RaphiMC avatar Jul 25 '24 23:07 RaphiMC

Can you install wireshark and let it record the packets ViaProxy sends (After starting wireshark, select your main network interface to start recording, then use ViaProxy and stop the packet recorder after you get disconnnected). After you are done go to the filter field of wireshark and filter for raknet (press enter to submit). Make a screenshot of the full window and send it (you can dm it on discord if you want: rk_01)

Added you on discord

Kurt6 avatar Jul 26 '24 05:07 Kurt6

try 74.235.56.167_30222_Bedrock-1.21.2.viaproxy.localho.st which is public wildcard hostname, to enable public wildcard hostname for bedrock and java: enable forward-hostname in geyser config set wildcard-domain-handler to Public in ViaProxy restart viaproxy.

select the account and then join with 74.235.56.167_30222_Bedrock-1.21.2.viaproxy.localho.st

Outfit8TSB avatar Sep 11 '24 07:09 Outfit8TSB

try 74.235.56.167_30222_Bedrock-1.21.2.viaproxy.localho.st which is public wildcard hostname, to enable public wildcard hostname for bedrock and java: enable forward-hostname in geyser config set wildcard-domain-handler to Public in ViaProxy restart viaproxy.

select the account and then join with 74.235.56.167_30222_Bedrock-1.21.2.viaproxy.localho.st

This is unrelated to the issue. Public wildcard hostname doesnt even support Realms.

RaphiMC avatar Sep 11 '24 08:09 RaphiMC

Closing because I already fixed the issue in the latest dev build

RaphiMC avatar Sep 11 '24 08:09 RaphiMC