aptalca

Post your docker run/create command

Take a step back. What exactly are you trying to achieve? Are you trying to be able to access nextcloud at https://yourdomain.com:53444 ?

The only thing I can think of is that geoip v1 was recently removed as it was deprecated a while back and now the databases are no longer available. If you were using geoip, that will result in a failure. Geoip v2 is included in the image with an up-to-date database. You can use that instead

Don't stop it, keep it running. If you don't want to use the webserver features at all, use dns validation and don't map any ports

You should set up a reverse proxy. Look into our letsencrypt image: https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/#nextcloudsubdomainreverseproxyexample

I noticed that, too. Didn't look into it yet, since it seems to work fine after a restart

The mapping is in the template but I don't know how you set it up or if you changed it

You likely created all the users while Authentication is set to something other than "local". The readme states that you need to switch to local first. Or, you didn't map the config folder correctly, so all your data is lost after an update. We don't control the openvpn-as webui, it's upstream. You can make a request to them for the import/export functionality. But just so you know. When you update/recreate the container, it automatically exports your old settings and database and imports into the new container (as long as the config folder is mapped correctly).

the geoip2 database is at this path inside the container: /var/lib/libmaxminddb/GeoLite2-City.mmdb the instructions are here: https://github.com/leev/ngx_http_geoip2_module/blob/master/README.md#example-usage

Geoip v1 has been deprecated for a while and as of last week, the databases are no longer available for download. So we removed the geoip packages from the image. But don't fret, geoip2 is included in the image and works. You just need to update your config to use that instead.

No, it's strictly a routing/dns issue. Something must have changed on your side. Did you reboot the router perhaps?

Having additional modules doesn't really hurt anything. We're going for simplicity. Variable for modules would increase complexity

Please create an issue on the github repo so we can track it

Perhaps you set the server to only accept encrypted connections over https

We can add that, too if it doesn't add too much bloat

Looks like attempts to update the geoip db are failing. Harmless but we'll look into it

You can request php modules to be added and unless they're really fringe cases, we add them. What exactly are you trying to set up?

I have a theory about that. Can you create an issue on the GitHub repo so we can track it easier?

Nobody is an actual user on unraid. It is meant to own all files on unraid, which is exactly what the user permissions script does. Your issue is that Plex (running as user nobody) saves the new files as owned by user nobody, but the group permissions are missing write. Your smb user, which is in the same group as user nobody, is allowed to read those files but cannot delete them.

That's right, it's not a docker image issue. It's because your smb user is different than user nobody. Plex is not creating those files with group write access.

Check the top of the default site config

Can't you delete them in the Plex gui?

That needs to be set to /transcode exactly

Just a heads up to both of you, mapping the /transcode location is not enough. You also need to go into Plex server settings in the gui and select /transcode as the transcode location

Create the container with host networking and make sure you're connecting to it from the same network subnet. Once you claim the server, you can switch to bridge again