-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Am I doing something wrong? #95
Comments
That looks right. I noticed logging of the mappings was missing, so can you grab https://github.com/itzg/mc-router/releases/tag/1.15.1 and provide the debug logs with that? |
Ok, this time it works but now clients get timed out while trying to join: Both IPv4 and IPv6 btw |
I guess I need add even more logs since I can't tell if the backend server or the client initiated the TCP closure:
Either way I'm pretty sure it's not the router. |
./mc-router -debug -connection-rate-limit 100 --mapping "mc.sientys.cloud=10.0.0.1:25566,mc.goldensmp.net=10.20.220.13:25565"
I am running mc-router standalone and I keep getting WARN[0004] Unable to find registered backend serverAddress=mc.sientys.cloud
same with IPs and all other domains.
The text was updated successfully, but these errors were encountered: