-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
traefik configs with xnat for https and owner certs #89
Comments
Hello @uaengr, I have an issue with using the features/dependency-mgmt branch for deployment. This branch uses Traefik, but I am unable to configure my own wildcard SSL certificate generated by GoDaddy. To work around this issue, I made the modification docker-compose file to port 443, mounted the certificate to the Traefik docker, and changed the traefik configuration. However, when I access the website from a browser, it uses the Traefik default certificate instead of my SSL certificate. Please respond, any help would be greatly appreciated. |
Amarjeet, |
A little late here, but in case someone else comes across this. I'm in the process of rebulding our setup, but we did have traefik working with our own local certs. It's lenghty (sorry), but here's is how I set it up. fwiw, it was a while ago, but I remember the traefik settings being particularly difficult - it was also unclear (still) if traefik.toml or traefik.yml is read/precedence order so I just left both in. The xnat-traefik and xnat-web sections of my working docker compose:
Then in traefik/config I have our-ssl-certs.yml, traefik.toml and traefik.yml as below:
traefik.toml (don't think this is used)
traefik.yml
|
The configuration of traefik to use https is non trivial I would like to see a working example of XNAT+traefik+OwnCerts
The setup we require needs XNAT to be secured via SSL certs serverd over https:
I considered dropping traefik and using nginx as a reverse proxy, but am unsure of the ramifications..
This should be easy, according all the hype about traefik, but I am not able to get it working. Nor can see where in the logs there are issues.
The text was updated successfully, but these errors were encountered: