6 ms·
> 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?
by pipo234 3y ago
> 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?
- repelsteeltje 3y agoThat 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) :-)
- pipo234 3y ago:-( Developing on a webserver that runs locally on your desktop is becoming more an more painful.
- valrix 3y agoHave you checked out https://www.getlocalcert.net/ https://www.getlocalcert.net/ yet? They're working on adding more login options than just Github, but they're not quite there yet.
- globular-toast 3y agoUse Firefox. No problems at all here.
- fragmede 3y agoChrome 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?
- Sohcahtoa82 3y agoCouldn'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?
- da768 3y agoYou can even use a DNS challenge and leave the 127.0.0.1 record in place.
- Phrodo_00 3y agoIf you want a CA you can just make a CA and add it to your trusted certificates.
- fragmede 3y agoSplit horizon DNS could work, if you're able to run your own DNS server for your local network.