j0nnymoe

Not unless there is a alpine package for that module.

Again as per the readme, it states `need to change both sides` aka the container port and host port to match and you haven't done this.

Did you create a new mapped port for the container?

I assume you read this section of our readme https://github.com/linuxserver/docker-qbittorrent/blob/master/README.md#webui_port-variable

It's not like we've got a forum / discord server or even IRC..

Your guess is as good as mine, I'm not involved with them.

Nothing - the latest tag hasn't been updated yet. https://hub.docker.com/r/emby/embyserver/tags

You've hit the request limit: There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: linnaeus.duckdns.org,linnio.duckdns.org,lserv.duckdns.org: see https://letsencrypt.org/docs/rate-limits/ Need to wait for that to reset which I believe is 7 days.

There is a config included with our letsencrypt container.

Run tvheadend in host instead of bridge. As per the documentation: https://github.com/linuxserver/docker-tvheadend#host-vs-bridge

Glad to here it's working you. I'm planning on digging into this properly myself soon. I guess you could use something like dbeaver to read the dB?

Correct, you just access it from your web browser.

Of course, just have to connect a usb barcode scanner to your computer. The fact it's in a docker container doesn't limit that.

I would seek support from unifi directly. No one within the team will be able to test as we don't have any USG's.

All the information to configure the convert plugin is here: https://beets.readthedocs.io/en/v1.4.7/plugins/convert.html

Yes Sir.

Looks like you are doing http verification. Make sure port 80 is open or switch to using DNS verification instead.

Try not using 0.0.0.0 - Leave that blank or put your actual IP range in 192.168.1.0/24 for example.

Adjust the ports that unraid webui run's on:

Fork the container and learn how to compile/patch Leia to be headless.

This is due to s6 which is used within all our containers. I believe you need to lookup spin up groups within unraid to get around this.

Setup the Cron on the host to call the container and run a command

Wrong support thread. You're using Binhex's container, not ours.

Add your mail settings to the .env file in `/config`

The config we provide with our letsencrypt container works fine. https://github.com/linuxserver/reverse-proxy-confs/blob/master/heimdall.subdomain.conf.sample