Tutorial cover

Domains, HTTPS and apps behind a proxy

Ports and domains

ports: are not published on the server. Services are reachable only through domains: open the project → Domains, choose the service and its internal port, and get an HTTPS address. Inside the project, services talk to each other by service name (http://backend:8080).

Your own domain

A domain bought anywhere (shop.example.com or example.com) can open a service of your project. The service needs a domain from the step above first; your domain goes the same way, without redeploying.

  1. Project → Domains → Own domains: enter the domain and choose the service.
  2. Add the records shown there at your domain registrar:
    • TXT _jambotron.<your domain> with the shown token — it proves the domain is yours;
    • CNAME to the service domain for a subdomain (www, shop…), or A to the shown IP for the root domain. One of them, not both;
    • remove AAAA records of the domain: Jambotron is reachable over IPv4 only, and the HTTPS certificate is not issued while an AAAA record points elsewhere.
  3. We check DNS every 10 minutes for 72 hours, or right away with Check now. When the records are found, the domain works over HTTPS; the certificate is issued on the first visit.

Up to 5 own domains per project. If the domain later stops pointing to Jambotron, it is marked DNS moved and disconnected after 7 days.

Applications behind a proxy

Requests reach your app through an HTTPS proxy. The app must trust the X-Forwarded-Proto and X-Forwarded-Host headers, otherwise redirects go to http:// and CORS checks fail with 403.

  • Spring Boot: server.forward-headers-strategy: framework;
  • Express: app.set('trust proxy', true);
  • other frameworks: enable "trust proxy" / forwarded headers.
Back to list