CHBMB

You rebooted yet?

Have a look in your Nextcloud data folder (the one you mapped to /data) copy all the folders that are called $username somewhere safe. Then delete everything else. (Check and double check what you're deleting of course) So now you should find your Nextcloud folder is empty. Reinstall. Then when it's all set up, recreate your users in Nextcloud then copy across your old folders, which should restore the files where they need to be. Then the commands below should scan your files back into the Nextcloud database. docker exec -it nextcloud bash cd /config/www/nextcloud/ sudo -u abc php7 occ files:scan

Yeah I always use the command line version.

Was a fresh pull...... or at least that's what I asked for...

Damnit I'll do the investigating then. It's an issue with their site, popped into their Discord channel and it's been reported.

@mrbilky Get rid of your plex appdata, remove the container and the image and reinstall. On the FIRST install, post your logs and your docker run command like I have below docker run -d --name='plex' --net='host' -e TZ="Europe/London" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -v '/mnt/user/movies/':'/movies':'rw' -v '/mnt/user/tv/':'/tv':'rw' -v '/mnt/user/music/':'/music':'rw' -v '/mnt/disks/virtualisation/.appdata/plex-test':'/config':'rw,slave' 'linuxserver/plex' [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... ##################################################### # Login via the webui at http://<ip>:32400/web # # and restart the docker, because there was no # # preference file found, possibly first startup. # ##################################################### [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. [services.d] done. dbus[272]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 for mDNS. Joining mDNS multicast group on interface veth73d18bc.IPv6 with address fe80::b0b3:3ff:feef:8ad4. New relevant interface veth73d18bc.IPv6 for mDNS. Joining mDNS multicast group on interface veth0c26bb0.IPv6 with address fe80::a88a:5cff:fe98:6b73. New relevant interface veth0c26bb0.IPv6 for mDNS. Joining mDNS multicast group on interface veth6e2d851.IPv6 with address fe80::2c7b:85ff:fe87:48d. New relevant interface veth6e2d851.IPv6 for mDNS. Joining mDNS multicast group on interface veth0b7125d.IPv6 with address fe80::801e:31ff:fede:bc8f. New relevant interface veth0b7125d.IPv6 for mDNS. Joining mDNS multicast group on interface vethe473a31.IPv6 with address fe80::f046:5bff:fecd:f333. New relevant interface vethe473a31.IPv6 for mDNS. Joining mDNS multicast group on interface vethc0ba8de.IPv6 with address fe80::1493:67ff:feaf:f9c4. New relevant interface vethc0ba8de.IPv6 for mDNS. Joining mDNS multicast group on interface veth023105f.IPv6 with address fe80::fc7a:3fff:fe08:b9bd. New relevant interface veth023105f.IPv6 for mDNS. Joining mDNS multicast group on interface veth3f99e43.IPv6 with address fe80::3c4c:dff:fe71:c4d7. New relevant interface veth3f99e43.IPv6 for mDNS. Joining mDNS multicast group on interface veth011c810.IPv6 with address fe80::f41b:7eff:fef4:7e16. New relevant interface veth011c810.IPv6 for mDNS. Joining mDNS multicast group on interface veth04bd526.IPv6 with address fe80::1c8a:63ff:fe45:49e7. New relevant interface veth04bd526.IPv6 for mDNS. Joining mDNS multicast group on interface veth16dee29.IPv6 with address fe80::c89b:17ff:fefe:96f0. New relevant interface veth16dee29.IPv6 for mDNS. Joining mDNS multicast group on interface vethe1a3273.IPv6 with address fe80::84e:3aff:fedc:b39a. New relevant interface vethe1a3273.IPv6 for mDNS. Joining mDNS multicast group on interface veth23bb0b2.IPv6 with address fe80::5099:eff:fe51:62eb. New relevant interface veth23bb0b2.IPv6 for mDNS. Joining mDNS multicast group on interface vethe0abaf8.IPv6 with address fe80::4461:79ff:fe8a:8fbd. New relevant interface vethe0abaf8.IPv6 for mDNS. Joining mDNS multicast group on interface veth51892a4.IPv6 with address fe80::60e2:eaff:febd:c4d2. New relevant interface veth51892a4.IPv6 for mDNS. Joining mDNS multicast group on interface veth21785d9.IPv6 with address fe80::6880:a5ff:fe8a:c531. New relevant interface veth21785d9.IPv6 for mDNS. Joining mDNS multicast group on interface veth47495d9.IPv6 with address fe80::742c:dfff:fe01:8c4d. New relevant interface veth47495d9.IPv6 for mDNS. Joining mDNS multicast group on interface veth3e45e33.IPv6 with address fe80::5c5c:2bff:fe15:c63f. New relevant interface veth3e45e33.IPv6 for mDNS. Joining mDNS multicast group on interface veth78c341e.IPv6 with address fe80::14e9:4fff:fed7:5345. New relevant interface veth78c341e.IPv6 for mDNS. Joining mDNS multicast group on interface vethf035633.IPv6 with address fe80::c004:6fff:fe9a:65fe. New relevant interface vethf035633.IPv6 for mDNS. Joining mDNS multicast group on interface vethafd8338.IPv6 with address fe80::ec3b:3aff:fe58:a5ab. New relevant interface vethafd8338.IPv6 for mDNS. Joining mDNS multicast group on interface veth0d2e265.IPv6 with address fe80::9c42:45ff:fed9:679e. New relevant interface veth0d2e265.IPv6 for mDNS. Joining mDNS multicast group on interface vethe6803dd.IPv6 with address fe80::c00b:5ff:fe22:a48a. New relevant interface vethe6803dd.IPv6 for mDNS. Joining mDNS multicast group on interface veth241b8af.IPv6 with address fe80::906d:87ff:feba:a655. New relevant interface veth241b8af.IPv6 for mDNS. Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:aeff:fe47:1dd2. New relevant interface docker0.IPv6 for mDNS. Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv6 with address fe80::5c97:34ff:fe2d:f7b9. New relevant interface br0.IPv6 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 192.168.0.1. New relevant interface br0.IPv4 for mDNS. Joining mDNS multicast group on interface eth0.IPv6 with address fe80::ae1f:6bff:fe1b:4d76. New relevant interface eth0.IPv6 for mDNS. Network interface enumeration completed. Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for fe80::b0b3:3ff:feef:8ad4 on veth73d18bc.*. Registering new address record for fe80::a88a:5cff:fe98:6b73 on veth0c26bb0.*. Registering new address record for fe80::2c7b:85ff:fe87:48d on veth6e2d851.*. Registering new address record for fe80::801e:31ff:fede:bc8f on veth0b7125d.*. Registering new address record for fe80::f046:5bff:fecd:f333 on vethe473a31.*. Registering new address record for fe80::1493:67ff:feaf:f9c4 on vethc0ba8de.*. Registering new address record for fe80::fc7a:3fff:fe08:b9bd on veth023105f.*. Registering new address record for fe80::3c4c:dff:fe71:c4d7 on veth3f99e43.*. Registering new address record for fe80::f41b:7eff:fef4:7e16 on veth011c810.*. Registering new address record for fe80::1c8a:63ff:fe45:49e7 on veth04bd526.*. Registering new address record for fe80::c89b:17ff:fefe:96f0 on veth16dee29.*. Registering new address record for fe80::84e:3aff:fedc:b39a on vethe1a3273.*. Registering new address record for fe80::5099:eff:fe51:62eb on veth23bb0b2.*. Registering new address record for fe80::4461:79ff:fe8a:8fbd on vethe0abaf8.*. Registering new address record for fe80::60e2:eaff:febd:c4d2 on veth51892a4.*. Registering new address record for fe80::6880:a5ff:fe8a:c531 on veth21785d9.*. Registering new address record for fe80::742c:dfff:fe01:8c4d on veth47495d9.*. Registering new address record for fe80::5c5c:2bff:fe15:c63f on veth3e45e33.*. Registering new address record for fe80::14e9:4fff:fed7:5345 on veth78c341e.*. Registering new address record for fe80::c004:6fff:fe9a:65fe on vethf035633.*. Registering new address record for fe80::ec3b:3aff:fe58:a5ab on vethafd8338.*. Registering new address record for fe80::9c42:45ff:fed9:679e on veth0d2e265.*. Registering new address record for fe80::c00b:5ff:fe22:a48a on vethe6803dd.*. Registering new address record for fe80::906d:87ff:feba:a655 on veth241b8af.*. Registering new address record for fe80::42:aeff:fe47:1dd2 on docker0.*. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for fe80::5c97:34ff:fe2d:f7b9 on br0.*. Registering new address record for 192.168.0.1 on br0.IPv4. Registering new address record for fe80::ae1f:6bff:fe1b:4d76 on eth0.*.

That suggests you haven't even got to the nginx part yet, that's the LE challenge......

Yes, in the "default" file, if you want nginx to respond on port 80, you have to configure the nginx server to do so. Response to the http challenge isn't done from nginx, completely separate process.

@mrbilky Can you access Plex from any of those IP addresses? Also found this.

# Generated settings: IFNAME[0]="eth0" DHCP_KEEPRESOLV="yes" DNS_SERVER1="192.168.1.1" DNS_SERVER2="" DNS_SERVER3="" DHCP6_KEEPRESOLV="no" DESCRIPTION[0]="" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.154" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" METRIC[0]="" USE_DHCP6[0]="yes" IPADDR6[0]="" NETMASK6[0]="" GATEWAY6[0]="" PRIVACY6[0]="" MTU[0]="1500" IFNAME[1]="eth1" DESCRIPTION[1]="" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="192.168.50.2" NETMASK[1]="255.255.255.0" GATEWAY[1]="" METRIC[1]="" USE_DHCP6[1]="" MTU[1]="9000" IFNAME[2]="eth2" DESCRIPTION[2]="" PROTOCOL[2]="ipv4" USE_DHCP[2]="no" IPADDR[2]="192.168.51.2" NETMASK[2]="255.255.255.0" GATEWAY[2]="" METRIC[2]="" USE_DHCP6[2]="" IPADDR6[2]="" NETMASK6[2]="" GATEWAY6[2]="" PRIVACY6[2]="" MTU[2]="9000" SYSNICS="3" Guess that explains it, I'm betting Plex is just really confused.... No idea how to solve it though.

TLS-SNI currently isn't supported, LE have disabled it. It's included in the container only in case they reenable it at a later date. https://github.com/linuxserver/docker-letsencrypt#parameters

I got no idea what radarr.video is.......

No clue, ask the Radarr guys?

That's fine as long as your firewall/router is forwarding 443 externally to 442 on your Unraid box.

Not that I know of if you're just running :latest and not updated.

Looks like your getting IP addresses from 3 different ethernet adapters. What's the config of your Unraid server network settings?

Here's the link.

https://hub.docker.com/r/binhex/arch-medusa/ Looks like it was last pushed 5 days ago......

Default doesn't mean correct. Plus rtorrentVPN is from Binhex, Radarr from Linuxserver. Different mappings. Read the link both Squid and I posted in our replies.

Because that's how you've set up either Radarr, NZBGet or SABnzbd DockerFAQ

Works for me.... Sent from my LG-H815 using Tapatalk

@wgstarks Why don't you just request the desktop site from your mobile browser?

https://github.com/theotherp/nzbhydra/wiki/Reverse-proxies-and-URLs#nginx

Not without some configs....

The only problem I can see with this, is when your certs need renewing. @aptalca is the expert, so I may be wrong.