You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Socket addresses must be the resolved IP address of the minecraft server. When lazymc stops container, it could come back with a different IP address, which (especially when running multiple servers) can causes issues, you start the "secondary" server and lazymc thinks that the "primary" server started (for no reason). This causes issues.
If we could somehow get lazymc to monitor the server using the DNS name this problem would go away
The text was updated successfully, but these errors were encountered:
Lazymc uses a TcpSocketAddr to monitor the server for the duration of lazymc running
https://github.com/timvisee/lazymc/blob/master/src/util/serde.rs#L27
Socket addresses must be the resolved IP address of the minecraft server. When lazymc stops container, it could come back with a different IP address, which (especially when running multiple servers) can causes issues, you start the "secondary" server and lazymc thinks that the "primary" server started (for no reason). This causes issues.
If we could somehow get lazymc to monitor the server using the DNS name this problem would go away
The text was updated successfully, but these errors were encountered: