Put your KB on your own domain: the three setups

·

The public KB can live on whatever domain suits you. There are three setups, simplest first. In every case, enable the public KB and set the Public base URL to the address visitors will use.

Setup 1 — your instance host (zero setup)

Your instance already answers on its own hostname with a valid certificate, so /kb is reachable there immediately. Example: https://helpdesk.yourmsp.com/kb. No DNS, certificate, or proxy work — just enable the KB and set the base URL to that host.

Setup 2 — a dedicated subdomain

Use a subdomain such as kb.yourmsp.com:

  • Point the subdomain's DNS at the instance.
  • Add the hostname to the instance's certificate and to its allowed hosts so it is accepted, then point that server block at the app.
  • Set the Public base URL to https://kb.yourmsp.com.

Setup 3 — under your marketing site

Serve the KB at https://yourmsp.com/kb by reverse-proxying from your main site. On that site's web server, proxy /kb (and /uploads/kb/ + /uploads/branding/ for images) to the instance, rewriting the Host header to the instance's allowed host. Set the Public base URL to https://yourmsp.com.

Because absolute URLs come from Public base URL, the proxied Host only has to match the instance's own allowed host — not the public domain. When proxying, expose only /kb and the KB/branding upload paths, never all of /uploads/ (that would leak private ticket attachments).

Was this article helpful?
Still need help? Contact SummitPSA support.