#Geyser Suddenly Not Working
23 messages · Page 1 of 1 (latest)
Spigot
0.0.0.0:19132 (internal IP)
***:25565
FLOODGATE
4172-Spigot-342f493-a437019 (MC: 1.20.6)
Yes
Ive double checked my firewall and ports so idk what could be the problem
And when attempting to connect geyser dosent even notice the Bedrock client trying to join as ther is no messages about the player trying to join in console
Portforwarding and Firewall screenshots
It was working fine this morning but when I boot the server up after some maintanence around noon to update some plugins Geyser included Geyser refuses to work at all. I can only join the Java server through LAN games on bedrock
Ive had this issue before with Geyser breaking after an update, but I don't remember the solution or if there is a new one. And its getting old that everytime I update this critical plugin its a 50/50 gamble on if itll stop half my playerbase from being able to play
Same here
this looks correct
Also, given that you are able to join via LAN, this is likely a portforwarding issue.
I'd recommend the following:
- see if you can join the server using your PC's local ipv4 address (instead of the LAN tab)
- check if your public ipv4 might've changed
Ive done that, I have tried joining using the local ipv4 because thats what I use normally and my ip should of not changed because I have a static IP provided by my ISP
Ive redone all my portforwarding and firewall settings for the bedrock connection and nothing works. Ive had this happen before after updating the .jar file with a new one. This only happens when I update thew .jar what the heck is going on?
does joining with the local ipv4 work, or not?
No
It dosent
I dont get what the problem is when geyser worked pre update but suddenly it refuses to work post update
but pre update I could join using both local ipv4 and external ipv4
You leveled up to level 3!
could you run ipconfig in your powershell & sending the output here?
Ethernet adapter NIC1:
Connection-specific DNS Suffix . : hsd1.in.comcast.net
IPv6 Address. . . . . . . . . . . : 2603:300f:ac9:100::76d5
IPv6 Address. . . . . . . . . . . : 2603:300f:ac9:100:cdaf:44a4:47cc:3fa3
Link-local IPv6 Address . . . . . : fe80::cdaf:44a4:47cc:3fa3%3
IPv4 Address. . . . . . . . . . . : 10.0.0.96
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::ba5e:71ff:feff:b9eb%3
10.0.0.1
Ethernet adapter NIC3:
Connection-specific DNS Suffix . : hsd1.in.comcast.net
IPv6 Address. . . . . . . . . . . : 2603:300f:ac9:100::8b4e
IPv6 Address. . . . . . . . . . . : 2603:300f:ac9:100:5048:37e:9de:248f
Link-local IPv6 Address . . . . . : fe80::5048:37e:9de:248f%8
IPv4 Address. . . . . . . . . . . : 10.0.0.98
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::ba5e:71ff:feff:b9eb%8
10.0.0.1
Ethernet adapter NIC2:
Connection-specific DNS Suffix . : hsd1.in.comcast.net
IPv6 Address. . . . . . . . . . . : 2603:300f:ac9:100::3509
IPv6 Address. . . . . . . . . . . : 2603:300f:ac9:100:6c79:f0f0:3a42:5ce4
Link-local IPv6 Address . . . . . : fe80::6c79:f0f0:3a42:5ce4%9
IPv4 Address. . . . . . . . . . . : 10.0.0.97
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::ba5e:71ff:feff:b9eb%9
10.0.0.1
Ethernet adapter vEthernet (Broadcom NetXtreme Gigabit Ethernet #2 - Virtual Switch):
Connection-specific DNS Suffix . : hsd1.in.comcast.net
IPv6 Address. . . . . . . . . . . : 2603:300f:ac9:100::193
IPv6 Address. . . . . . . . . . . : 2603:300f:ac9:100:d99d:9c93:e409:3eb
Link-local IPv6 Address . . . . . : fe80::d99d:9c93:e409:3eb%6
IPv4 Address. . . . . . . . . . . : 10.0.0.99
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::ba5e:71ff:feff:b9eb%6
10.0.0.11```
sorry about the emojis i tried to get rid of them : 100 : should be what they say
wrap that with ``` that'll make it look nicer :p
It looks like you have multiple local ip addresses on that PC, I'd recommend to try connecting with those locally - maybe that'll work?
I've seen issues in the past occuring with multiple network adapters present on windows; sometimes you need to test all of them and see which one works.
Specifically:
- try uncommenting the
address: 0.0.0.0field - change that 0.0.0.0 address to one of the local ip's you have
- restart
- try connecting with that one
If that doesn't work, try the next one, and so forth. This should at least resolve the issue with not being able to connect locally
That fixed everything actually thanks for the help 😄
Post is tagged with Answered