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
The point of prevent-client-proxy-connections is to prevent connections where the client's IP address from the proxy's perspective is different from the IP address used to authenticate with Mojang's servers. This makes sense for most use cases, but not for connections across a private network because Mojang will never see the private IP address, and will always prevent the connection.
I think that an exemption should be made for connections from private networks so that this feature can still be used for players connecting from the public internet while not blocking players connecting over a private network (such as a VPN).
Actual Behavior
Player fails to authenticate with the usual "You are not logged into your Minecraft account..." message.
Steps to Reproduce
To reproduce this, the client must be attempting to connect to the Velocity server with a private IP (e.g. 10.0.0.1), but the client and proxy must have different public IPs when connecting to Mojang's servers. This is a common configuration when using a VPN.
Plugin List
None
Velocity Version
Velocity 3.3.0-SNAPSHOT (git-09f687e5-b413)
Additional Information
I've been running a patch with the change I mentioned above and can submit a PR if this is acceptable.
The text was updated successfully, but these errors were encountered:
Expected Behavior
The point of
prevent-client-proxy-connections
is to prevent connections where the client's IP address from the proxy's perspective is different from the IP address used to authenticate with Mojang's servers. This makes sense for most use cases, but not for connections across a private network because Mojang will never see the private IP address, and will always prevent the connection.I think that an exemption should be made for connections from private networks so that this feature can still be used for players connecting from the public internet while not blocking players connecting over a private network (such as a VPN).
Actual Behavior
Player fails to authenticate with the usual "You are not logged into your Minecraft account..." message.
Steps to Reproduce
To reproduce this, the client must be attempting to connect to the Velocity server with a private IP (e.g. 10.0.0.1), but the client and proxy must have different public IPs when connecting to Mojang's servers. This is a common configuration when using a VPN.
Plugin List
None
Velocity Version
Velocity 3.3.0-SNAPSHOT (git-09f687e5-b413)
Additional Information
I've been running a patch with the change I mentioned above and can submit a PR if this is acceptable.
The text was updated successfully, but these errors were encountered: