Troubleshooting domains and HTTPS

"No DNS record found yet"

Symptom: Check DNS finds no record.

Cause: The A record is missing, in the wrong DNS zone, or not propagated yet.

Fix:

1. Add an A record: name @ (apex) or the subdomain part (e.g. app), value = the IP on the Domains tab.
2. Edit it at the provider your registrar's nameservers point to.
3. Wait a few minutes (up to the record's TTL) and Check DNS again.

"DNS points somewhere else"

Symptom: Check DNS lists other IPs.

Cause: Old A/AAAA records, a CNAME, a parking page, or a proxy (Cloudflare orange cloud) answers for the name.

Fix:

1. Remove other A, AAAA and CNAME records for that name.
2. Keep one A record with the IP from the Domains tab.
3. Cloudflare: switch to DNS only, or use the proxied setup in Custom domains and HTTPS.

Certificate warning in the browser

Symptom: "Your connection is not private" or a certificate for the wrong name.

Cause: The certificate isn't issued yet, Certificate is None, or Let's Encrypt validation failed.

Fix:

1. Make sure Check DNS passes; certificates need DNS pointing at MarvX.
2. Edit the domain: HTTPS on, Certificate Let's Encrypt, save (this redeploys).
3. Revisit after a minute. With Cloudflare proxying, use DNS only.
4. If the domain has CAA records, allow letsencrypt.org.

Let's Encrypt rate limits

Symptom: Still no certificate after DNS is right, especially after many attempts.

Cause: Let's Encrypt limits certificates and failed validations per domain over time.

Fix:

1. Fix DNS, then stop adding, removing or re-pointing the domain.
2. Wait about an hour (failed validations) or up to a week (certificate limits).
3. Contact support with the domain if it persists.

"Routing error" badge

Symptom: A red Routing error badge on the domain.

Cause: The domain was saved but routing couldn't be applied.

Fix:

1. Click Deploy; routing is reapplied on every deploy.
2. Contact support if it stays after a successful deploy.

502 Bad Gateway or 404 on a working domain

Symptom: DNS and HTTPS work but the page fails.

Cause: The app isn't reachable on its port, has no successful deployment, or the path doesn't match.

Fix:

1. 502: listen on 0.0.0.0:$PORT (or the domain's Container port) and check Logs for crashes.
2. 404: confirm a successful deployment and that the request path matches the domain's Path.
3. Strip path off: your app gets /api/users; on: it gets /users.

www works but the apex doesn't (or the reverse)

Symptom: Only one of www.example.com and example.com loads.

Cause: Each hostname needs its own domain entry and A record; MarvX doesn't redirect between them.

Fix:

1. Add domain for the missing hostname and create its A record.
2. Do any www/apex redirect in your app or at your DNS provider.

"is already connected to an app"

Symptom: Adding a domain fails with this message.

Cause: A hostname can be connected to only one app across MarvX.

Fix:

1. Remove it from the other project first.
2. If you don't control that app, contact support.

Free domain doesn't load

Symptom: The sslip.io domain doesn't respond or warns about the certificate.

Cause: The redeploy applying it hasn't finished, the app isn't deployed, or no certificate could be issued.

Fix:

1. Wait for the redeploy on the Deployments tab and make sure the app deploys successfully.
2. If HTTPS still fails, use your own domain or contact support.