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 trying to reverse proxy the Webmin instance behind a Traefik instance, which works as a SSL terminator for the connection, the present configuration does not seem to work.
More specifically, the proxy is achieved by declaring the Webmin instance as not-SSL-enabled (since that is the role of Traefik), but the redirect rules do not respect the protocol. switching from https back to http since that protocol is the one seen by Webmin.
Following is the relevant part of the Docker Compose configuration:
As explained in this issue comment on the webmin repository, this can be achieved by using some more parameters, namely redirect_ssl, webprefixnoredir and relative_redir.
I have a pull request againts this issue, which I shall upload.
It would be truly easy to simply build a new image using this as a base and simply patching the issue, but that would not be good etiquette for the Open Source community. would it?
Thanks for the awesome work!
The text was updated successfully, but these errors were encountered:
Greetings.
In trying to reverse proxy the Webmin instance behind a Traefik instance, which works as a SSL terminator for the connection, the present configuration does not seem to work.
More specifically, the proxy is achieved by declaring the Webmin instance as not-SSL-enabled (since that is the role of Traefik), but the redirect rules do not respect the protocol. switching from https back to http since that protocol is the one seen by Webmin.
Following is the relevant part of the Docker Compose configuration:
After opening correctly the login page on https://my.custom.domain, the login redirects back to http://my.custom.domain:443 which is incorrect.
As explained in this issue comment on the webmin repository, this can be achieved by using some more parameters, namely
redirect_ssl
,webprefixnoredir
andrelative_redir
.I have a pull request againts this issue, which I shall upload.
It would be truly easy to simply build a new image using this as a base and simply patching the issue, but that would not be good etiquette for the Open Source community. would it?
Thanks for the awesome work!
The text was updated successfully, but these errors were encountered: