coolprop.org doesn't support HTTPS

[softwareengineerprogrammer]

Most browsers (rightfully) warn when sites don't support HTTPS and make users click through a warning dialog to confirm visiting an HTTP site

[ibell]

Yup - agreed. But getting SSL certs and so on is not free and requires expertise to implement. Want to volunteer?

[softwareengineerprogrammer]

I can possibly volunteer if given access to the relevant infrastructure, I suppose. https://letsencrypt.org/ provides free SSL certs btw, as does AWS, so there probably shouldn't be any cost unless your hosting provider is charging an unusual fee for it.

[ibell]

@jowr do you have some input? Maybe you can coordinate offline?

[jowr]

I have no way of handling this. I do not own the domain and that is where the settings have to be applied. Was it you who owns the domain @Rod-Persky?

[Rod-Persky]

Hi All,

letsencrypt would work, the only requirement is to have the server setup to respond and load the certificate.

The config for DNS points to 216.105.38.10

Happy to help, but this will be something that will need to be done on the server side.

[Rod-Persky]

@jowr : @softwareengineerprogrammer

The DNS hosting is done with name.com if there is a need I'll look into how to delegate maintenance otherwise just let me know if/what changes are required.

Also did you want a custom email domain? There are MX records which I think are pointing to a free Google GSuite account, but in 2022 Google shut all the free GSuite accounts down (who did not transition to paying accounts).

[softwareengineerprogrammer]

@Rod-Persky I can't do anything without access to the name.com account and whatever hosting provider you have. I would start by looking for a guide on how to configure SSL for whatever server implementation coolprop.org is using and following the steps - for example, if it's Apache, this guide looks fine: https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-20-04

[Rod-Persky]

I'm not sure where/how the website is being hosted, but hopefully @ibell or @jowr might be able to follow the guide.

Should the site be hosted on a VM the let's encrypt certbot tools will work perfectly without needing DNS access.

If we cannot get this working easily we can also use cloudflare to do the HTTPS and that will need a dns change. Cloudflare will terminate the HTTPS on their side and proxys the current server.