jpresson

Just went through similar issues - it worked fine for a while but recently noticed karakeep was not successfully pulling and traced it back to a timeout communicating with browserless. The solution was to switch to CA's "browserless-v2" template and replacing the URL used in karakeep's template with ws://[IP]:[PORT]/chromium/playwright?token=[TOKEN] I'd recommend a note be added to the top of this thread if it's editable, and the docs @ https://docs.karakeep.app/Installation/unraid be updated to specify "browserless-v2" instead of just "browserless" to help anyone who encounters this issue in the future. I'll also add the previous commenter mentioned using browserless-v2's internal port # in the karakeep config. I did not need to do that, using 3012 in karakeep worked as it should.

Thanks for the suggestion. In the end, it was two problems (one of which was absolute PEBKAC). First is Chrome doesn't work, but Firefox does. Second is I had forgotten I was playing with VPN settings on the firefox install I was using after trying out SIOne's gluetun vid, and had forgotten to revert it back. That was preventing connection to the IP ZNC was on.

what is the "NextAuth" and associated secret for?

Installed this ZNC container, settings appear very simple but I am not able to access the WebUI. I have tried using multiple different browsers, as well as tried host, bridge, and my custom docker network used for most of my other service containers and get the same result every time: ERR_CONNECTION_RESET error in browser on attempting to access the hostip:6501. (Also tried using a different port number in the container config, made no difference.) Logs report no errors or warnings. I can bash into the container fine, not not able to access any WebUI. Any thoughts?

I am that someone. @ahror, https://xkcd.com/979/ Ahror's error log looks exactly like mine. I've tried reinstalling both containers (with removal of /appdata/container folders and even removing the template from CA apps page with no success. This worked for me previously, had immich working with swag & tailscale, but for a couple reasons after learning my way around and how external libraries are implemented, I decided I wanted to start over from scratch. That's when this issue began. I've tried several times now and I'm sure that i'm entering the same DB uname/pwd, setting right port, setting the integrated Redis, etc. In case it matters, both containers are on the same docker network and it's exactly how i had it set up the first time (which was working). edit - on 2nd inspection my error may be a little different. (similar red text about unable to connect, but the lines below that may be different. I'm taking another crack at it now and will report back). edit 2 - Solved the issue, and it was 100% PEBKAC. What I did wrong was used an incorrect IP address for the DB host when setting up the immich container. ... derp, forgot my current router is x.x.50.x instead of x.x.1.x.

+1, very much want to see this feature and I'll go one step further: In addition to being able to enforce a max size for a share, i'd also appreciate the ability to set a max GB of primary storage utilization for that share before it spills over to secondary storage. This would be especially helpful for shares where the mover is set to Array->Cachce for performance reasons, but where I want to control the max amount of data that can be kept on cache on a per-share basis.