Hacker News Reader

Comment by pipo234 | Hacker News Reader

> 127-0-0-1.backname.io resolves to 127.0.0.1

Is this enough to fool Edge (Windows 10) into allowing you to view your local Apache development environment?

That should allow access to port 80, maybe. But for TLS, you still need some CA to certify you're you. And you won't be able to convince LetsEncrypt that you control 127-0-0-1.backname.io because it resolves to localhost, which isn't you (from LetsEncrypt's perspective) :-)

:-(

Developing on a webserver that runs locally on your desktop is becoming more an more painful.

Have you checked out https://www.getlocalcert.net/ yet? They're working on adding more login options than just Github, but they're not quite there yet.

Use Firefox. No problems at all here.

Chrome has an exception for requiring tls on localhost for certain services. That, plus an extension to disable CORS on it has gotten me as far as I've needed (so far). What roadblocks have you come across?

Couldn't you bind localhost.yourdomain.com to a public IP, get a certificate, install that certificate locally, then change localhost.yourdomain.com to resolve to 127.0.0.1?

You can even use a DNS challenge and leave the 127.0.0.1 record in place.

If you want a CA you can just make a CA and add it to your trusted certificates.

Not sure if this works for Windows, but the author knows what he is doing and his technique seems fairly well thought out.

https://github.com/FiloSottile/mkcert

+1 for `mkcert`

Works like magic!

Split horizon DNS could work, if you're able to run your own DNS server for your local network.

Reply on news.ycombinator.com