Domain shows 404
Domain shows 404
A 404 means DNS is pointing to Pxxl, but the edge proxy has no application route registered for that hostname.Fix steps
Connect the domain to a project
Open Dashboard > Projects, select your project, go to the Domains tab, and confirm the domain appears there. If it does not, click Add Domain and attach it.
Resync the proxy
Open Dashboard > Domains, select the domain, and click Resync Proxy. This tells the edge to re-read the route and create a certificate request for the hostname.
Confirm the deployment is active
Check that the latest deployment finished successfully. A healthy upstream must exist before the proxy can return a response.
Domain shows 503
Domain shows 503
A 503 means the proxy has a route for the hostname, but the upstream app is not healthy or the registered port does not match the port your app actually listens on.Before you change anything, check:
- The latest deployment finished successfully.
- The project port in Settings matches the port your app listens on.
- The app reads the
PORTenvironment variable when one is provided. - The domain is attached to the current project.
- The proxy route was resynced after the last port or domain change.
Check the port in Settings
Open the Settings tab and confirm the port value matches the port your app binds to at runtime.
Correct the port if needed
Update the port to match your app’s listener. The proxy can only route to the port Pxxl registered for the container; if the values differ, the route exists but traffic never reaches the app.
Redeploy the project
If the container image needs to pick up the new port value, trigger a new deployment.
DNS records are wrong or not resolving
DNS records are wrong or not resolving
For domains managed by Pxxl, DNS records are handled automatically from the domain page. For external domains, configure the records at your registrar or DNS provider.Required records
Avoiding conflictsRemove any existing A records for the same host before adding the Pxxl records. If
| Goal | Record type | Name | Value |
|---|---|---|---|
| Root domain | A | @ | 193.181.212.65 |
| Subdomain | A | app or your subdomain label | 193.181.212.65 |
| Wildcard subdomains | A | * | 193.181.212.65 |
@ already points to another server, replace it with 193.181.212.65. Duplicate A records for the same hostname cause unpredictable routing.PropagationDNS changes can take a few minutes to propagate globally. If the record looks correct but SSL still fails immediately after you made the change, wait a few minutes and then click Resync Proxy again on the domain page.For subdomains, enter only the subdomain label in the DNS provider UI. Use
api to create api.example.com — not api.example.com.SSL certificate is missing or wrong
SSL certificate is missing or wrong
If your domain loads but the browser reports a missing, expired, or mismatched SSL certificate, you need to ask Pxxl to resync the proxy certificate for that domain.When to use Resync ProxyExpected SSL state after a successful resync
- You just pointed a domain to Pxxl.
- You recently connected a domain to a project.
- The site loads over HTTP, but HTTPS shows the wrong certificate.
- You bought a domain on Pxxl and DNS records are correct, but the SSL tab still shows missing coverage.
- You changed the project connected to a domain.
- You changed proxy SSL settings such as Force HTTPS,
wwwredirect behaviour, or WebSocket support.
Click Resync Proxy
Click Resync Proxy in the domain actions area. Pxxl refreshes the proxy route and requests a dedicated certificate via SNI. You do not need to redeploy your project to refresh SSL.
Check the SSL tab
Open the SSL tab and click Renew / Resync if you want to verify certificate stage and expiry directly.
| Field | Expected value |
|---|---|
| Coverage | Covered |
| TLS | Enabled |
| Browser | No certificate warning |
| URL | https://yourdomain.com loads successfully |
Connect a domain to a project
Connect a domain to a project
Purchasing a domain and deploying a project are separate actions. A domain only receives traffic after it is attached to a project.From the project
From the domain
For subdomains, enter only the subdomain label when the UI asks for it. Use
api for api.example.com.After buying a domain on Pxxl
After buying a domain on Pxxl
After payment is confirmed, Pxxl starts the registration and DNS setup flow. Once the domain appears in your dashboard, complete these steps to make it live.
Confirm DNS is managed by Pxxl
Check that the DNS management indicator shows Pxxl is in control of the nameservers. If registration is still pending, wait for the domain task to finish before expecting DNS or SSL to work.
Connect the domain to a project
Attach the domain to the project you want to serve traffic. See the “Connect a domain to a project” section above if you need detailed steps.
