Currently, in the browser version if v6 function is called and the API request returns a v4 version, then an error is made and we can't get the IP.

It'd be good if there's a single function to return IPV6/IPV4, if v6 is available :

console.log(await publicIp.get());
//=> '46.5.21.123' or v6 if available (preferred)

Fixes #45 Added new general HTTPs APIs from which IP is retrieved with a regex pattern. Adds a JSON object to do that :

general: {
  'https://www.cloudflare.com/cdn-cgi/trace': 'ip(=)(.*?)\n',
  'https://ip-api.io/api/json': 'ip"(.*?)"(.*?)"'
}

Some things that could be considered to be useful:

• Multiple DNS resolver host alternatives
• Multiple DNS resolver providers
• Fallback to HTTPS by default if DNS does not resolve (no need to choose one or the other, just try DNS and if it fails use HTTPS)
• Ability to disable or enable HTTPS check ({ https: true } will only check HTTPS). Defaults to DNS + HTTPS
• Added options.urls array to be able to add more urls to fallback to (like ifconfig.co)

might fix #5

@galambalazs Could you try this out? I couldn't test as my current connection is blocking it somehow.

@silverwind This was easier to implement with and support retries so it's more resilient.

See https://github.com/sindresorhus/is-online/issues/64. One or two alternative services to be checked in parallel would probably be beneficial for better resilience against outages.

When starting a fleet of instances (e.g. -i 4) with pm2, and public-ip runs inside each instance upon launch, only the first one succeeds. All the other ones report this error:

[Error: Request timed out]

Example script:

require('public-ip').v4(function (err, ip) {
    if (err) return console.error('no public IP found', err);
    console.log('ip', ip)
});

pm2 start publicIp.js -i 4

Hello,

Since we're reaching the end of IPv4 blocks, it seems like a good idea to support IPv6. This modification seems to do the job, but before continuing I wanted to get your feedback on the direction it's taking since it's obviously a breaking change. Of course you'll need an IPv6 ready network to make the tests pass.

• Uses closure on xhr to avoid referencing the wrong xhr object in the load callback if multiple requests are done in parallel
• Remove the abort method that was not exported so was useless

Closes #52

some organizations use zscaler. This causes some ip resolver services to recognize the zscaler IP instead of the actual user's IP.

This issues is to request the support of overriding the standard ip address resolvers (icanhazip and ipify) with a list of user defined resolvers.

Cannot get IP v6, the service https://ipv6.icanhazip.com/ seems down, or maybe it was moved, anyhow this library is not working for v6 anymore following the examples. The browser displays this error: ipv6.icanhazip.com’s server IP address could not be found. Maybe the service maintainers deleted the DNS for the "ipv6" subdomain.

IP v4 does work.

Testing code:

const publicIp = require('public-ip');
(async () => {
	console.log(await publicIp.v6());
})();

public-ip version: 3.2.0 I submited the issue to major/icanhaz here.

We are using AWS EC2 instance and have implemented node.js server written in hapi js which is deployed using docker. On our development server public-ip library is giving proper result. Now we have setup staging server with similar configuration. Here we are getting below error.

error:  Error: Query timed out
    at DNS._ontimeout (/usr/src/app/node_modules/public-ip/node_modules/dns-socket/index.js:98:18)
    at ontimeout (/usr/src/app/node_modules/public-ip/node_modules/dns-socket/index.js:52:10)
    at wrapper (timers.js:275:11)
    at Timer.listOnTimeout (timers.js:92:15)

Can you please suggest some way out of this issue? Let me know if any further information required.

I tried this line without internet access and after approximately 9 seconds later it return error "Error: Couldn't find your IP" publicIp.v4({timeout:100}).then(value => console.log(value)).catch(err => console.log(err));

I was expecting it to error out within 100 milliseconds, not 9000 milliseconds. Am I missing something?