aptalca

I have been doing all my linuxserver.io development through this image for a while. I work on dozens of git repos and it works just fine. Make sure the config folder is on a /mnt/cache or /mnt/diskX location. Fuse on unraid may cause issues

When you put up the nginx container, are you trying the http endpoint? From outside of the lan?

That sounds like a plex issue. You should ask them on their forums

Only worry about the last line. The others are system ones and are used for things like logrotate. 4) yes

I don't think anyone on the team has ipv6 resources/capability, so no, we don't have any plans since we can't even test anything.

1) fully automated 2) daily 3) sure, edit the crontabs/root file in the config folder and restart the container PS. If you do dns or duckdns validation, you don't need to keep any ports open or forwarded as they are not used for validation

Just an alert. It's harmless

https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/ And https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

Logpath should point to bitwarden logs. You need to map that folder in letsencrypt

Info in the readme

Edit the default site config and modify the location block for "/" For unraid, you can copy and modify an existing proxy conf with unraid values

Is this a new container or an update of an existing install? Check the openvpn logs in the config folder and it should tell you what the issue is Also try using /mnt/cache endpoint for the config folder instead of /mnt/user

Post your docker run

Check the Plex server logs in the config folder

Check the logs after an update. Post your docker run. Make sure the config folder is on /mnt/cache

You set one of the vars to docker (as it says in the log). Check the readme to see what it means

It's all explained in the readme, which is the official word

Please open an issue on GitHub so we can track it. Make sure to include the reason why you need it. Check to make sure there is an alpine package for it

You need to follow the instructions at the top of each proxy conf. If it says to set a base url, you need to do that in the upstream app

You removed crucial elements including the listen directive, as well as the inclusion of ssl.conf

You can do that. Map an additional volume where host side is on /mnt/user and modify the default site conf to point the root directive to it EDIT: May have misread. I'm talking about the "web root". If you're talking about being able to put the config folder on a share on the array, we can't do that. It's an issue/bug with the fuse filesystem implementation unraid uses for array shares

Try it without organizr. If they work (they work for us), then you can ask organizr devs why they don't work with it.

Recreate the container and it should successfully install node 12.15.0

Oh crap, I forgot a package. I'll PR a fix later today. It should install the latest LTS (v12). I'll let you know here once updated.

You need to set the key to DOCKER_MODS