Struggling to understand how to associate domain over SSL for SEQ (domain is working over SSL, SEQ is running over HTTP ) #2359
-
|
Hi - I have really spent time trying to understand where I'm going wrong with this, so It's not for the lack of trying - I just really need some help at the final hurdle please. I have SEQ running on a docker container (on ubuntu) over http and it's all working as it should (ingesting logs etc) via http://myDomain.com (not https). The domain has a certifcate via Lets Encrypt (ngnix and certbot on same ubuntu instance) and when visiting it via https://myDomain.com, it displays the standard Ngnix page (Welcome to nginx!) over SSL. The part I'm really struggling with is how to associate the https with the SEQ docker instance. I've looked though the docs, searched everywhere and I just can't understand how to take the next step and link them up. Any pointers from someone in the know would be very much appreciated, thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi! This will require configuring nginx as a reverse proxy so that the SSL connections arriving on port 443 are passed through to the Seq Docker container on port 80. Check out nginx's |
Beta Was this translation helpful? Give feedback.
-
|
That's a huge help, thank you. I was getting tunnel vision over the SEQ settings and just needed a push (kick) in the right direction - thank you so much! |
Beta Was this translation helpful? Give feedback.
Hi! This will require configuring nginx as a reverse proxy so that the SSL connections arriving on port 443 are passed through to the Seq Docker container on port 80. Check out nginx's
proxy_passdirective, and also, if nginx is running in a container you'll have some additional Docker networking issues to look at before the nginx container will be able to reach the Seq one). HTH!