OpenSource/GeyserMC
OpenSource/GeyserMC
1
0
Fork 0
mirror of https://github.com/GeyserMC/Geyser.git synced 2024-12-14 18:55:51 +01:00
Code Issues Projects Releases Packages Wiki Activity

Add steps (thanks to Doctacosa#8882)

Camotoy 2020-07-28 10:36:32 -04:00
parent 0f3cfa04ba
commit d51966594f
1 changed files with 10 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
Common-Issues.md

@ -44,7 +44,16 @@ This usually has something to do on your host's end. Most commonly, it's because
## Bedrock players can connect *after* hitting the server on a TCP port (e.g. on Java or a website on the same server) ## Bedrock players can connect *after* hitting the server on a TCP port (e.g. on Java or a website on the same server)
This is likely a firewall issue on your server. Please contact your server host. This is likely a firewall issue on your server.
Here is how to prevent the issue on SoYouStart (a subsidiary of OVH):
In the SoYouStart control panel:
1. Click the IP tab.
2. Click the gear at the right of the public IP address; select "Game mitigation".
3. Pick "Add a rule".
4. Select "minecraftPocketEdition" in the dropdown list and enter the target UDP ports.
5. Save and wait a few seconds for the changes to come into effect.
# java.net.BindException: Address already in use: bind # java.net.BindException: Address already in use: bind
This means something (likely another instance of Geyser) is running on the port you have specified in the config. Please make sure you close all applications running on this port. This is sometimes due to the fact that you doubleclicked the jar instead of running it using a startup script. If you don't recall opening anything, usually restarting your computer fixes this. This means something (likely another instance of Geyser) is running on the port you have specified in the config. Please make sure you close all applications running on this port. This is sometimes due to the fact that you doubleclicked the jar instead of running it using a startup script. If you don't recall opening anything, usually restarting your computer fixes this.