Skip to main content
Domains on Pxxl go through three layers before traffic reaches your app: DNS resolution, edge proxy routing, and SSL certificate coverage. A problem at any one layer produces a different symptom — a 404 means the proxy has no route for the hostname, a 503 means the route exists but the upstream is unhealthy, and a certificate warning means the proxy has not yet issued or refreshed the cert. Use the accordions below to find the symptom that matches your situation and follow the fix steps.
A 404 means DNS is pointing to Pxxl, but the edge proxy has no application route registered for that hostname.Fix steps
1

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.
2

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.
3

Confirm the deployment is active

Check that the latest deployment finished successfully. A healthy upstream must exist before the proxy can return a response.
4

Wait for DNS and proxy setup to finish

If the domain was just created or just attached to a project, give the system a short moment to complete DNS and proxy setup, then refresh the page.
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 PORT environment 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.
Fix steps
1

Open the project

Go to Dashboard > Projects and select the affected project.
2

Check the port in Settings

Open the Settings tab and confirm the port value matches the port your app binds to at runtime.
3

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.
4

Redeploy the project

If the container image needs to pick up the new port value, trigger a new deployment.
5

Resync the proxy

Open Dashboard > Domains, select the domain, and click Resync Proxy so the edge picks up the updated upstream target.
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
GoalRecord typeNameValue
Root domainA@193.181.212.65
SubdomainAapp or your subdomain label193.181.212.65
Wildcard subdomainsA*193.181.212.65
Avoiding conflictsRemove any existing A records for the same host before adding the Pxxl records. If @ 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.
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 Proxy
  • 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, www redirect behaviour, or WebSocket support.
Fix steps
1

Open the domain

Go to Dashboard > Domains and select the affected domain.
2

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.
3

Check the SSL tab

Open the SSL tab and click Renew / Resync if you want to verify certificate stage and expiry directly.
4

Test the domain

Wait briefly, then reload the domain over https://.
Expected SSL state after a successful resync
FieldExpected value
CoverageCovered
TLSEnabled
BrowserNo certificate warning
URLhttps://yourdomain.com loads successfully
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
1

Open the project

Go to Dashboard > Projects and select your project.
2

Open the Domains tab

Click the Domains tab inside the project.
3

Add the domain

Click Add Domain, then choose an existing Pxxl domain or enter an external domain.
4

Save and resync

Save the connection, then click Resync Proxy on the domain if the route needs refreshing.
From the domain
1

Open the domain

Go to Dashboard > Domains and select the domain.
2

Open Settings or Subdomains

Click the Settings or Subdomains tab.
3

Pick the project

Select the project that should receive traffic for this domain.
4

Save and resync

Save the connection, then click Resync Proxy.
For subdomains, enter only the subdomain label when the UI asks for it. Use api for api.example.com.
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.
1

Open the domain detail page

Go to Dashboard > Domains and click the new domain.
2

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.
3

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.
4

Click Resync Proxy

Click Resync Proxy on the domain detail page to push the route to the edge.
5

Check SSL coverage

Open the SSL tab and confirm the coverage shows Covered. If it does not, click Renew / Resync and wait a moment.