I’m currently experimenting with the Permitted Paths option of Pritunl Zero.
I found a major issue, completely destroying the experience and wonder wether this is a misconfiguration on my side or a design decision:
When using permitted Paths, requests allowed by it (everything addressed to a permitted path) will be built differently than the requests issued by a regular, authenticated user.
One quick example: I’m running Nextcloud behind Pritunl Zero. The Moment i add the nextcloud sharing paths to permitted paths, the URLs returned by nextcloud (i.e. hrefs for Buttons, etc.) will change to the internal IP, pritunl used to acces the service, but not the public Domain. This will make the site unusable. Also: Nextcloud will no longer recognize the requests as issued by a reverse Proxy (which would mean, that you set the trusted_proxy to the pritunl-zero host and the trusted_domains option to the public DNS), but instead interpret it as a direct request issued by nextcloud (recognized Domain is no longer DNS, but instead the internal IP). Nextcloud behaves correct when permitted paths are unset.
Am I the only one having this issue or is this known?
Thanks in advance you guys!