4 ms·
Lvh.me no longer resolving to localhost?
This morning I found that lvh.me is no longer responding to localhost and is instead resolving to 34.98.99.30
Looks like the domain has expired.
Anyone know who the owner is or how I can help in sponsoring getting this set back up again? It's a free tool, but it's used by a lot of developers.
- raasdnil 5y agoGoDaddy are now showing the domain name is expired and parked. Having a bad actor take control of this domain would not be a fantastic outcome.
- raasdnil 5y agoJust did some testing and it seems like the latest Chrome and Firefox browsers both support *.localhost, so this is a good replacement. Works also with port numbers, eg http://example.localhost:3000/ http://example.localhost:3000/
- beprogrammed 5y agoThis seems like a terrible practice, localhost should resolve to localhost a TLD of its own. Having some random entity controlling a domain at the .me TLD, and using that in a processes is just asking for trouble.
- clusmore 5y agoNot an answer to your actual question but you might be able to switch to https://readme.localtest.me/ https://readme.localtest.me/ instead.
- robbiejs 5y agoI don't know lvh.me, but it sounds similar to nip.io and xip.io. If you don't want to rely on a free service to point to your localhost, I recommand ngrok.io. I believe they have a free plan. It works with your virtual hosts as well :-)