-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Players can't join, cause "sub server is offline" (more in explanation) #3515
Comments
Did you set (HOWEVER DO NOT set it to -1 in bungee's config, thats a huge DoS risk and completely unrelated to this problem!) |
currently set to default to 4000. |
You can set it in bungeecord to -1 if you have connection limit with iptables or something else, with iptables it should also be more efficient |
You need to set it to This is written for example as first thing in the Post-Installation section here: https://www.spigotmc.org/wiki/bungeecord-installation/#post-installation Please also read the rest of that section, maybe your spigot servers are not yet secured from outside connections. |
hey, im reading the complete installation part and set the throttle to -1, etc. any ideas |
I do not think there is a problem inside bungeecord. You do have some invasive bungeecord plugins (geyser, protocolize, tablist). I suggest you try without these, or if not possible to seek for further help using spigotmc.org forums (as I don't think there is a problem inside bungee). If you or a dev of your server is capable, add |
Bungeecord version
git:BungeeCord-Bootstrap:1.20-R0.2-SNAPSHOP:9e83ee6:17
Server version
Paper-176 MC:1.20.1
Client version
1.20.1
Bungeecord plugins
AdvancedBan, AntiBot, BungeeTabListPlus, CraftingStore, Geyser-Bungeecord, Luckperms-Bungee, Pl-Hide-Pro, Plan-5.5. Analytics, SCAutoBroadcaster, SlashServer, floodgate-bungee, minimotd-universal, nuvotifier, protocolize-bungeecord
The bug
Due to an unregistered bug, players can sporadically no longer join a sub server.
We use multiple sub servers that can be joined through a hub/lobby server.
4 of the 5 sub servers, including the hub can be entered normally, the forwarding and /send works normally.
The one sub server, no great differences from the others, no plugins that are not also installed elsewhere, but cannot be entered.
The error message is the following from the messages.yml of "server_went_down". The sub server is supposed to be down.
The surprising thing is:
There are already players on it. There are already 30 players on the server, suddenly no new players can join because of the error message. Then the sub server has to be restarted to fix the problem.
Most of the time it works again after a few minutes, so you just have to wait and see.
As mentioned at the beginning, there are no logs about this, except for the message that the player who tried to join is disconnected again.
Log output (links)
there arent any log files, searched the startup logs but there arent issues.
also there arent issues or errors when the players join the server
Checking
The text was updated successfully, but these errors were encountered: