Runtipi•14mo ago

Uptime Kuma problems after update to Tipi 2.1.0

Hello All. I recently updated from Tipi 2.0.5 to 2.1.0. After the upgrade, I noticed Uptime Kuma no longer launches. Before I noticed, I had seen the guest dashboard and enabled Uptime Kuma to be available from the guest dashboard and enabled the guest feature in Tipi. After I realized it was no longer working, I reverted the changes to the guest access for Uptime Kuma and disabled the guest setting in Tipi and restarted. Im not sure if the guest access had anything to do with the app no longer functioning, but I did make the changes at the same time as the upgrade of Tipi. Has anyone else seen a problem like this? The only error showing up in my error.log file is

cli: 2023-11-11T14:30:00.065Z - error >     stderr: Command failed: git config --global --add safe.directory /root/runtipi/repos/29ca930bfdaffa1dfabf5726336380ede7066bc53297e3c0c868b27c97282903
fatal: $HOME not set

cli: 2023-11-11T14:30:00.065Z - error >     stderr: Command failed: git config --global --add safe.directory /root/runtipi/repos/29ca930bfdaffa1dfabf5726336380ede7066bc53297e3c0c868b27c97282903
fatal: $HOME not set

11 Replies

Stavros•14mo ago

the error is fine no need for that can you manually start and stop uptime kuma?

austinsrOP•14mo ago

I can hit start or stop on it, but it never launches. I've check with a port scanner and the port isnt open. I get a "This site can’t be reached" when I try to load it Watching syslog when the container starts, I get

Nov 11 14:29:37 tipi1 dockerd[975]: time="2023-11-11T14:29:37.362696550-05:00" level=warning msg="Failed to allocate and map port 8125-8125: Error starting userland proxy: list             en tcp4 0.0.0.0:8125: bind: address already in use"
Nov 11 14:29:37 tipi1 systemd-networkd[700]: veth8e03bd1: Link DOWN
Nov 11 14:29:37 tipi1 kernel: [62451.415011] br-4fa03cc748a8: port 10(veth8e03bd1) entered disabled state
Nov 11 14:29:37 tipi1 kernel: [62451.415996] veth8e03bd1 (unregistering): left allmulticast mode
Nov 11 14:29:37 tipi1 kernel: [62451.416001] veth8e03bd1 (unregistering): left promiscuous mode
Nov 11 14:29:37 tipi1 kernel: [62451.416005] br-4fa03cc748a8: port 10(veth8e03bd1) entered disabled state
Nov 11 14:29:37 tipi1 NetworkManager[725]: <info>  [1699730977.3891] device (veth8e03bd1): released from master device br-4fa03cc748a8
Nov 11 14:29:37 tipi1 dockerd[975]: time="2023-11-11T14:29:37.459908201-05:00" level=error msg="Handler for POST /v1.43/containers/b81895c63825c18430bdc16cfb94f938640a65964f559             a4f41b8a6dc4ee83fa0/start returned error: driver failed programming external connectivity on endpoint uptime-kuma (194b3833015b4d72f966412d54f35212fa3c2e6127a3356f896dffc3aad82             157): Error starting userland proxy: listen tcp4 0.0.0.0:8125: bind: address already in use"

Nov 11 14:29:37 tipi1 dockerd[975]: time="2023-11-11T14:29:37.362696550-05:00" level=warning msg="Failed to allocate and map port 8125-8125: Error starting userland proxy: list             en tcp4 0.0.0.0:8125: bind: address already in use"
Nov 11 14:29:37 tipi1 systemd-networkd[700]: veth8e03bd1: Link DOWN
Nov 11 14:29:37 tipi1 kernel: [62451.415011] br-4fa03cc748a8: port 10(veth8e03bd1) entered disabled state
Nov 11 14:29:37 tipi1 kernel: [62451.415996] veth8e03bd1 (unregistering): left allmulticast mode
Nov 11 14:29:37 tipi1 kernel: [62451.416001] veth8e03bd1 (unregistering): left promiscuous mode
Nov 11 14:29:37 tipi1 kernel: [62451.416005] br-4fa03cc748a8: port 10(veth8e03bd1) entered disabled state
Nov 11 14:29:37 tipi1 NetworkManager[725]: <info>  [1699730977.3891] device (veth8e03bd1): released from master device br-4fa03cc748a8
Nov 11 14:29:37 tipi1 dockerd[975]: time="2023-11-11T14:29:37.459908201-05:00" level=error msg="Handler for POST /v1.43/containers/b81895c63825c18430bdc16cfb94f938640a65964f559             a4f41b8a6dc4ee83fa0/start returned error: driver failed programming external connectivity on endpoint uptime-kuma (194b3833015b4d72f966412d54f35212fa3c2e6127a3356f896dffc3aad82             157): Error starting userland proxy: listen tcp4 0.0.0.0:8125: bind: address already in use"

Ive rebooted the host a few times now, so I dont know how 0.0.0.0:8125 is already in use, unless its crashing at system boot time and then staying bound afterwards

Stavros•14mo ago

what does docker ps give you?

austinsrOP•14mo ago

I just figured it out. It was a conflict with the port 8125 with "netdata". I had installed that on my Tipi nodes to get some bandwidth and cpu graphs. Thanks for assisting

Stavros•14mo ago

wait what netdata? i have configured netdata to use port 1999 or something

austinsrOP•14mo ago

Sorry, I also have a CasaOS node that is running Emby and netdata, since Emby isnt in the Tipi store.

Stavros•14mo ago

yeah we are planning to add it

austinsrOP•14mo ago

I should have known trying to mix and match the 2 infrastructures would end up causing problems.

Stavros•14mo ago

no problem..

austinsrOP•14mo ago

But yeah, thank you for assisting. It is much appreciated. Live and learn

Stavros•14mo ago

of course thats my job here! @Mxrcy we can close this

Gaming

Programming

Uptime Kuma problems after update to Tipi 2.1.0

Did you find this page helpful?