exposing the minecraft ports, hoping that bungeecord can reach them.setting server.properties/server-ip= to localhost and the IP of the vm.starting bungeecord before minecraft, and vice versa.changing the port that bungeecord listens on and the corresponding docker port.changing the minecraft server ports in server.properties and corresponding values in config.yaml.In both cases, the minecraft GUI shows that it can see the bungeecord server. In both environments, I get this when connecting to containerized bungeecord:ĭisconnected with: Could not connect to a default or fallback server, please try again later: io.$AnnotatedConnectException That makes me think that I'm either missing something in the configs, or am misunderstanding something to do with docker networking. Notice that the minecraft logs don't indicate connection activity. I am able to connect to the containerized mc server directly in either env. However, when containerized, the proxy doesn't seem to be able to reach the mc server. When running the jar files directly on the host, or in the VM, I'm able to connect without issue. I've been trying for a couple days now to get the bungeecord proxy to connect the backend spigot server. I wanted to include logs and configs up front. Contact your server admin for more details.Sorry in advance for the text wall. : disconnected with: Kicked whilst connecting to 1.18.1_survival: This server has mods that require Forge to be installed on the client. I checked out the problem with BungeeCord and reported the error message: During the test, it was found that the client cannot contact the sub-server normally, but if the client directly connects to the sub-server, there is no problem. I built a new BungeeCord server, the sub-servers are all minecraft version 1.18.1, and the server core is Arclight.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |