rama3124

Thanks, I'm more than happy to give this a go but fairly new to unraid so not sure how to modify the plugin. Is it a simple process?

I have monica installed using the docker compose plugin and the container constantly shows up on my unraid docker action centre and on the fix-common-problems plugin as needing update. I read in other comments on this thread that docker containers installed with the compose plugin cannot be updated the usual way through unraid and need to be updated by clicking 'update stack'. Even when I do this, the container still shows up as needing update. Is there a way to stop unraid from checking for updates for containers installed with this plugin? TIA

Thanks Still learning

Hi, i tried running one of the default scripts to remove dangling images and received the following error: NoteError response from daemon: conflict: unable to delete 4acdeafdf597 (cannot be forced) - image is being used by running container 4f1978a0b6d1 Is this an error that can be ignored? Thanks

Is there a way to modify the name of the docker containers that are created with this plugin? I just created a monica container and named the stack 'Monica', so now my container is called monica-monica-1. Can i somehow just rename this monica?

I seem to have located the solution to this problem on github as linked below but it involves making a duplicate of the monica container that runs the cron.sh script. The commenter seems to have used docker compose but I haven't got docker compose installed since I make use of the templates instead on the CA store. Is there a way to duplicate the container to run the cron.sh script without docker compose? Perhaps I can include command: cron.sh in the post arguments? Sorry, still new to unraid so learning https://github.com/monicahq/monica/issues/4178#issuecomment-1925669386

Do i add this to the post-arguments? I tried adding this and the container didn't start

Hi, I have the latest version of authentik installed on my unraid server and the authentik container crashes randomly every few hours, resulting in the loss of access to all my services. When I check the logs, I see the redis timeout error included below. Any tips on how to resolve this? TIA 16/05/202405:19:32 am error=dial tcp: lookup redis: i/o timeout event=failed to connect to redis level=panic logger=authentik.outpost.proxyv2.application name=Calibre Web Forward Auth timestamp=2024-05-16T05:19:28+10:00 16/05/202405:19:32 am panic: (*logrus.Entry) 0xc0001b0ee0 16/05/202405:19:32 am 16/05/202405:19:32 am goroutine 108 [running]: 16/05/202405:19:32 am github.com/sirupsen/logrus.(*Entry).log(0xc0001b0e70, 0x0, {0xc0010946a0, 0x1a}) 16/05/202405:19:32 am /go/pkg/mod/github.com/sirupsen/[email protected]/entry.go:260 +0x491 16/05/202405:19:32 am github.com/sirupsen/logrus.(*Entry).Log(0xc0001b0e70, 0x0, {0xc000450340?, 0x5?, 0x2?}) 16/05/202405:19:32 am /go/pkg/mod/github.com/sirupsen/[email protected]/entry.go:304 +0x48 16/05/202405:19:32 am github.com/sirupsen/logrus.(*Entry).Panic(...) 16/05/202405:19:32 am /go/pkg/mod/github.com/sirupsen/[email protected]/entry.go:342 16/05/202405:19:32 am goauthentik.io/internal/outpost/proxyv2/application.(*Application).getStore(_, {0xf, {0xc0003a0960, 0x18}, 0xc00033d870, {0xc00029ed20, 0x1a}, 0xc001066718, 0xc00033d880, 0xc00033d890, ...}, ...) 16/05/202405:19:32 am /go/src/goauthentik.io/internal/outpost/proxyv2/application/session.go:76 +0x7e8 16/05/202405:19:32 am goauthentik.io/internal/outpost/proxyv2/application.NewApplication({0xf, {0xc0003a0960, 0x18}, 0xc00033d870, {0xc00029ed20, 0x1a}, 0xc001066718, 0xc00033d880, 0xc00033d890, {{0xc000e2ed50, ...}, ...}, ...}, ...) 16/05/202405:19:32 am /go/src/goauthentik.io/internal/outpost/proxyv2/application/application.go:140 +0xf4a 16/05/202405:19:32 am goauthentik.io/internal/outpost/proxyv2.(*ProxyServer).Refresh(0xc00043a0b0) 16/05/202405:19:32 am /go/src/goauthentik.io/internal/outpost/proxyv2/refresh.go:37 +0x567 16/05/202405:19:32 am goauthentik.io/internal/outpost/ak.(*APIController).OnRefresh(0xc000383500) 16/05/202405:19:32 am /go/src/goauthentik.io/internal/outpost/ak/api.go:178 +0x314 16/05/202405:19:32 am goauthentik.io/internal/outpost/ak.(*APIController).startIntervalUpdater(0xc000383500) 16/05/202405:19:32 am /go/src/goauthentik.io/internal/outpost/ak/api_ws.go:189 +0x17b 16/05/202405:19:32 am goauthentik.io/internal/outpost/ak.(*APIController).StartBackgroundTasks.func3() 16/05/202405:19:32 am /go/src/goauthentik.io/internal/outpost/ak/api.go:216 +0x5d 16/05/202405:19:32 am created by goauthentik.io/internal/outpost/ak.(*APIController).StartBackgroundTasks in goroutine 100 16/05/202405:19:32 am /go/src/goauthentik.io/internal/outpost/ak/api.go:214 +0x38d

I'm having the same issue with authentik crashing every few hours due to failing to connect with redis. Did you ever end up solving this?

Hey braintrust, I've got vaultwarden currently exposed to the internet through a cloudflare tunnel pointing to traefik reverse proxy but am looking to make it only available on my internal network (and on tailscale VPN) for increased security. I know that vaultwarden needs HTTPS to function but can't work out a way to make my subdomain (vaultwarden.mydomain.com) point to traefik so that it can generate a wildcard SSL certificate for vaultwarden. I tried to follow this guide linked below but when I set up the DNS record on cloudflare to point to my internal server address, it just leads to the unraid login page rather than vaultwarden and I don't have the ability to add a port number on the DNS record. How can I make the DNS record point to the traefik port of my unraid server? https://github.com/dani-garcia/vaultwarden/wiki/Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs

Hi Are the following instructions still valid for manual upgrade to 6.12.10 from 6.12.9? I tried it through SSH and my server is now unresponsive TIA

Still can't get the webgui to work. Checked ifconfig and it's tailscale1 listening. My unraid network settings has both tailscale1 and tailscale0 listening. Tried deleting tailscale0 from listening interfaces with no luck. I can access all docker containers, just not webgui. Here are the diagnostics too Unraid-tailscale-diag-20240402-142821.zip

Yeh I ran this in SSH: /usr/local/emhttp/plugins/tailscale/restart.sh I just tried it again but it didn't help. Anything else you can recommend to troubleshoot? I can access all the docker containers fine, just not the webgui. I'll try and get the diagnostics but it could be hard since I don't have local access right now

Thank you, the device came up as connected as soon as I ran tailscale up. Now I can access all my docker containers when adding the port numbers but can't get the Unraid webgui up. I saw this is a common issue when enabling subnets but I can't get the webgui up even when I put in the tailscale IP address

I gave this a go after all and when I stopped the docker container and approved the plugin, the new unraid instance didn't show as online in my tailscale admin console. I have SSH access so I can just delete the plugin and restart the tailscale container but is there a way to complete setup for the plugin through command line?

Ok thanks for your prompt replies

That sounds very complicated, it seems like my best bet is just to wait till I've got local access. Once I have, do I just delete the docker container and install the plugin? No other setup steps or configuration required?

It seems like the general consensus is to use the plugin now rather than the docker container. I currently don't have local access to my server, is it still possible to change to the plugin while maintaining tailscale connection? I'm assuming the answer is no since it seems I have to delete the docker container first (losing tailscale connection) before adding the plugin but I thought I'd check

Do we still need to modify the listening interfaces on network settings to get the unraid webui to work? And does the go file still need to be modified to get it to work on restart?

Correct you are. I'm running the docker container so posted this in the wrong forum. I'll move the post, thanks

Hi Do I still need to add tailscale0 to listening interfaces under network settings and modify the go file? Or has this since been resolved in a more recently release? TIA

Ok thanks for the tips, I'll check out the built in uptime kuma tunnel

If i've already got a cloudflare tunnel running through the cloudflared container by aeleos, is there an advantage to switch to this container?

I've cleared the logs and closed the tabs so let's see if it happens again. I usually leave a tab open with my docker page of unraid GUI but have never had a problem till now

No i didn't unfortunately, I just use firefox now to make bookmarks with keyword shortcuts for my internal IP addresses