Topic Summary - Displaying 15 post(s). Click here to show all
Posted by: Dandello Posted on: Jan 23rd, 2018 at 7:51pm
Going over your video again, you have not been banned. The warning popping up indicates you are trying to register someone using a user name or e-mail address that has been banned.
Check your banlist to make sure the user name for your new member isn't in the user name part of banlist. (You didn't show checking that part in the video, only banned IP addresses. The reference to 'admin' in that list only indicates it was user 'admin' who did the banning.) Also check to make sure that part of 'banned' user's email address is not in the banlist.
from the banlist HERE:
Code
173.231.39.42 - Tue Jan 6 02:23:18 2015 by Dandello (admin) - Permanent
That IP address was banned BY ME on the date and time listed and was a permanent ban. I was not banned. I did the banning.
Posted by: Dandello Posted on: Jan 22nd, 2018 at 6:32pm
I am hoping to have the SVN updated by the end of the week.
I have really think about how to do White-listing as it will affect two different major code sections (Banning and Guardian).
Posted by: Rucola Posted on: Jan 22nd, 2018 at 6:12pm
just have their own problems with the Russians. We are contributing our own changes-and how can we forget anything when releasing a new version?
Posted by: Rucola Posted on: Jan 22nd, 2018 at 6:10pm
right now I thought maybe in the admin center to make a whitelist like when banning a call from a proxy? enter new tab-whitelist but how will understand your correction, who is the administrator and who is not the administrator? and then we send it to the admin-won admin as there was an Ex Participant and stayed-and after all we corrected it and you wrote it and it was in the first message to the new user and it remained-displayed as Administrator (Ex-Participant)
just so as not to forget that it is corrected that there is not in the new versions a white list to be registered in the Admin Center.
Posted by: Dandello Posted on: Jan 22nd, 2018 at 2:36am
Okay, I can't figure out how this is happening. However, you can block banning of the admin by editing Security.pm.
Find
Code (Perl)
&& $banned ne '127.0.0.1'
Add beneath it :
Code (Perl)
&& $banned ne 'admin'
&& $banned ne 'not to be banned IP'
replace 'not to be banned IP' with the IP address that you're white-listing.
Posted by: Dandello Posted on: Jan 22nd, 2018 at 12:34am
What does the YaBB error log say? And what does tha ban log say?
Posted by: Dandello Posted on: Jan 22nd, 2018 at 12:29am
Look for that IP address in Variables/banlist.db. 'admin' cannot be banned from their Profile page, but someone with access to the Ban Utilities in the Admin Center could, conceivably, ban user 'admin' that way.
Posted by: Rucola Posted on: Jan 21st, 2018 at 11:18pm
the error is some kind of strange-if you disable the check-guards and add to the file-vseravno such a lock on the output-this is the first time I see not an ipy wrote banned. and-your name is in the black list-login? -nik? -what name? -admin ?
Posted by: Rucola Posted on: Jan 21st, 2018 at 11:16pm
swill everything, I blinked, I checked the beginning of blocking users-this is htaccess, and then I checked the Guardian blocking list-it's just the second file in ftp-everything on video-work as you can see, I can-but I can not create new users ( second video) -and by pressing the exit I get to the ban-write-your name is in the black list and not the ip, after the call through the vpn-neither in the first nor in the second file, the ip is not added-there is something to happen by pressing the button, I trust you try to enter my login password but api will be your-can will work, and this effect will not be followed-check? -click where to send my login password?
Posted by: Dandello Posted on: Jan 21st, 2018 at 10:45pm
What I saw on the video - you checked to make sure the IP address in question was not in the .htaccess. Then you tried to log in or tried to access the Admin Center and were told you were banned from the forum. Unless I blinked, you never got to the Admin Center because your IP address had been banned.
These are two different systems, two different files, and you only checked one of them.
Banning does not ever happen automatically. SOMEONE banned that IP address.
Posted by: Rucola Posted on: Jan 21st, 2018 at 10:07pm
you do not seem to understand the ip either in this or in that file and by clicking the exit everything happens-I created the same video because I press the output-writes in the bath and does not give anything-the files are clean, after calling through Vn all gives and went to my Aipi to work on the forum gives a create a new user does not give out the admin panel-but with vpn it allows to create
Posted by: Dandello Posted on: Jan 21st, 2018 at 8:46pm
You are confusing two different lists: Banned is from WITHIN YaBB - open Variables/banlist.db and make sure that IP address is not IN THAT FILE.
However, if the the IP address IS IN THAT FILE, then YaBB can put that IP address in the .htaccess if the banned user keeps trying to get in.
Posted by: Rucola Posted on: Jan 21st, 2018 at 3:59pm
not add new user
Posted by: Rucola Posted on: Jan 21st, 2018 at 3:24pm
after that, the call is possible only with vpn and after that the main ip. 128. added to the guardian, with what is added if both the douche adguardian and write in htaytsess are removed
also when trying to add a user through the admin panel from the address 128. writes-your name is in the black list
Posted by: Rucola Posted on: Jan 21st, 2018 at 3:21pm