Blacklist won't disable

[Illarane]

Hi,

This is fairly serious as DirectAdmin is blocking the system we use to check our servers for vulnerabilities. I've unticked the "Blacklist IPs for excessive login attempts" box in Administrator Settings and clicked save, which tells me it's been appended to the task queue. DirectAdmin gets restarted fine, but the blacklisting doesn't actually get disabled.

There's no reference to ip_blacklist in /usr/local/directadmin/conf/directadmin.conf and bruteforce is set to 0, yet the tickybox is still ticked and IPs are still being blacklisted. Anyone got any ideas as to how to fix this?

Thanks,

Ben.

 

[daveyw]

If you don't see any IPs located in 'ip_blacklist' file then its not blocked by DirectAdmin. Maybe you got a firewall running that is blocking the IP-addresses.

All IPs located in 'ip_blacklist' can't login to DirectAdmin but still can connect/login to server

 

[Illarane]

Hi, Dave,

The problem isn't the fact that the IP addresses are being added to the blacklist; it's that I can't disable the blacklist. I've unticked the box next to the text field and saved the form, and I've received the message telling me that the task will be executed shortly. Except it isn't.

DirectAdmin gets restarted and the box is still ticked. The main directadmin.conf file has the blacklisting stuff switched off, and there's no ip_blacklist option in there at all, so I'm really quite stuck. My boss is giving me hassle because DirectAdmin blocks the security scanning software we're using from accessing it (I've found two things which put DirectAdmin at odds with United Kingdom card-processing legislation already, so he does actually have a point, for once), so I need to figure out how to disable it.

Ideas, anyone? :/

Ben.

 

[nobaloney]

Check to make sure your cron daemon is working. Check to make sure the reuest is being added to the task.queue.

Jeff

 

[Illarane]

Hi, Jeff,

The anacron was working properly, as was the insertion into dataskq. However, the DirectAdmin process wasn't actually getting restarted, or, if it was, the new settings weren't taking effect.

I ran `killall directadmin` then started it manually, and the new settings finally took effect. I can only assume that the init script forgot the process ID, or similar. Perhaps it would be worth implementing a NOHUP-triggered config reload? This would have the added advantage the DA process would not need to be interrupted to make configuration changes as it does currently.

Will try to work out why the restart wasn't happening properly and post back here at some point. I'd imagine it'll happen again at some point, so I'll keep and eye out and let you know.

Regards,

Ben.