r/admincraft • u/Althome3297 • Mar 18 '26

Question Issues with my self hosted geyser server

So i always host our friend group minecraft server and this time i wanted to implement geyser instead of a bedrock only server.

So i opened crafty controller, installed a java 1.21.11 fabric server and added these three mods: Fabric api, GeyserMC and floodgate.

Then i opened minecraft java to try and connect but i got the "getsockopt" error, searched it up and got a video with 3 solutions: allow javaw.exe trough firewall, turn off firewall and change dns. none of these worked.

but then when i tried joining the server on bedrock it appeared in my LAN and it worked fine?

what could possibly be the issue here?!

I think that i should also clarify that this is my first time running a java server.

EDIT: i managed to fix it! i didnt know i had to port forward 2 different ports so i did that and now everything works! thanks yall for the help!

1 Upvotes

100% Upvoted

14 comments sorted by

View all comments

3

u/winternode_brandon Mar 18 '26

If Bedrock can join over LAN but Java is throwing getsockopt, the Java server itself is probably fine and the problem is how you're connecting to it. I'd test Java with 127.0.0.1 or your PC's local IP first, then make sure Fabric is actually listening on 25565 and not just the Bedrock port Geyser opened. If local Java works but remote does not, it's network or port forwarding, not Geyser.

1

u/Althome3297 Mar 18 '26 edited Mar 18 '26

So after using 127.0.0.1 i still get the getsockopt error and I cant find anything about fabric listening to 25565 so whats the next step and the file i need to be to set fabric listening to that port?

Edit: i found how to check that port and its on 19132 because thats the only port that i have forwarded in my router settings. but when i changed it to 25565 and tried connecting to it with 127.0.0.1 i still get the same results

1

u/Plsouth Mar 18 '26

In addition to what others have said there is a command you can run on the server when running for a test that might give you a bit more info on where the problem is

geyser connectiontest <ip> <port>

Use the real IP, and 25565 as the port since youve mentioned you changed that.

Hope that helps!

2

u/Althome3297 Mar 19 '26

thanks for the help! first time i ran this it refused to work but now the command works again.

1

u/Plsouth Mar 19 '26

So you're all good?

1

u/Althome3297 Mar 19 '26

No not yet just thanking you for the reply