You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: