after disabling the proxy protection in the guardian-ban an administrator's aipi from the whitelist, deletion in .htaccess does not help

Уведомление о Блокировке. You have been banned from using this forum permanently by Administrator.

when you press the exit-I is banned with the above notification

Forbidden
You don't have permission to access /cgi-bin/yabb2/YaBB.pl on this server.

yes in the file everything is erased-it does not help, when you press the admin on the output immediately appears a message about the bunt and 3 times the admin's ip appears in the settings of the ban Guardian-I'm tired from there erasing-again 3 times the ipy will wither there

push Exit

Уведомление о Блокировке. You have been banned from using this forum permanently by Administrator.

how do I fix it? -no they come in. Personally, I'm the main admin-root, just clicked to sign out. You were at the forum and got a ban

hurray, earned-deleted from the list of blocking participant-and earned, it turned out he was banned with my ip (since I started it) -something deleted and in the lock list forever for nickname he was

What I was seeing as happening from the logs:

There were 2 logins for user admin from different IP addresses. One from an IP starting with 176. and one from an IP starting with 5.

One of those made an edit that threw an error that was reported here.

Almost immediately after, someone who was not logged in as admin at IP 176 tried to enter the Admin Center. At some point, the 'Guest' at 176 was banned - prossibly by the person logged in as admin at IP 5. Once IP address 176 was banned, 'Guest' at 176 got IP blocked because of repeated rapid errors.

Now, how the supposed admin logged in from IP 176 got logged out and failed to notice is something I can only guess at. I am guessing that their IP address got shifted to something else and then back again. OR they were working from 2 different computers on the same IP address and were logged on one machine and not the other and may have even banned themselves.

And yes, the same IP address can be added multiple times to the Guardian blocked list from the ErrorLog. (Although that's not likely to happen if the problem IP address is added automatically since once the IP address is listed, the problem user can't make any more errors to be automatically blocked.)

IP bans and IP blocks are part of two completely different and unrelated systems. While you're right that a Permanent IP ban on top of an IP block in the htaccess seems redundant, many admins don't use or don't have access to htaccess for IP blocking.

Again: this is what I've pieced together: user admin at IP beginning with 176 IP-banned someone with the same IP address. Therefore the admin got IP banned. This is a known hazard.

Because the admin got IP banned and started throwing errors to the errorlog in a way that mimicked a bad bot trying to break into YaBB, that IP got autoblocked in htaccess.

And changing the exit routine for the IP banning from Profiles as you suggest will cause major issues for the Forum Moderator who does not have access to the Admin Center and does not solve the actual issue: you IP banned yourself.

The admins I've known that have accidentally banned themselves (and it does happen) have either logged in from a different IP and unbanned themselves it or contacted the YaBBForum administrators and asked one of us to log in and unban them. Not one of those admins triggered the autoblock by flooding the errorlog with errors while IP banned.

I may, when I have time, put together some code to check IP bans against the admin's IP list. But then, you're probably the first in YaBB's long history to get autoblocked by the errorlog protections after IP banning yourself.

So, no, not going to try to fix a 'bug' that that doesn't exist but does reveal you do a good emulation of a bot.

The only way an IP can be banned is by a person actually banning that IP either from a member profile OR in Banning Utilities in the Admin Center.

There are 3 separate ban sections - one for user names, one for e-mail addresses, and one IP addresses. Banning an user name does not ban the IP address that user used or their e-mail address. Banning an e-mail address does not ban the user name or the IP address. Banning an IP address does not ban any user names or e-mail addresses.

Banning a user name, e-mail address, or IP address does not make changes to Guardian or htaccess files.

Deleting a member does not affect what bans are in place, nor does it make changes to Guardian or htaccess files.

Therefore: while you claim a user name was being banned, that cannot have banned their IP address UNLESS SOMEBODY CHANGED THE CODE IN THE BANNING SECTON. And if that happened, that's not YaBB's fault nor is it a bug within YaBB.

All other problems you reported, including the changes in Guardian and the htaccess file, came from banning that IP address.

You IP banned your own IP address. But now it's MY fault because YaBB can't anticipate people doing dumb things?

Over the many years YaBB has been around, other admins have IP banned themselves but, to my knowledge, you're the first one to not only IP ban yourself but trigger the IP blocker in the errorlog. And this is not once but repeatedly.

DON'T BAN YOUR OWN IP ADDRESS