xip.io - Access any dev App via internal IP using a magic domain

[girish]

@robi Do you know if Let's Encrypt certs work with those domains (since LE has limits). Or maybe they have some special agreement with Let's Encrypt to get over the rate limits?

[mehdi]

@girish they resolve to a local IP, so I don't really see how the letsencrypt verification procedure could find your server. Or am I missing something ?

[girish]

@mehdi I think you can put any public IP as well. So you can create a droplet and use it's public IP address.

[robi]

Any IP is usable not just private ones. Hence yes, you can get a LE cert.. try it.

[Lonkle]

@fbartels said in xip.io - Access any dev App via internal IP using a magic domain:

@Lonk said in xip.io - Access any dev App via internal IP using a magic domain:

What’s the benefit over just using the IP though?

Through sni you can host multiple websites on the same ip.

I don’t understand how tho if no two of these “magic domains” can point to the same IP?

[Lonkle]

@robi said in xip.io - Access any dev App via internal IP using a magic domain:

Any IP is usable not just private ones. Hence yes, you can get a LE cert.. try it.

I think I may have a use case for this then! wonder if I could get a wildcard cert for it.

[fbartels]

@Lonk said in xip.io - Access any dev App via internal IP using a magic domain:

I don’t understand how tho if no two of these “magic domains” can point to the same IP?

From the projects homepage:

10.0.0.1.xip.io resolves to 10.0.0.1
www.10.0.0.1.xip.io resolves to 10.0.0.1
mysite.10.0.0.1.xip.io resolves to 10.0.0.1
foo.bar.10.0.0.1.xip.io resolves to 10.0.0.1

So multiple domains can point to the same ip.

[Lonkle]

@fbartels Ohhhhhh. I understand now. Thanks for the explanation. What a cool concept.

[robi]

bumping for a refresher.

[rmdes]

@robi main domain seems to be dead ?

[BrutalBirdie]

@rmdes there is also https://nip.io/

[robi]

@girish said in xip.io - Access any dev App via internal IP using a magic domain:

@robi Do you know if Let's Encrypt certs work with those domains (since LE has limits). Or maybe they have some special agreement with Let's Encrypt to get over the rate limits?

nip.io maps <anything>[.-]<IP Address>.nip.io in "dot", "dash" or "hexadecimal" notation to the corresponding <IP Address>:

dot notation: magic.127.0.0.1.nip.io
dash notation: magic-127-0-0-1.nip.io
hexadecimal notation: magic-7f000001.nip.io

The "dash" and "hexadecimal" notation is especially useful when using services like LetsEncrypt as it's just a regular sub-domain of nip.io