Locate the verified panel address and username in the service information. Use the hostname assigned by the provider, particularly when a website domain has recently moved. The normal DirectAdmin port is 2222, but your service may use a branded alternative.

1. Open the supplied HTTPS address, such as https://server.example.com:2222, using the actual server hostname.
2. Check the browser certificate and address before entering credentials. An IP-address certificate mismatch should be resolved with the correct hostname, not dismissed automatically.
3. Enter the DirectAdmin username and password and complete additional authentication if enabled. If the client area supplies an authorized panel-login button, open it only from your authenticated service page.
4. Confirm the account and currently selected domain after login. Accounts hosting several domains require the correct domain context for mail, DNS and website changes.
5. If your role can switch levels, select the level needed for the task. Log out when finished and avoid sharing session URLs.

You should see the expected domains and tools for your active plan. A missing administrator menu is normal for a hosting user and does not mean the login failed.

For rejected credentials, use the authorized reset route instead of guessing repeatedly. For a timeout, check the exact server address and whether your network blocks the required port. DNS caches can vary after a change, so do not rely on a fixed propagation promise. Report a certificate mismatch or unexpected destination to support.

• Creating and downloading a full DirectAdmin account backup
• Opening DirectAdmin webmail securely
• Creating a MySQL or MariaDB database in DirectAdmin
• Installing DirectAdmin on a supported Linux server

• DirectAdmin: First Steps