Replies: 2 comments
-
I fixed the first problem there's a page dedicated to this problem. You can find the problem fix here: Anyways, the second problem still occurs, and i figured my proxy server can't dedect the minecraft-server you can find the logs both proxy and minecraft-server down. Proxy server:
Minecraft server:
|
Beta Was this translation helpful? Give feedback.
-
Hi @dodoflix ! This error is handled by the proxy when your connection IP is not the same as the one you used to authenticate to Mojang. In Kubernetes its really common when you do a manual port-forward because Kubernetes will see a local IP, thus not the one used to authenticate. You are saying that you enabled the proxy protocol to fix the issue, it could also be that if it's enabled on your load balancer. For your second issue, may you share the logs of the proxy and server themselves? Agones sidecar logs are not that helpful. I suspect your Minecraft server is taking too much time to boot and is killed due to health issue → do not hesitate to remove sensitive information if you have any in your logs. Thanks |
Beta Was this translation helpful? Give feedback.
-
Hi,
I finally find a chance to install Shulker on my test kube, so i had a strange problem after successfully installed.
So about the problem, I get this error while i try to connect to server:
First of all I have a premium account, I tried to restart my client but it didn't work. Then i thought problem could be about connection to Mojang API, maybe my kube cluster cannot access to Mojang API's then i wanted to change the online mode to false from servers.
And then i tried to reconfigure velocity.toml in configmap but whatever i tried i couldn't save the configmap maybe i did and something re edit automatically the configmap again idk.
So, why the first problem could occur? And how can i fix the second problem of my installation?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions