Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]
 

No, for each server you set the unique server ID in your sourcebans.cfg

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]
 

And inside admin panel on site I see the server id? I cand find a way to connect my webhost to server:((( look, is not working... my webhoster said is not blocked the port: http://profihosting.ro/csgo/index.php

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]
 

HOME » ADMIN PANEL » SERVER MANAGEMENT. You will find the ID near every server you have.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]
 

Yes, i see all servers, and the sourcebans plugin work fine for all, but how i said before, contextual options in web panel for kick, ban, and see player information (or get info for ban in webpanel), only work for the first server in port 27015. And... yes. All servers are well configurated with a unique server ID: 1, 2, 3, 4 etc.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]
 

I can't connect my server with my server, Error connecting... my webhost said all ports are opened:(

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]
 

If anyone doesn't know at this point, I have stopped development on SB++.

If anyone wants to takeover development and they feel they are ready for the task of handling a system used by thousands of Gameservers, please PM me.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]
 

:shock:

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]
 

Also, good luck with taking care of the mess that is the web UI.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]
 

Encountered the same issue. Were you able to resolve it?

Edit:

Nvm, fixed it.

The parse_url fails on some special characters, so if you have special characters in your password, it parses that and fails.

The Future of SourceBans++
 

With Sarabveer stepping down from the active development roaster, I quickly want to state what will happen with SourceBans++.
A few months back we (Groruk and Galexrt) approached Sarabveer to become a part of the SourceBans++ development team.
So there are still people developing SourceBans++, but after a few months with the project, we (and a lot of community members) decided that its the best to start rewriting SourceBans++ from scratch.
This means we are currently actively writing a "SourceBans++ 2.0" which will focus less on JavaScript and 8-year-old code, to provide a more stable and user-friendly experience (we will also take a look at the plugin and try to fix as many bugs as possible).
It can take a few months until the new SourceBans++ is ready for active use because both Galexrt and I are busy with RL (he is working and I'm in university). The current SourceBans++ will get some bug fixes and will move in a deprecated status when "SourceBans++ 2.0" is in a stable form.

I hope this will clear up the future of the SourceBans++ project and if you have any questions or feature requests let me know them via pm, the SourceBans++ GitHub repo or email [email protected].

Also big thanks to everybody helping with the SourceBans++ project really appreciating it.

TL, DR: There are still people developing SourceBans++ and there will be a new "SourceBans++ 2.0" next year.

Thanks,
Groruk