Diagnosing connection issues to your DirectAdmin control panel
Your IP address (216.73.216.181) has been blacklisted by DirectAdmin.
This is the reason you're receiving HTTP 403 Forbidden errors with the "x-directadmin: blacklisted" header.
HTTP/2 401
cache-control: no-cache
content-type: application/json
cross-origin-resource-policy: same-origin
vary: Origin
vary: Accept-Encoding
x-content-type-options: nosniff
x-frame-options: sameorigin
content-length: 93
date: Thu, 15 Jan 2026 04:10:24 GMT
{"client_ip":"94.72.118.163","error":"Not logged in","have_lost_password":"0","success":"no"}
HTTP/2 401
cache-control: no-cache
content-type: application/json
cross-origin-resource-policy: same-origin
vary: Origin
vary: Accept-Encoding
x-content-type-options: nosniff
x-frame-options: sameorigin
content-length: 93
date: Thu, 15 Jan 2026 04:10:24 GMT
{"client_ip":"94.72.118.163","error":"Not logged in","have_lost_password":"0","success":"no"}
HTTP/2 401
cache-control: no-cache
content-type: application/json
cross-origin-resource-policy: same-origin
vary: Origin
vary: Accept-Encoding
x-content-type-options: nosniff
x-frame-options: sameorigin
content-length: 93
date: Thu, 15 Jan 2026 04:10:24 GMT
{"client_ip":"94.72.118.163","error":"Not logged in","have_lost_password":"0","success":"no"}
HTTP/2 405 cross-origin-resource-policy: same-origin vary: Origin vary: Accept-Encoding x-content-type-options: nosniff x-frame-options: sameorigin content-length: 0 date: Thu, 15 Jan 2026 04:10:24 GMT
HTTP/2 401
cache-control: no-cache
content-type: application/json
cross-origin-resource-policy: same-origin
vary: Origin
vary: Accept-Encoding
x-content-type-options: nosniff
x-frame-options: sameorigin
content-length: 93
date: Thu, 15 Jan 2026 04:10:24 GMT
{"client_ip":"94.72.118.163","error":"Not logged in","have_lost_password":"0","success":"no"}
HTTP/2 401
cache-control: no-cache
content-type: application/json
cross-origin-resource-policy: same-origin
vary: Origin
vary: Accept-Encoding
x-content-type-options: nosniff
x-frame-options: sameorigin
content-length: 93
date: Thu, 15 Jan 2026 04:10:24 GMT
{"client_ip":"94.72.118.163","error":"Not logged in","have_lost_password":"0","success":"no"}
Since your IP has been blacklisted by DirectAdmin, you need to contact your hosting provider or server administrator to have your IP removed from the blacklist.
If possible, try accessing the API from a different IP address that isn't blacklisted.
Login to DirectAdmin directly and check the Brute Force Monitor to see if your IP is listed there. You might be able to remove it yourself if you have admin access.
Check your DirectAdmin configuration files for any IP blacklist settings:
/usr/local/directadmin/conf/directadmin.conf/usr/local/directadmin/data/admin/ip_blacklist/usr/local/directadmin/data/admin/ip_whitelistIf your server uses Fail2Ban or ConfigServer Firewall (CSF), check their configurations to see if your IP has been banned by these security systems.
As a temporary workaround, you could use a proxy server or VPN to connect from a different IP address. However, this is not a recommended long-term solution.