which plugin causes automatic addip by console
Hi Folks
Starting some days ago, I have a little problem on our gameserver. I found out, that the Sourceban installation could get no connection to the gameserver. After checking some logs, I found this in the gameservers console (hlsw), sometimes every two or three minutes, sometimes even twice a second: Code:
Addip: "<><><>" was banned by IP "permanently" by "Console" (IP "xx.xxx.xx.xxx") When I´m running a "naked" gameserver without any plugins, there is no problem, but as soon as I activate sourcemod - zooomm, there it is. Does anybody know, which plugin causes this automatic ban? Can I add the IP to a kind of whitelist? Is there another possibility to stop the bans? Any hints would be nice! |
Re: which plugin causes automatic addip by console
It took me forever to figure out what caused that! Whenever SourceBans can't connect to the game server, it seems to convert into "local" mode, and it saves all of your bans in a sql database. However, there seems to be an issue with it because those bans remain and are never checked again!
To fix this issue, power down your server. Load up your FTP and navigate to /addons/sourcemod/data/sqlite/ and delete sourcebans-queue.sq3. Once you turn your server back on, the constant rebanning will be gone. Just be sure to removeip <affected ips>. |
Re: which plugin causes automatic addip by console
I found the "sourcebans-queue.sq3", including some of the last bans. Unfortunately the IP-Ban I was looking for is not inside.
Anyway, I deleted the file, I deleted the IP in banned_ip.cfg and started the server again. And it happened again... So which plugin can add an IP ban? Where can I configure it? Can I add an "IP-whitelist"? |
Re: which plugin causes automatic addip by console
I'm pretty sure that your issue is still coming from SourceBans; perhaps you need to try deleting everything (.sq3, banned_ips, etc). But for shittles and giggles, please post a rcon sm plugins list so we can see what other plugins you're running.
|
Re: which plugin causes automatic addip by console
here is my list:
Code:
22:41:18 [SM] Listing 42 plugins: |
Re: which plugin causes automatic addip by console
Maybe you configured the rcon password wrong on SourceBans and it's getting autobanned for bad attempts?
|
Re: which plugin causes automatic addip by console
Latest version of sourcebans is 1.4.5, you are at 1.4.2
|
Re: which plugin causes automatic addip by console
@bl4nk: no wrong rcon, this is what I have checked first. And the new set up server works fine, with the same rcon. I did even copy and paste the rcon from the old one to the new one in Sourcebans server-list.
@Antithasys: the connection to the new set up server works fine. Why not with the existing server? Something else must cause the IP-ban. Which plugin or other serverside module can do such a ban? Except of Sourcebans? My problem is, I do not find any reason for this ban, just the ban itself. |
Re: which plugin causes automatic addip by console
Quote:
I am not saying that this is the issue... but it would help the sb devs(me and others) to find the reason if you were on the same version as us. In other words.... update sb and see if it still happens. If so... unload all your plugins and just run the basic version like you mentioned... then add 1 plugin at a time until you find the cause. |
Re: which plugin causes automatic addip by console
We have had this problem before. It's not just SourceBans.
Any plugin that also has a web interface generally uses logaddress_add and tends to send a lot of rcon commands to the server. SourceBans does this very rarely (only when updating the admin cache after adding an admin or changing an admin's privileges, and a few other instances). HLStatsX CE, however, has a perl daemon going on the web server that is sending huge amounts of rcon commands to the server at any given time. Any time you ever change an rcon password for your game server, you have to update the rcon password config entries in the SourceBans and HLStatsX CE web configurations. What happened with us is that we updated the rcon passwords for the servers correctly in SourceBans, but since the HLStatsX CE perl deamons were running on the same webserver as SourceBans is, it was causing the webserver to get banned for failed rcon attempts. This, of course, also borked SourceBans. Once we figured out that you have to stop the HLStats daemonds and update the rcon password for them before restarting it, we were able to get things running properly again. After you've updated those website configs with the rcon passwords and restarted them, you simply delete the ips in the banned_ips.cfg file and everything should work fine. |
All times are GMT -4. The time now is 14:48. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.