Skip to content
Documentation navigation

Start here

Product

Integrations

SDK

MCP

Custom domains

Before you start

Use one hostname per workspace, such as https://feedback.correla.app/, to serve your public board at the domain root. Only the workspace owner can save, verify, replace, or remove it. Custom domains do not change your board's submission settings, customer permissions, or branding rules; see Public boards.

DNS ownership and HTTPS readiness are separate. Upweight reads your verification TXT record; it never changes customer DNS. Managed HTTPS is automatic for every verified custom hostname. Domains are advertised only while the current verified claim has ready, unexpired TLS; platform links remain available during setup or errors.

Managed certificate renewal is automatic. Keep both your ownership TXT and HTTPS certificate DNS records in place so Upweight can continue verification and renewal.

Use the direct DNS setup shown in settings. A traffic CNAME routes requests to Upweight; the separate certificate DNS record allows HTTPS to be issued for your hostname. Neither replaces your ownership TXT record.

Save your hostname

Open workspace settings on the main Upweight site. In the custom-domain section, enter only the hostname, such as feedback.correla.app, and save it. Do not enter https://, a path, a port, an IP address, or a wildcard. Upweight lowercases the hostname and accepts one trailing dot; unsupported Unicode and reserved platform or local-only names are rejected.

Saving a new hostname creates a pending claim and generates a verification value. A pending claim does not serve the board. Saving an unchanged hostname in settings (including case-only or trailing-dot changes) preserves verification and HTTPS state. Replacing or explicitly rotating the claim requires the latest proof value.

Publish the verification TXT record

Create a TXT record in your DNS provider using the name and value shown in settings. For the example hostname, the full record name is:

_upweight-verification.feedback.correla.app

The exact value has this form:

upweight-domain-verification=<generated token>

Replace <generated token> with the current generated token from your workspace settings; the placeholder is not a usable verification value. Some providers expect a name relative to your DNS zone rather than the full name. Check the resulting full record name to avoid appending the zone twice. Keep the complete value in one TXT record.

Upweight only reads this record. It never changes your DNS or checks ownership by fetching a customer URL.

Verify ownership

Choose the verification action in settings. The DNS check runs asynchronously; wait for the result before trying again. If the record is not visible yet, allow DNS propagation and retry. A missing, mismatched, timed-out, or failed lookup leaves the claim unverified.

Verified means DNS ownership verified, not HTTPS ready. Once ownership is verified, continue with the traffic and HTTPS DNS records below. You do not need to verify ownership again. Verification cannot activate a hostname already verified by another workspace; resolve that claim with the other workspace owner or contact support.

Configure traffic and HTTPS DNS

Settings shows the exact record type, full name, and value for your hostname. Copy those values rather than using a target from another workspace or a generic application hostname. If instructions are still being fetched, check back shortly; do not guess the targets.

  • Board traffic: use the recommended record type shown in settings to route your hostname directly to Upweight. For a CNAME, remove conflicting A or AAAA records at that name; a CNAME cannot coexist with those records. If settings instead shows A or AAAA records, add all displayed addresses and remove any CNAME at that name. Do not point your hostname at upweight.dev.
  • HTTPS certificate: add the recommended certificate CNAME for ACME delegation. This is a separate record that allows certificate issuance and renewal. Use the exact name and value shown in settings.
  • Alternative records: settings may show another ownership record as an alternative. It is not universally required and is not needed when using the recommended records. It does not replace your Upweight verification TXT record.

For Cloudflare, set the displayed traffic records and the certificate CNAME to DNS only, not proxied (orange cloud). The certificate record is independent of whether traffic uses CNAME or A/AAAA records. Keep the Upweight ownership TXT record in place.

Record names in settings are fully qualified. If your DNS provider automatically appends your zone, enter only the part before the zone. Check the final full name to avoid adding the zone twice.

Wait for HTTPS readiness

DNS updates can take time. Upweight checks automatically after ownership verification. Wait for HTTPS active in settings before sharing the custom hostname; your platform URL stays available during setup. Keep the traffic, ownership, and certificate DNS records in place.

If settings says the certificate request is being checked, you can still configure the displayed DNS records. DNS changes do not resolve every certificate request issue; contact support if the notice persists.

Public routes and customer sign-in

On a verified customer hostname, the supported public paths are:

PathPurpose
/Public feedback board
/roadmap and /roadmap/:statusRoadmap and status views
/board/new and /board/:feedback_slugSubmit feedback and view a request
/auth/signin and /auth/signupCustomer sign-in and sign-up
/auth/magic/:tokenEmail sign-in callback
/auth/sessionSign in with POST; sign out with DELETE
/accountCustomer account
/changelog and /changelog/:post_slugPublished updates

Required static assets and the /live transport are supported. Marketing pages, owner settings, administration, billing, APIs, MCP, and platform OAuth are unavailable on customer hosts. Use the main Upweight site for those features. Workspace-slug-prefixed paths are not alternate routes on the customer hostname.

The direct DNS setup preserves the original Host and supports WebSocket upgrades for live updates. If you add a reverse proxy, it must preserve both; forwarding requests to a workspace URL path is not a substitute for the custom-host setup.

Customer cookies are host-only: signing in on upweight.dev does not sign the customer in on your hostname. Request a fresh email sign-in link for the intended site; links are bound to their workspace and approved origin. Existing customer authorization and submission rules still apply.

Replace or remove a domain

Replacing or removing the hostname immediately revokes the old custom-host mapping and disconnects its active connections. Replacement or intentional proof rotation requires the new verification value; an unchanged settings save is a no-op. Old custom-host sessions and sign-in links must not be reused; customers should sign in again after setup.

The canonical workspace URL, such as https://upweight.dev/correla/board, remains available. After removal, newly generated public links fall back to the canonical workspace URL. Update links you have already shared. Contact support if HTTPS setup remains unavailable rather than repeatedly replacing the domain.

Troubleshooting

  • TXT missing or mismatched: confirm the full name, copy the newest generated value exactly, and allow propagation. A value from before a save or replacement will not verify.
  • Already verified elsewhere: a pending claim does not reserve a hostname, but only one workspace can have the verified mapping. Resolve the existing verified claim before retrying.
  • 404 on the customer hostname: confirm verification is current, the requested path is public, and ingress preserves the original Host. Unknown, pending, and removed hostnames are rejected.
  • TLS errors or 502 responses: check that traffic and certificate records match settings exactly and are DNS only. A traffic CNAME must not coexist with A or AAAA records; when settings shows addresses instead, keep those A/AAAA records and remove any conflicting CNAME. Ownership verification alone does not make HTTPS ready. Use your platform URL until HTTPS is active; contact support if setup remains unavailable.
  • Live updates or reconnects fail: ensure ingress supports WebSocket upgrades and the browser Origin uses the same scheme, hostname, and port as the transport request. Do not rewrite the request to the platform hostname.
  • Sign-in fails after a change: request a fresh link on the intended hostname. Canonical and custom-host sessions are independent.

Last reviewed