-
Notifications
You must be signed in to change notification settings - Fork 34
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
Adding HTTPS on Prod version #214
Conversation
Added certs and open both port 80 and 443. Port 80 will redirect to port 443.
Deploy Link: http://45.33.71.174/ |
The autogenerating openssl is cool Seems like the redirect is redirecting to Also, just wondering, how would we specify custom ssl certificates? |
Oh, that's weird... I'll double-check with my end on this. |
Ah I did not, only the |
Wait, what does that mean? |
So the issue is the |
So now said that's a deployment issue? Nothing wrong with the code. It's just that this deployment thing isn't (like you said) not overriding. |
Yes, unfortunately we'll need to fix that before we merge or its going to break on subsequent pull requests. tagging @jshom re: the |
Deploy Link: http://173.255.231.178/ |
Added certs and open both port 80 and 443. Port 80 will redirect to port 443.
Deploy Link: / |
Niiiiiiiiiice! Good stuff man! 🎊 Two small tweaks to get this to work with our temp and other environments:
|
Deploy Link: https://23.239.14.246/ |
Added certs and open both port 80 and 443. Port 80 will redirect to port 443.
oi, the build info link... this is fine for now, will make another issue for this, no need to fix it in this PR (this would need to stick to http) |
Yeah. But this is weird. I think 3 days ago, I couldn't get into port 443 on the old URL: |
Ye maybe, I think that could have been a flaky build too. |
Deploy Link: http://45.79.183.91/ |
Deploy Link: https://45.79.171.4/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm bad with bash and certificates so ill defer to @jshom but looks good to me
Small thing from a glance, seeing file |
What changed on the README? I was planning to add more stuff on how to obtain a cert and issue it to a CA for free.
It's alright! I didn't know if what I implemented was what you guys had in mind! |
Added certs and open both port 80 and 443. Port 80 will redirect to port 443.
WOOOHOOO, thing works. Gonna open new issue to address nginx tweaks for protocols & ciphers to address the test. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After removal of the csr check line for provided key/cert, and small whitespace fixes; good for merge!
Deploy Link: https://45.33.88.96/ |
Deploy Link: https://97.107.142.48/ |
Features Added
I added certs and open both port 80 and 443. Port 80 will redirect to port 443. Also made it auto-generate the OpenSSL certificate every time it reruns.
Additional Info
https://tech.osteel.me/posts/docker-for-local-web-development-part-5-https-all-the-things#generating-the-certificate
https://www.digitalocean.com/community/tutorials/how-to-create-a-self-signed-ssl-certificate-for-nginx-in-ubuntu-16-04