WatchTower Widget API error

[ninjamonkey198206]

I'm getting an API error from the Watchtower widget: Unexpected token '<', "<bod"... is not valid JSON

I do have the Watchtower container on it's own network, as I have ALL of my services on separate Docker networks by type and function, eg all media containers are on the same network, Vaultwarden instances are on own their separate networks, etc.

When communication between the networks is necessary I add rules allowing traffic between the networks (limited by container IPs and new, existing, and related traffic types) in question, and this has worked for the Portainer widget as well as a few others.

I currently have rules in place to allow traffic between the network homepage is on and watchtower, without limitations by IP (I add those after I get it working, so I can tell quickly if I did something boneheaded and reversed the source and destination IPs).

I simply cannot get the watchtower widget to work. All instructions to enable HTTP API access have been followed.

Here is the config:

version: "3.7"

# networks
networks:
  watchtower:
    driver: bridge
    driver_opts:
      com.docker.network.bridge.name: watchtower
    ipam:
      driver: default
      config:
        - subnet: ${SUBNET}/24
          gateway: ${GATEWAY}

services:
  # Watchtower
  watchtower:
    image: containrrr/watchtower:latest
    container_name: watchtower
    restart: unless-stopped
    labels:
      - homepage.group=Docker Utilities
      - homepage.name=WatchTower
      - homepage.icon=watchtower.png
      - homepage.description=Container update monitor
      - homepage.widget.type=watchtower
      - homepage.widget.url=http://172.27.0.2:8080
      - homepage.widget.key=MyKey
    environment:
      TZ: ${TZ}
      WATCHTOWER_CLEANUP: ${CLEANUP}
      DOCKER_API_VERSION: ${API_VER}
      WATCHTOWER_INCLUDE_STOPPED: ${INCLUDE_STOPPED}
      WATCHTOWER_HTTP_API_UPDATE: ${HTTP_API_UPDATE}
      WATCHTOWER_HTTP_API_PERIODIC_POLLS: ${HTTP_API_PERIODIC_POLLS}
      WATCHTOWER_HTTP_API_TOKEN: ${API_KEY}
      WATCHTOWER_HTTP_API_METRICS: ${HTTP_API_METRICS}
      WATCHTOWER_POLL_INTERVAL: ${POLL_INTERVAL}
      WATCHTOWER_MONITOR_ONLY: ${MONITOR_ONLY}
      WATCHTOWER_NOTIFICATIONS: ${NOTIFICATIONS}
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER_TLS_SKIP_VERIFY: ${EMAIL_SKIP_VERIFY}
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT: ${EMAIL_PORT}
      WATCHTOWER_NOTIFICATION_EMAIL_FROM: ${EMAIL_FROM}
      WATCHTOWER_NOTIFICATION_EMAIL_TO: ${EMAIL_TO}
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER: ${EMAIL_SERVER}
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER: ${EMAIL_USER}
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD: ${EMAIL_PASS}
      WATCHTOWER_NOTIFICATION_EMAIL_DELAY: ${EMAIL_DELAY}
    networks:
      watchtower:
        ipv4_address: ${WATCHTOWER_IP}
    ports:
      - ${WATCHTOWER_EXP_PORT}:8080
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

[shamoon]

So you’ve verified homepage can communicate with the watchtower container? How about the actual api calls?

see https://gethomepage.dev/en/more/troubleshooting/

[ninjamonkey198206]

Chain DOCKER-USER (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     all  --  watchtower media   172.27.0.2           172.18.0.12          ctstate RELATED,ESTABLISHED
    0     0 ACCEPT     all  --  media  watchtower  172.18.0.12          172.27.0.2           ctstate NEW,RELATED,ESTABLISHED
 3104   27M ACCEPT     all  --  docker0 media   172.17.0.2           172.18.0.12          ctstate RELATED,ESTABLISHED
 2534  176K ACCEPT     all  --  media  docker0  172.18.0.12          172.17.0.2           ctstate NEW,RELATED,ESTABLISHED

[shamoon]

Well if you can't ping watchtower from the homepage container then its your networking setup no? I don't use this kind of setup, I have a 'backend' network that is not connected to the public internet (directly) and I put my containers that need to talk to each other on it (in addition to other networks, if needed). But yea, gotta sort out why your homepage container can't reach the watchtower container

Yep, that's why the troubleshooting guide starts with that, folks got fancy setups out there but sometimes the basics can help to find the issue =)

[ninjamonkey198206]

Going to try creating an isolated bridge network and adding the various containers that need cross network communication for homepage to it. Pretty much what you said you do, and without my firewall hacks.

[ninjamonkey198206]

That did it.
Won't work for portainer unless I create a compose file for it, but it'll work for everything else.
But the portainer firewall rules are working, so no need.
Don't suppose it'd be helpful to post the info on how to do that in the docs, would it?

[shamoon]

Awesome 👏

I think it’s a little specific for the docs? But if others run into this we can always add down the road

[github-actions[bot]]

This discussion has been automatically closed due to inactivity.

[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.