![]() |
|
Guide Can't Open the BillionMail Dashboard? Login URL, Ports and Firewall Fixes - Printable Version +- AdminsForum (https://adminsforum.com) +-- Forum: Free & open-source control panels (https://adminsforum.com/Forum-free-open-source-control-panels) +--- Forum: aaPanel (https://adminsforum.com/Forum-aapanel) +---- Forum: aaPanel Guides & Tutorials (https://adminsforum.com/Forum-aapanel-guides-tutorials) +----- Forum: aaPanel BillionMail Guides (https://adminsforum.com/Forum-aapanel-billionmail-guides) +----- Thread: Guide Can't Open the BillionMail Dashboard? Login URL, Ports and Firewall Fixes (/Thread-guide-can-t-open-the-billionmail-dashboard-login-url-ports-and-firewall-fixes) |
Can't Open the BillionMail Dashboard? Login URL, Ports and Firewall Fixes - JAY - 10-23-2026 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:
Code: ls -d /www/dk_project/dk_app/billionmail/billionmail_* /opt/BillionMail 2>/dev/null
docker ps --format "{{.Names}}" | grep -i billionmailCode: billionmail_xxxx-core-billionmail-1Check 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: https://your-host:HTTPS_PORT/SAFE_PATHCode: grep -E '^HTTPS_PORT|^HTTP_PORT|^SafePath' .envCode: bm.shCode: lsCode: bash bm.sh defaultCode: https://your-host/Check 2: Is the port open?
Code: curl -kI https://your-host:HTTPS_PORT/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: docker ps -a --format "table {{.Names}}\t{{.Status}}" | grep -i billionmailCode: docker logs --tail 50 CONTAINER_NAMECode: docker compose restartCheck 5: Port conflicts If the Code: coreCode: ss -tlnp | grep -E ':80 |:443 |:8080 'Code: nginxCode: httpdCode: .envCode: HTTP_PORTCode: HTTPS_PORTCode: docker compose up -dCheck 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
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
Applies to BillionMail 4.9 installed through aaPanel or the install script, October 2026. |