j0nnymoe

Unfortunately I'm a firefox user and it's working fine in that.

I can only assume it's something specific to your server. I use TVHeadend daily along with my DigiBit R1 for DVB-S2 and never had an issue.

This looks more like an issue Chrome blocking the invalid cert rather an issue with the docker container.

No. Only fresh installs will pickup v17. Existing issues will get v17 when nextcloud release it to their web updater. They stagger the release for obvious reasons.

@jpowell8672 Checking the nzbhydrav2 change log shows this: So it's an issue with the software itself, not the container. You'll need to find you last working backup and update that.

I would say that your issue isn't a container issue but a bug within unraid 6.5 itself, I would contact lime tech about it or search the forum to see if someone else has had this issue (I suspect someone has).

Update to latest unraid first, then come if you have the same issue.

As per our chat on discord, it was your pihole instance that's causing this problem.

1.) you'd have to add this to your local dns server (if you have one setup) 2.) you'd need to read the nginx documentation on how to redirect this.

I guess it's as secure as your password?

afaik SQLite has always been an option within nextcloud but they don't recommend it for anything other than testing.

No we don't include MariaDB within the container. He must be using the default sqlite for nextcloud (Though even they don't recommend it for production use)

It's already been mentioned in this thread multiple times that this is nothing to worry about.

Think you need to set your IP here. The second issue is caused by a security "feature" of docker.

Yep

Yea no worries - I've always ran PiHole/Adguard on a dedicated Pi aswell so never had this issue.

I believe the issue is actually when you run PiHole as a container with it's own IP, there are docker security features that stop docker macvlan IP's communicating with each other. So when you have Letencrypt on it's own net and Pihole on it's own ip, if unraid it setup to check pihole for dns, letsencrypt is able to talk to pihole. I always suggest to people if their wanting to run pihole/adguard on your network, run it from a dedicated device.

It's an unraid issue, not a problem with the container. Check the stable bug reports forum.

Just make sure your unraid server isn't using the pihole DNS.

You don't need to change the port number within the reverse proxy config.

Unraid Update / Docker Hub issues - unrelated to our containers.

Considering airsonic is forked from libresonic, I would suspect that the app just doesn't like network mounted shares.

I might be wrong but if you have both bookstack and mariadb on their on dedicated ip's, there is a docker "security" feature that blocks them talking to each other.

Preview is unsupported. it's a use at own risk.