Skip to content

problems with Uptime-Kuma mod #789

@apperrault

Description

@apperrault

hey all
I am running SWAG via docker compose with an override. I originally got the docker mod to work, and it was great. Then I made the mistake of removing a container that had been setup to be monitored and now the docker mod is erroring out and stopping swag when i try and restart it.

here is a link to the swag logs from when I try and start it with the mod enabled
https://pastebin.com/1WdwFLpV

here is the pertinent portions of my compose
swag: volumes: - ${DOCKERCONFDIR}/organizr/www/db:/organizrlog:ro environment: - MAXMINDDB_LICENSE_KEY=XXXXXXXXXXXXXXX - DOCKER_MODS=linuxserver/mods:swag-dashboard|linuxserver/mods:swag-auto-reload|linuxserver/mods:universal-docker|linuxserver/mods:swag-cloudflare-real-ip|linuxserver/mods:swag-auto-proxy #|linuxserver/mods:swag-auto-uptime-kuma - DISC_HOOK=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - DISC_ME=XXXXXXXXXXXXXXXXXXXXXXXXXXX - DOCKER_HOST=tcp://dockerproxy:2375 - CROWDSEC_API_KEY=XXXXXXXXXXXXXXXXXXXXXXX - CROWDSEC_LAPI_URL=http://crowdsec:9091 - UPTIME_KUMA_URL=http://uptime-kuma:3001/ - UPTIME_KUMA_USERNAME=admin - UPTIME_KUMA_PASSWORD=XXXXXXXXXXXXXXXXXXXXX

Any thoughts on how to fix this?
thanks
app

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions