danclark

I have each container on a custom docker network so in the range 172.18.0.x but I hadn't bothered assigning each container a static IP they were set to dynamic. So essentially what had happened for some reason was that some of the IPs on my customs docker network were reallocated. So essentially the Browserless IP was no longer 172.18.0.17 and had changed to 172.18.0.21 so basically Karakeep was no longer looking for it in the right place. I updated the Browserless path in the Karakeep container settings to point to the new IP and it started working again. Hope this helps.

This happened to me too. In my case it was because my docker network IPs had randomly changed! No idea why, but essentially the Karakeep container was no longer pointing at the Browserless one as the IP address was no wrong. I don't think I had changed anything on my end, so assume it was a result of one update or another.

Has anyone managed to get this working with Tailscale on Unraid 7? I'm still fairly new to Unraid so possible I'm doing something wrong, but this is the first container that hasn't more or less 'just worked' when I added tailscale connectivity. I'm by no means an expert on Docker either but have been homelabing for a couple of years so know the basics. I am able to create and launch the container fine, and have confirmed it is working via localIPaddress:port. Tailscale appears to sign in correctly and the container shows as connected to my tailnet. I can also ping the container via tailscale IP and name. However I cannot access the webUI of Splitpro via the tailscale IP or name. I am specifying the port I chose (30123) in the URL (3000 already being used), but has also tried 80 and 3000 just in case. The container and tailscale logs look sensible. I am unable to enter the console of the container as it immediately closes itself so can't exec in. Bit stumped and unsure what to try next. Anyone able to point me in the right direction? Thanks to Swiss01 for making this template. Unfortunately if we can't use Splitpro away from our home WiFi we can't really replace Splitwise so this is very frustrating.