Domain or HTTPS not working: checklist

Address not found, Minecraft still wants a port, certificate missing, 502 Bad Gateway, too many redirects: the usual causes and fixes.

2 min readUpdated 2026-09-24Diese Anleitung auf Deutsch lesen →

The address is not found

  • New address or record: wait up to an hour, run ipconfig /flushdns (Windows), or try mobile data.
  • Record name entered as play.yourdomain.com instead of play: many providers append the domain, so check with nslookup.
  • Record saved at the wrong provider: DNS counts only where your domain's nameservers point (visible at your registrar).

Minecraft Java still asks for a port

  • The SRV name must be _minecraft._tcp.play for play.yourdomain.com, and the port must be your server's port.
  • The target must be a name with an A or CNAME record, not an IP address.
  • Bedrock and all other games do not read SRV records; they always need the port.
  • The free penguhost.com address sets all of this up automatically.

HTTPS stays at "Live · HTTP"

The certificate can only be issued when your domain points to us:

  • The A record points somewhere else, or an extra AAAA record exists: fix it, then click Enable HTTPS now.
  • Cloudflare shows an orange cloud: switch it to DNS only (grey).
  • A CAA record that does not allow letsencrypt.org: add 0 issue "letsencrypt.org" or remove the CAA record.

502 Bad Gateway

Our proxy reaches your server, but nothing answers on that port:

  • the app is not running (check the console),
  • wrong port (Advanced → Web server port in the Domains tab Website proxy),
  • the app listens on 127.0.0.1 instead of 0.0.0.0,
  • the app speaks HTTPS itself: switch it to plain HTTP, we do HTTPS.

Too many redirects

Your app redirects http to https itself, but from our proxy it always receives http. Turn the app's own redirect off (we already redirect), or let it read the X-Forwarded-Proto header.

The wrong website shows up

An old A or AAAA record, or the browser cache. Check with nslookup and try a private window.

Still stuck? Open a ticket with the domain and a screenshot, or ask Kowalski in the panel to check the DNS records for you.