j0nnymoe

Check their site at https://www.picons.eu/ You'll probably need to submit them via their github.

You would need to add them upstream (picons.eu) so they get picked up by us. Otherwise, you'll have to re-add them everytime the image updates.

We add all the icons from `https://www.picons.eu/` Though if you want to create your own blank set, create an additional mount for `/picons` on the tvheadend container page and point it to your own folder which will allow you to maintain your own icons. This will obviously not use the included icons.

There's alot of history with our unifi container and to be perfectly honest, unifi aren't known for quality releases. We've already been through the pain of users asking us for a new version that's been released instantly then we'd update them and then we would get complaint's that X/Y/Z wouldn't work. Adding a beta/unstable branch would increase the questions even if we stated we don't give support for it. Abit of back story: https://blog.linuxserver.io/2019/02/18/changes-to-our-unifi-image/

As mentioned a couple posts back, it's an upstream issue with mono6 and duplicati, not with the container.

Actually, the issue is due to the upgrade to mono6 and specifically onedrive. Running latest here no problems with backblaze2 so I think it's unfair for you to make the following comment `For now, this docker will not work for new users using "latest" or old user that upgrade soon.` Right now it only seems to affect onedrive uploading and only 1 other user has reported at duplicati. https://forum.duplicati.com/t/mono-update-breaks-onedrive-v2/7569 This is an upstream issue, Not an container issue.

Change from the `lsiodev/sonarr-preview` to `linuxserver/sonarr:preview`

🔮🔮🔮🔮

Nope.

Do you have the `/tmp` mounted on the container?

eh, other than the fact they've dropped support for 5.9...lol they only support 5.6 or 5.10

Have you been updating Nextcloud within the container?

If you read back through the thread, you'll find everyone else gets this error and you'll also find it's harmless.

Create your shares as normal and add them using external storage app within nextcloud, that's the proper way to do it.

You need to do what's being done in this picture or read the post right above your one. (Stolen from post further up)

Just configure your DNS to allow you to use your reverse proxy internally? We don't support putting SSL directly on the container.

Please search the thread first. It has already been discussed multiple times. This will only cause issues if you use lua. It's an upstream issue so out of our hands.

maybe your ISP are blocking your ports.

Have you thought about reading through the beets documentation? I suspect alot of your questions are covered there. https://beets.readthedocs.io/en/v1.4.7/

You could read about it at their website.. https://grocy.info/

Yes.

You wouldn't reverse proxy a database connection via a HTTP proxy. Just point your windows application at the firebird SQL port number and away you go.

You would have to give that request to the grocy developers directly.

Looks like corrupted database. Restore a backup.

All you do is create a subdomain at your DNS - point it to your IP and then browse to https://subdomain.domain.com:portnumber .