-
Notifications
You must be signed in to change notification settings - Fork 43
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
Enable https on the danse server #1827
Comments
There is some kind of weird rate limit on certificates from let's encrypt, so if you have more than 5 sites you want to cover with one cert, it may take time. https://community.letsencrypt.org/t/maximum-number-of-sites-on-one-certificate/10634 |
That should not be a problem from what I can tell. However the link at the top was for nginx. This gives the instructions for using certbot to automate the install and renewal using the Apache web server and Ubuntu 20.04 LTS (danse 2) |
Current status:
At that point we should consider this ticket closed. I don't think we should try to add https certification to dans1 which is still running lts 14! Instead we should be executing on the server upgrade project described in issue SasView/sasmeta#7 and in particular for this topic under phase II of the wiki pages for upgrading our servers by moving all services off of danse which can then have new drives installed and be upgraded to the latest Ubuntu. |
"At that point we should consider this ticket closed." ----> |
The Danse server needs to have a trusted certificate and https enabled. Browsers are getting increasingly wary of non https sites. There are many services, not all SasView using the server, but the SasView marketplace is one that does for example. So does the old trac site. There may be more? Further, UTK which hosts the machines is cracking down on security issues.
Note that there are services that allow the obtaining of the HTTPS certificate for free. See for example:
https://linuxize.com/post/secure-nginx-with-let-s-encrypt-on-ubuntu-18-04/
besides the certificate it will need to be linked to the apache web server we are using.
The text was updated successfully, but these errors were encountered: