Skip to content

SSL? #6

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

Closed
davisshaver opened this issue Sep 8, 2017 · 7 comments
Closed

SSL? #6

davisshaver opened this issue Sep 8, 2017 · 7 comments

Comments

@davisshaver
Copy link

Not worried about the security of the content as much as the potential Google Chrome nags in coming months about unsecure pages. Any thought what we'd need to do to support SSL (or even if you'd want to)?

My first batch of notes are here, https://davisshaver.com/2017/09/08/setting-up-pagepark-to-corral-my-unused-domains/, smooth sailing so far! ⛵️

@scripting
Copy link
Owner

I understand. I haven't yet tried to use PagePark with SSL, but I would be interested in finding out what it takes to do so and what if anything needs to change in the server. I'll post a link to this on Scripting News and see if anyone has tried this.

BTW, from reading your post, publicfolder is not a web server. It runs exclusively on the desktop not on the server. But it gives me some ideas on how it might work with PagePark. ;-)

@scotthansonde
Copy link

I'm not familiar with Elastic Beanstalk, but I think the standard way to do this is put a reverse proxy in front of the app to handle the SSL, then the app itself doesn't need any changes. Just for fun I put an instance of river5 behind an SSL proxy (nginx running on the same virtual server as river5). I haven't really maintained it, but it still works :-) https://river5.papascott.de
I can try this with PagePark, I'm pretty sure it would work just as well.

@jsavin
Copy link

jsavin commented Sep 9, 2017 via email

@davisshaver
Copy link
Author

I looked into this today, thanks to @papascott and @jsavin for weighing in, I was able to solve it outside of pagePark. That said, I unwittingly bought a regular SSL cert when I would have needed a multi-domain cert to make this work in my use case. So I'll close this for now but share any more findings I get.

@davisshaver
Copy link
Author

Cloudfront (AWS) ended up working well for this. They have a feature similar to Cloudflare's for upgrading all requests to SSL. In my case, I also added a cname & SSL cert to the load balancer so that the user->Cloudflare & Cloudflare>Load balancer & Load balancer -> Server should all be using 443

@scripting
Copy link
Owner

scripting commented Sep 19, 2017 via email

@scotthansonde
Copy link

Sure, I can take a quick look. BTW ngrok is a cool tool to test SSL on localhost. If you're running a web service locally, it will tunnel it to the internet and generate a random URL on both http and https (for free and without having to sign up).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants