Skip to content
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

SSL Encryption for the hosted service on Rallly.co #30

Closed
nprail opened this issue Apr 1, 2017 · 2 comments
Closed

SSL Encryption for the hosted service on Rallly.co #30

nprail opened this issue Apr 1, 2017 · 2 comments

Comments

@nprail
Copy link

nprail commented Apr 1, 2017

As I said in #29, it would be great if the Rallly.co hosted service had SSL encryption. It's almost expected these days for websites to have SSL and some potential users may not use Rallly because it doesn't have SSL.

This could be a simple and free change. Or it may not be. It depends on where Rallly.co is hosted. Based on a DNS lookup I'm going to guess that it is hosted on a Digital Ocean Droplet using Express directly. That makes SSL easy.

I would recommend using Let's Encrypt. I would also recommend reverse proxying the Express server with Caddy , Apache, or NGINX in a production environment. This improves security and makes SSL easier. I would highly recommend Caddy because SSL is automatic with Let's Encrypt.

@nprail
Copy link
Author

nprail commented Apr 1, 2017

Here is an example Caddyfile. This assumes that you are running Rallly on port 3000. Instructions for running Caddy as a daemon are here.

rallly.co {
    tls hello@rallly.co

    errors {
        log ../error.log
    }

    proxy / 127.0.0.1:3000 {

        transparent
    }
}

You may need to setup DNS challenge properly for your configuration. Instructions for that are here.

@nprail
Copy link
Author

nprail commented Feb 5, 2020

I see that Rallly.co is now secured with TLS!

@nprail nprail closed this as completed Feb 5, 2020
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

1 participant