Skip to content
Discussion options

You must be logged in to vote

The important distinction is that Pangolin/Traefik path rewrite only changes the inbound request before it is proxied upstream. It cannot make the upstream app generate subpath-aware URLs in the browser.

So this part can work:

/browser asks /machine-name-1  -> rewrite/proxy to upstream /

But if the app later makes an absolute request to /api/content, the browser requests:

https://admin.domain.com/api/content

That request no longer has the /machine-name-1 prefix, so it will not match the /machine-name-1 route.

The reliable options are:

  1. Use a subdomain per service, for example machine-name-1.admin.domain.com and machine-name-2.admin.domain.com.
  2. If the upstream app supports a base/public …

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@tealtxgr
Comment options

Answer selected by tealtxgr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants