Tailwidget API - Not Fetching IP Info

[BBT-nZ]

Description

I'm probably not the first and maybe not the last. But this has driven me to insanity, so hoping someone much smarter here can be a helping hand. Thanks in advance.

Environments:

1. Proxmox> Ubuntu Server VM> Docker/Docker Compose> Homepage
2. Proxmox> Ubuntu Desktop VM> Docker/Docker Compose> Homepage
3. Proxmox> Ubuntu Server VM> CasaOS> Homepage

At one stage, by some miracle (I cannot recall the setting of the VM's) precisely, but it was Ubuntu Desktop VM with simple docker installed on it via terminal. It did manage to work and I had it working for nearly x2 weeks before I decided to clean up my VM and start things fresh as was just testing homepage to ensure all works as desired.

However, now I'm stuck against the error below like a concrete wall driving me to insanity!

API Error: Unknown error
URL: https://api.tailscale.com/api/v2/device/devicerandomtext
Raw Error:
{
"code": "ENETUNREACH"
}

### homepage version

latest

### Installation method

Docker

### Configuration

```yaml
- Tailscale:
        icon: tailscale
        href: https://login.tailscale.com/admin/machines
        ping: https://login.tailscale.com/admin/machines
        description: Tailscale Admin Console
        widget:
          type: tailscale
          deviceid: xoxoxoxoxoCNTRL
          key: apikeyapkikey

Container Logs

]
[2024-11-29T01:41:46.314Z] error: <credentialedProxyHandler> HTTP Error 500 calling https://api.tailscale.com/api/v2/device/nfFp5sbaYk11CNTRL
[2024-11-29T01:41:46.315Z] error: <httpProxy> Error calling https://api.tailscale.com/api/v2/device/ntx9XB9Ete11CNTRL...
[2024-11-29T01:41:46.315Z] error: <httpProxy> [
  500,
  AggregateError
      at internalConnectMultiple (node:net:1114:18)
      at internalConnectMultiple (node:net:1173:5)
      at Timeout.internalConnectMultipleTimeout (node:net:1632:3)
      at listOnTimeout (node:internal/timers:571:11)
      at process.processTimers (node:internal/timers:512:7) {
    code: 'ENETUNREACH',
    [errors]: [
      [Error], [Error], [Error],
      [Error], [Error], [Error],
      [Error], [Error], [Error],
      [Error], [Error], [Error],
      [Error], [Error], [Error],
      [Error]
    ]
  }

Browser Logs

No response

Troubleshooting

On Host

ubuntu-desktop@ubuntu-desktop:~/Docker/homepage$ curl -H "Authorization: Bearer **apikeyapikeyapikey**" https://api.tailscale.com/api/v2/device/**deviceIDCNTRL**
{"addresses":["100.100.100.12","fd7a:125c:a8e0::cd01:4126"],"authorized":true,"blocksIncomingConnections":false,"clientVersion":"1.76.1","created":"2024-11-03T07:33:50Z","expires":"2025-05-02T07:33:50Z","hostname":"opnsense","id":"5576439172817070","isExternal":false,"keyExpiryDisabled":true,"lastSeen":"2024-11-29T04:54:56Z","machineKey":"mkey:1ba27e58e8997729cfdfd2bda688ab03888f1679828abc2a34ffd57da0fe4047","name":"opnsense.tail51fc9b.ts.net","nodeId":"mydeviceIDCNTRL","nodeKey":"nodekey:b4e4a3810b9340e5c48829c7a69b7889a55919023409236sudfj04bccf5a5125","os":"freebsd","tailnetLockError":"","tailnetLockKey":"nlpub:f0d5e8506aa0172629347ae5e9bccc7a031433c0f1d09a8f2b61844843ad37b2","updateAvailable":false,"user":"myemail@gmail.com"}ubuntu-desktop@ubuntu-desktop:~/Docker/homepage$ 

[BBT-nZ]

@shamoon I'm calling all Homepage GOD's here, tell me I'm dumb and missed out something.

[shamoon]

No need to ping mate, I get all messages here.

ENETUNREACH suggests the container cant reach the internet, or just tailscale.com . Try the troubleshooting steps again carefully, the curl should be from inside the homepage container (I suspect it wont work)

[shamoon]

Hmm, yea thats odd. I cant reproduce anything over here:

Not sure mate, sorry

[BBT-nZ]

Err....I noted an existing issue as well that was logged several months back similar to this but no response as well.

Is this a potential bug? Any recommendations as under what settings this should work, environment, OS? Im baffled as I got it working previously in ubuntu desktop vm but now no more

Are you running this on a VM too? If yes, is that Proxmox?

[shamoon]

Im not running in a VM no.

[BBT-nZ]

Wooah! After nearly a week of debugging this looks like I've narrowed down the suspect and have it working across atleast x3 environments! :D I'd like to post some instructions for the dumb myself and others who may venture down this path as to how to fix this issue in Docker, CasaOS, VM (Ubuntu Server) just managed to checked this so far..

Please advice.

[shamoon]

Is that a question? Just post the solution here, people can search

glad it’s solved

[BBT-nZ]

Goal:

Case 1:
Proxmox > Ubuntu Server VM > CasaOS > Homepage

Container Config:

• Make sure the container is running in HOST mode

Enter the shell of the container

Check if IPv6 is Disabled:

Run the following command to check:
sysctl net.ipv6.conf.all.disable_ipv6
If the output is net.ipv6.conf.all.disable_ipv6 = 0, IPv6 is enabled.
If the output is net.ipv6.conf.all.disable_ipv6 = 1, IPv6 is disabled.

How to Disable IPv6 Permanently

1. Edit the sysctl.conf file:
   sudo nano /etc/sysctl.conf

2. Add the following lines at the bottom of the file:

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

3. Save and exit (Ctrl+O, Enter, Ctrl+X).
4. Apply the changes
   sudo sysctl -p
5. Reboot (highly recommended)

Case 2:
Proxmox > Homepage LXC via Legendary tteck R.I.P (We Miss You)

New Installation:

Make sure to Disable IPv6

Exisiting Installation:

Check if IPv6 is Disabled:

Run the following command to check:
sysctl net.ipv6.conf.all.disable_ipv6
If the output is net.ipv6.conf.all.disable_ipv6 = 0, IPv6 is enabled.
If the output is net.ipv6.conf.all.disable_ipv6 = 1, IPv6 is disabled.

How to Disable IPv6 Permanently
Follow the same steps as above in Case 1

Case 3:
Proxmox > Ubuntu Server VM> Docker/Docker Compose > Homepage

Sorry no screenshots here, but the principle remains the same

How to Disable IPv6 Permanently
Follow the same steps as above in Case 1

Thanks for providing this amazing platform Homepage :) glad to be in a position to contribute.

[shamoon]

Thanks for taking the time to post all of this, I'm sure it will help someone.

And yea I saw some stuff online about IPv6, will refer people here in the future if this comes up.

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.