Fix for already connecting ...

[TamataPvP]

Hello this is my 3rd thread for this thing and i still have the problem i still cant fix it
- Some of my players can join everywhere except factions
- Its saying - Already Connected to this server
- if they are using our ip wartic.eu to fix this problem we must give them the ip with the numbers (0.0.0.0 - example)
- if they are using with numbers and its buggy they must use wartic.eu i dont know why this is happening only for 1 of my 4 servers im willing to pay if someone can help me to fix this problem

 

[KingWampy]

Pm me

 

[LordOfTime]

Sounds like you're trying to pizza, when you should really french fry.

Unless you're actually going to try and help, please leave

 

[LordOfTime]

Hahaha, no, this is not a player.dat corruption. If it were, they would have the same joining issues regardless of which IP they used. Note that the OP said there's a difference between different IPs, suggesting it's an issue with either their Spigot interfacing with their BungeeCord, or their Bungee itself.

 

[LordOfTime]

or their firewall, or their host, or a number of things really, and no the problem would not be persistent regardless of which IP they use as there's only 1 IP, the domain simply forwards to the IP. So if they're having issues connecting via domain it only means there's an added potential something is wrong with the domain host configuration or their servers. Whats with the "hahaha" btw? No need to be an ass, I dont see you offering a solution. My suggested approach would take less than 30 minutes to completely do, is free, and has an honest attempt at creating a permanent solution.

The difference is simply that I've been pming back and forth with the OP today Fine, don't refer to it as an IP, refer to it as a connection address, it doesn't change the fact that it's connecting to the same server through different means (connection -> forward through bungee hub -> server, vs connection -> server), to the same server, which makes the theory about the player.dat corruption extremely unlikely, if not impossible, as the same player.dat is used regardless of which method you use to connect. As for the firewall, or the host, neither of those is likely to produce differing results per player, as the OP is presumably hosting all of their servers through the same host, who would use the same firewall setup for all of their servers.

 

[LordOfTime]

If you have a different server version or jar then your other servers this can cause a conflict especially with newer 1.9+ .
For example if your bungee and and lobby and creative servers are 1.9 1.10 and 1.11 then a 1.8 user can't connect to those. Or the other way around depending on your setup. It's hard to explain but basically if you have 1 server that is 1.8 on your network and other servers 1.9,1.7 or 1.11 then there will be a conflict[DOUBLEPOST=1497387195][/DOUBLEPOST]You could also have a 1.9 bungee which sometimes has a conflict with 1.8 users.
This "already connecting" happened on my server many times

Having talked to OP, their versions check out it would appear.

 

[LordOfTime]

Alright what version is their bungee?

"its for 1.7 and 1.8"
It's a custom build, apparently.

 

[LordOfTime]

Most likely the cause

That's what I said, but the OP isn't going to update to it since it's custom, so I just suggested double checking Spigot versions. Haven't gotten a reply yet.

 

[KingWampy]

If a user joins with 1.7 and trys to join a 1.8 server, unless they directly join the server (which most likely has viaversion) they won't be able to connect. If a 1.8 trys to join a 1.8 it will work

If a 1.7 client tried to join a 1.8 server it would probably kick them with a message saying, "Outdated Client."

 

[LordOfTime]

Not if it's a custom or different version of bungee

I would be very impressed if somebody managed to accidentally overwrite the error message in a custom Bungee in such a way so that it acted like the player was already online if they logged in with the wrong version.

 

[LordOfTime]

It says "they are already connecting" which means it's attempting to connect but cannot which is definitely a version issue I'm positive

I've already suggested to the OP that they update their Spigot to 1.8.9, but since they're using a custom bungee there's not much else they can do besides replace it if that doesn't work.