Can't Join Server Unless Super Admin

[[GL] KoreanBiscuit]

Hey I have been searching everywhere for this and the issue I am having is that I am currently running my server with GMChosting and We are currently trying to get everything set up but my friends can't join the server unless I set them as SuperAdmin and if I don't set them as Superadmin it will go to sending client info and then it will kick them back into the loading screen.

I hope some of you can help me with this issue hoping it's a quick fix!

[JamminR]

Sounds like you've set reserved slots too high and/or with incorrect mode.
Your server console should be logging this saying "kicked X due to reserved slot" or something to that effect.

[[GL] KoreanBiscuit]

Hello,

Thanks for the reply I thought that at first but it isn't that it seems if you aren't a superadmin ulx group rank my friend said once you hit sending client info and shows the motd it kicks you off the server and goes back to a loading screen.
I'm not sure if anyone has a solution for this issue but please leave an answer or possible ideas please!

[MrPresident]

Possibly a conflicting mod if you are sure it is not a reserved slot issue.

Try removing ALL of your mods except ULX and see if you can join as a non-superadmin.

If that works, add them back in a few at a time until you find out what is causing it.

[JamminR]

Check server console for messages of why it kicked. ULX logs it, and I'd hope, other addons/subscriptions do the same.

[MrPresident]

The way he worded it "kicked them back into the loading screen" makes me think that it's a disconnect and not necessarily a 'kick'.

It's hard to say, but that's why I suggested removing all addons to find the culprit.

If it were a kick, I would assume there would be a kick message or some kind of a logged event, but he makes it sound like that's not that case.

[genokoenig]

I have had this before, you my friend have a backdoor.

bars

[JamminR]

Though very possible, not absolutely.
We've seen admin mod and addon conflicts cause issues like this far more often than exploits.
Either way, if server log text during the kick could not be searched in text code to determine if it's ULX or which addon, MrPresident's remove all, add back one at a time method would find the offending addon, be it conflicting, or exploited (or perhaps yes even both)