The console does not load or shows a TLS error
The certificate is issued over port 80, so that port has to reach the server
What you see
- The browser shows ERR_SSL_PROTOCOL_ERROR or SSL_ERROR_INTERNAL_ERROR_ALERT.
- The log says no viable challenge type found, or missing certificate.
- The installer warned that port 80 is not reachable from the internet.
Why it happens
The server gets its certificate from Let's Encrypt, which checks the server over TCP port 80. A closed port 80, a DNS name that points somewhere else, or a proxy in front of the server stops the certificate from being issued or renewed.
-
Check the ports from the internet
This stops the service for a few seconds, has WarpSpeed send test traffic to the server's ports, and starts the service again.
sudo warpspeed check ports -
Open what it reports
It prints the command for firewalld or ufw when one is running. Otherwise a cloud firewall or security group is closed, so allow TCP 80 and 443 inbound from anywhere in your provider's console.
sudo firewall-cmd --permanent --add-port=80/tcp && sudo firewall-cmd --reload sudo ufw allow 80/tcp -
Check the DNS name
The name must point straight at the server's public address. Turn off a Cloudflare proxy (the grey cloud) and remove any second A record.
-
Restart and watch the log
The certificate is requested again on the first visit to the console.
sudo systemctl restart warpspeed sudo journalctl --unit warpspeed --follow -
If port 80 cannot open
WarpSpeed has no other way to get a certificate yet, so run it on a network where TCP 80 reaches the server, and keep it open for renewals.