[JAY]

Can't open the BillionMail dashboard? Login URL, ports and firewall fixes

BillionMail installed without errors, but the browser shows "This site can't be reached", a blank page, or a login that won't accept your password. Work through these checks in order; most people are back in within five minutes.

First, find your BillionMail folder and containers. Most commands below run from the BillionMail folder:

• aaPanel Docker install:
  Code:Copy

  /www/dk_project/dk_app/billionmail/billionmail_XXXX
  (the last part is random)
  
• Script install: usually
  Code:Copy

  /opt/BillionMail

Code:Copy

ls -d /www/dk_project/dk_app/billionmail/billionmail_* /opt/BillionMail 2>/dev/null docker ps --format "{{.Names}}" | grep -i billionmail

The second command lists the containers, with names like

Code:Copy

billionmail_xxxx-core-billionmail-1

.

Check 1: Are you using the right address?
The dashboard address has three parts: the host, the HTTPS port and a secret path (the "safe entrance"):

Code:Copy

https://your-host:HTTPS_PORT/SAFE_PATH

See your values in the BillionMail folder:

Code:Copy

grep -E '^HTTPS_PORT|^HTTP_PORT|^SafePath' .env

If the folder contains

Code:Copy

bm.sh

(run

Code:Copy

ls

), it can print the full address and login details for you:

Code:Copy

bash bm.sh default

On aaPanel installs the ports are often not 80 and 443, because aaPanel's own web server may already use them. Opening

Code:Copy

https://your-host/

without the port and path is the most common mistake.

Check 2: Is the port open?

• In aaPanel, open Security and add the HTTPS port (and HTTP port) if it's missing.
  
• Check your provider's cloud firewall too; it sits in front of aaPanel's.
  

From your own computer:

Code:Copy

curl -kI https://your-host:HTTPS_PORT/

A timeout means a firewall blocks it. "Connection refused" means nothing listens there (see Check 4).

Check 3: Cloudflare
If your domain uses Cloudflare with the orange cloud, the proxy only passes a few HTTPS ports (443, 2053, 2083, 2087, 2096 and 8443). Any other custom port simply won't load through it. Set the mail host record to DNS only (grey cloud). Mail records must be DNS only anyway.

Check 4: Are the containers running?

Code:Copy

docker ps -a --format "table {{.Names}}\t{{.Status}}" | grep -i billionmail

Every container should say Up. If one says Exited or Restarting, look at its log:

Code:Copy

docker logs --tail 50 CONTAINER_NAME

Restart everything from the BillionMail folder:

Code:Copy

docker compose restart

Once you're back in, Settings > Service shows the same containers with Restart buttons, handy for next time.


Check 5: Port conflicts
If the

Code:Copy

core

container won't start, another program may already use its port:

Code:Copy

ss -tlnp | grep -E ':80 |:443 |:8080 '

If

Code:Copy

nginx

or

Code:Copy

httpd

holds the port, change BillionMail's port in

Code:Copy

.env

(

Code:Copy

HTTP_PORT

/

Code:Copy

HTTPS_PORT

) to a free one, run

Code:Copy

docker compose up -d

, and open the new port in the firewall.

Check 6: Browser warning about the certificate
Until you apply a Let's Encrypt certificate, BillionMail uses a self-signed one, so the browser warns you. That's expected on a fresh install: click Advanced > Proceed, then fix it properly with BillionMail SSL and hostname fix.

Check 7: Login page loads but you can't get in

• Forgot the password or username: in the BillionMail folder,
  Code:Copy

  bash bm.sh change-password
  or
  Code:Copy

  bash bm.sh change-user
  (if your folder has bm.sh).
  
• Still using the default login? A fresh install from the official script starts with a well-known default username and password. Change both, and the safe entrance path, under Settings > Common Settings > Security Settings straight away.
  
• Blocked after too many attempts: BillionMail uses fail2ban to block repeated failed logins. Wait, or try from another connection. Check with
  Code:Copy

  tail -n 30 logs/fail2ban/fail2ban.log
  .
  
• IP whitelist turned on and your IP changed:
  Code:Copy

  bash bm.sh cancel-ip-limit
  turns the console IP whitelist off again.
  

Still stuck? Post in this section with the output of Check 1 (hide your domain if you like), Check 4, and what the browser shows.

Sources: BillionMail on GitHub · Cloudflare: network ports


More BillionMail troubleshooting

• Port 25 blocked: emails not sending
  
• SSL certificate won't apply
  
• DKIM fails although the record exists
  
• Emails stuck in the send queue
  
• Webmail (Roundcube) problems
  
• Emails going to spam
  
• Update safely and roll back
  

Applies to BillionMail 4.9 installed through aaPanel or the install script, October 2026.