AuthMe
Country-based Protection conflicting with TCP Shield
What behaviour is observed?
I recently updated to Minecraft 1.21, along with the latest version of AuthMeReloaded. However, I suddenly couldn't join my own server from WAN nor could my friends. We had AuthMeReloaded (with Country Whitelisting) and TCPShield for around 1.5 years now and we never had such an issue.
I've tried adding the TCP Shield IP's country, always seems to be the UK, and it didn't work.
Expected behaviour
It should allow the user to join if the IP is in the whitelisted country or isn't in the blacklisted country.
To Reproduce
Set up country-based protection, add your country's code (Singapore/SG) for mine's, use TCP Shield and get banned from your own server until you disable country-based protection
Plugin list
30.06 14:49:58 [Server] INFO Server Plugins (18): 30.06 14:49:58 [Server] INFO Bukkit Plugins: 30.06 14:49:58 [Server] INFO - AuthMe, CoreProtect, DeathCoordinates, Essentials, EssentialsChat, ExploitFixer, GrimAC, HamsterAPI, LocketteX, LuckPerms 30.06 14:49:58 [Server] INFO ProtocolLib, RHLeafDecay, SkinsRestorer, TCPShield, TradeSystem, Vault, WorldEdit, WorldGuard
Server Implementation
Proxy (TCP Shield)
Database Implementation
MySQL
AuthMe Version
v5.6.0
Error log (if applicable)
No response
Configuration
https://paste.gg/p/anonymous/d3f41bbbe9404f80ad77e01e9ea936f6
What IP address do you see for the users logging into the server? Is it the same?
What IP address do you see for the users logging into the server? Is it the same?
Yes, mostly the same. Also, WHOIS points all those IPs to TCPShield, so I'm 100% sure it's not my side (I don't even have a UK VPN)
Then the TCPShield plugin doesn't expose the real IP address at all or not early enough. Maybe check if it's correctly running like if it's even enabled or was disable due to an error. The best option is to check the server log.
There not a lot we can do here on AuthMe side.