You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In an older version, it was possible to configure a reverse proxy to wg-portal under a secondary, internal domain name. This is not possible anymore, only the external url, defined in config.yml, is able to authenticate to the ldap backend.
I tried to hack around this with Nginx, but ultimately could not succeed.
Should this be possible?
The text was updated successfully, but these errors were encountered:
In an older version, it was possible to configure a reverse proxy to wg-portal under a secondary, internal domain name. This is not possible anymore, only the external url, defined in
config.yml
, is able to authenticate to the ldap backend.I tried to hack around this with Nginx, but ultimately could not succeed.
Should this be possible?
The text was updated successfully, but these errors were encountered: