Why Static Websites Need HTTPS

Re:Why Static Websites Need HTTPS by hiccuphippo on Tuesday August 28, 2018 @09:11AM (#17858518)

How can I go about securing a server without a domain? Just a static IP? Let's Encrypt doesn't allow IPs and the owner doesn't care for a domain.

Context: small business with a web based application in a local server, all they need is to be able to access reports from their phone.

[ Parent | on HN ]

Re:Why Static Websites Need HTTPS by detaro on Tuesday August 28, 2018 @09:14AM (#17858537)

Self-signed certificate (or own CA and certificate signed by that). Buying a certificate for an IP is more expensive than a domain.

[ Parent | on HN ]

Re:Why Static Websites Need HTTPS by hiccuphippo on Tuesday August 28, 2018 @09:38AM (#17858671)

I've tried self-signed certificate somewhere else but it seems Chrome doesn't add the certificate permanently so every few days they get the "scary" not secure window again.

I'll try with my own CA.

[ Parent | on HN ]

Re:Why Static Websites Need HTTPS by breakingcups on Tuesday August 28, 2018 @10:53AM (#17859216)

Can I suggest registering a domain for $1, pointing that at the IP and using LetsEncrypt? Probably less effort in the long run.

[ Parent | on HN ]

Re:Why Static Websites Need HTTPS by user9182031 on Tuesday August 28, 2018 @01:54PM (#17861081)

Trusted certification authorities are not issuing DV SSL certificates (with domain verification) for IP-addresses; because it creates certain security threats .

[ Parent | on HN ]