Stop repeated attempts and identify the exact error
If DirectAdmin login is not working, first check that you have the correct panel address and hosting account. A rejected login, a page that returns to the sign-in form and a message that your IP is blocked can have different causes. DirectAdmin documents possible causes including an incorrect password, browser cookies, a changing client IP address and server-side login protection; the exact behaviour depends on the installed version and configuration.
Do not keep retrying when the page reports a block or you are unsure of the password. Firewall changes, blacklist edits, server-level password resets and DirectAdmin configuration changes are administrator tasks. For a Novasean shared-hosting service, use the known client-area route to raise a support request instead of trying server commands.
Verify the panel address and the account you are using
Open the DirectAdmin link from a trusted bookmark or, if your service displays one, from the authenticated Novasean client area for the affected service. Check the full hostname before entering credentials. If neither route identifies the panel address, ask Novasean support through the authenticated client area to confirm it before entering credentials. If you are uncertain that a login page is genuine, follow the hosting-login authenticity checks first.
Use the DirectAdmin account details for the particular hosting service. The client-area, mailbox and DirectAdmin logins are separate account contexts; do not assume that a password for one will authenticate the others. Check the service name or domain attached to the account, and avoid guessing between several saved usernames or passwords.
Check credentials without exposing or repeatedly changing them
Check for an accidental space, a different keyboard layout or Caps Lock, then compare the username with the details for this hosting service. If you use a password manager, confirm that its entry belongs to this exact panel hostname and service. Do not paste a password into a support ticket, email or chat.
If you no longer know the DirectAdmin password, use only a reset route that Novasean confirms for your account, or contact support through the authenticated client area. Do not run a root-level password command or change another DirectAdmin user. A shared-hosting login is not authority to administer the server.
If DirectAdmin returns you to the login page
DirectAdmin's technical documentation identifies a changing client IP address, filtered cookies and an inaccurate client or server clock as possible causes of session problems. If you switched between Wi-Fi, mobile data or a VPN while signing in, return to one trusted connection and check that your device date and time are set correctly. Make sure the browser allows the panel site to store its login cookie. Do not disable security checks or change server settings.
If the loop continues after one careful check, stop repeating the login and record the time and exact browser message. The issue may need a server-side check; support can decide what to investigate for the affected service.
If the page says your IP is blacklisted
Stop trying to sign in and contact Novasean through the known client-area route. DirectAdmin's Brute Force Monitor can block an address after repeated failed login attempts; the threshold and any automatic removal behaviour depend on server configuration. Its own documentation warns that, in some configurations, even requests to the login page may count towards protection limits.
Do not try to remove yourself from a server blacklist, edit firewall rules, add yourself to an allow-list or disable brute-force protection. Those changes require administrator access and can weaken protection for the server. Ask support to check the specific service and advise the next safe step. Do not rely on a generic “wait 15 minutes” or other fixed unblock time.
Give support enough detail to diagnose the login
Open or continue a ticket through the authenticated client area. Include the affected domain or service identifier, the DirectAdmin username if known, the exact error text, when it occurred with the time zone, the panel hostname and whether you changed networks or VPN during sign-in. A redacted screenshot can help if it contains no personal message content or credentials. If support asks for your current public IP to investigate a reported block, send it only through the authenticated support route.
Never send your password, one-time authentication code, backup code or private key. For help writing a safe ticket and keeping its evidence in one thread, see how to raise a support request safely. To interpret the reply and ticket state, see the support-ticket status guide.
Frequently asked questions
Should I keep retrying if the password looks correct? No. Confirm the panel address and account once; if the error persists or reports a block, stop and ask support to check it.
Why might a successful login return to the sign-in page? DirectAdmin documents session conditions that can include changing client IP addresses, browser cookie handling and clock differences. These are possibilities, not a diagnosis of your account.
Can I unblock my IP in DirectAdmin? Do not edit server blacklist files or firewall settings unless you are the authorised administrator for that server. For Novasean shared hosting, ask support through the authenticated client area.
How long will an IP block last? The duration depends on the server configuration. Novasean does not promise a universal unblock time in this guide.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.