[bug report] Gluetun public ip check will fail, for all eventually...

[iPromKnight]

🤪 Sanity check

• I have searched and confirmed no existing open/closed issues exist for this bug

1️⃣ Description

The gluetun ipinfo.io public ip check will fail as those are all lookups via the vpn to get the current IP for every user using the system.

If everyone has the same vpn server selected (pia), those 30k allowed public clls per month to ipinfo.io are going to fail (its shared with the entire gluetun userbase I guess).

Given the low number of vpn servers each provider has, this will eventually become a widespread issue

This results in an unhealthy - restarting gluetun container.

2️⃣ Expected Behaviour

As a user, I'd expect that gluetun containers should start up within my tenancy performing requests using my own ipinfo.io token, so that i'm using my own pool of requests.

3️⃣ Actual Behaviour

As a user, my requests are shared with the other users of the vpn I am connected to

4️⃣ Steps to Reproduce

Run gluetun as its currently configured.

5️⃣ Possible solutions

PUBLICIP_API_TOKEN as a configurable option allows us to provide our own values for ipinfo.io lookups.
The account to get one of these tokens (from https://ipinfo.io/account/token) is free for 50k requests per month

Each user subscribing to gluetun should probably get one of these accounts, and it should be made a mandatory configuration value.

6️⃣ Relevant Information

https://github.com/qdm12/gluetun-wiki/blob/e74f645ff302f299217d703cb7fac1a94de0c9fd/setup/options/others.md?plain=1#L13

qdm12/gluetun#2190

💬 Your Discord username

iPromKnight

💍 Engagement

• Test the changes after a preview deploy and provide feedback
• Solicit community input in Discord
• Submit a PR for a fix myself 🏆

✅ Code of Conduct

• I agree to follow this Geek Cookbook's Code of Conduct