aptalca

That is brilliant

I'm not getting this error, but can you check the file "config.ini" in your config folder and see what the parameter "log_dir" is set to? That's a gui setting and by default it should be "/config/logs". If different, set it to that and restart

Yup. "ls -al" will list permissions and owner info

Check the permissions of the other folders in that location and match it If you do "chown -R nobody:users webtoolsfoldername" it should take care of it

I don't quite understand where you expect to see the padlock icon in vpn. Your server is set up at the address: https://hamza219421.duckdns.org That is the address the cert checking websites are checking. That has nothing to do with vpn. Just go to that address in your browser while you're away from home and you'll see your website and the green padlock. If you want to access other services through that address, you'll have to set them up through reverse proxy. There is plenty of info on that in this thread.

It was supposed to auto update to the latest version. I'll look into it

In order to use a device in docker, the host would need to load either the drivers or the kernel modules. I don't believe unraid supports any USB cameras

I don't understand what the issue is. The certs are there, and the nightly renewal script is running successfully. So the container is running fine. The nginx error log has to do with a client that tried to access your site. It could be an issue on their end or an issue with your site config or contents. I have no information to determine that.

I'm using a single btrfs cache drive still. No problems. I added the other drives through unassigned devices

Try restarting the container (not reinstall). There is an intermittent bug that pops up every once in a while on first boot, but works on a reboot. If that doesn't work, post the full container log

Calibre server has no gui to change settings. It looks for the library at /config. Set that to your existing library location. It has to already be set up with calibre prior. Otherwise use the rdp version and create a new library and set it however you like

I don't experience it. Please post your container settings and we'll take a look

Not an easy fix. There are a few options but none are really ideal. Currently discussing internally the best recourse

Never used aspx, so not entirely sure, but there is no mono in this image, so probably a no go.

Nginx cannot connect to the reverse proxied servers. If you didn't change the nginx site config in a while, then you probably changed your router/firewall rules or something. Can you connect to Sonarr directly at 192.168.2.90:9898?

This image is still supported. There used to be a separate location mapped for transcode but now you can select a location in the plex gui so no need for that additional mapping.

Not feasible in an automated way

You're right. I realized I'm on an older version as well. We'll look into it. Thanks

Yes, that is correct about wildcard certs. Letsencrypt (acme) uses a couple of different methods to verify that you control the domain. One is using a webserver and serving a custom file to the letsencrypt server. That is the method we use in this container. Another method is to add a custom txt variable in the public dns settings of the domain, which letsencrypt reads to validate. Unfortunately the wildcard domains will work only with the dns method.

You can edit the nginx.conf but don't overwrite it with a config from another server or you'll break it. Nginx package from the ubuntu repo has very different defaults than this container which is alpine based, and uses s6 as the supervisor. What you posted is just a snippet of the site config. And not related to the error you're getting.

I suspect you highly modified the nginx. conf and perhaps removed the "daemon off" setting so it's trying to launch a second instance unsuccessfully. Did you by any chance copy your nginx settings over from another install? If so, go back to defaults by deleting them and restarting the container. Then modify the defaults as needed. If that doesn't work, post your container settings along with nginx and site configs and we'll take a look.

DNS challenge only https://community.letsencrypt.org/t/wildcard-certificates-coming-january-2018/37567/8

A couple of thing I noticed. . . I am not sure if 0.0.0.0 is the real ip you are trying to reverse proxy or if that's your redaction. If former, that is incorrect. 0.0.0.0 in net=bridge will refer only to the letsencrypt container, not the host and not other containers. You can use the server ip to connect to a different container. Also, you are trying to reverse proxy an https page. That is likely the reason you are getting the ssl handshake error (or a combination with a nonexistent service on 0.0.0.0 as referenced above). Try to use an http address for the reverse proxy.

Works fine here. It wasn't the rdp part that broke, it was the built in server. It is now fixed but you have to enable in the gui settings. Details on docker hub description

s6-svc -h /var/run/s6/services/nginx