tetrapod

Also posted this to Organizr thread Having problems with getting organizr to communicate with deluge docker (using binhex-delugevpn). I have followed the instructions and downloaded the egg file WebAPI-0.4.0-py3.7.egg for Deluge. Renamed it WebAPI-0.4.0-py3.9.egg and installed it. I can however not tick the box to enable the plugin and I'm getting API Error (no. 2) when testing the connection from Organizr. I also can not find out how to remove the plugin from Deluge to start over again 😐 Is this something I can not do in this container?

Well, yes, but probably no. NGINX seems to be a trustworthy product used by many big companies. It's more that I do not trust my knowledge about security to rely on my server setup and configuration of NGINX :-$ I can see that is working, but I have no idea if it's secure. I'm now using Organizr as an authenticating wall in front of nginx. Your writeup helped me understand the concept, but I'm using Swag so I had to figure some of config out by myself (because I can't use NGINX Proxy Manager as a GUI to nginx in the Swag container - right?). I still think I'm missing something here because it works great accessing/blocking all my container GUIs from WAN, except for the Ombi app. I'd guess that is because the app have no way of authenticating itself to Organizr. But, does that mean I have to leave it out of Organizer authentication all together, or is there a way to let the Ombi API through and still protect the GUI? Maybe you can point me in the right direction @ados?

I have been going the same route and had some problems. Did you configure these ports in the binhex-delugevpn container config? I missed this and was struggling until I had read and fully understood Q24-27 in binhex exelent guide: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Having problems with getting organizr to communicate with deluge docker (using binhex-delugevpn). I have followed the instructions and downloaded the egg file WebAPI-0.4.0-py3.7.egg. Renamed it WebAPI-0.4.0-py3.9.egg and installed it. I can however not tick the box for enable and getting API Error (no. 2) when testing the connection. All the other configured arrs and media apps works great. Looks beautiful 🤘 I also can not find out how to remove the plugin to start over again 😐

@ados intro in the write-up above convinced me to try Organizr and it's now running. It looks beautiful and is so flexible. Heimdall is deleted forever and you are now on my beer supply list. My last step resulted in a problem though and I question my understanding. I run Organizer in a docker on Unraid 6.9.2. My services are reverse proxied (swag) with subdomain setup. My problem started when I started with authentication via Organizer. Worked brilliant as I wanted with different groups, level, on/off LAN access. Everything as I wanted until I came to Ombi. Now, Ombi access works fine in browser, but not the mobile app and I guess that is because it can't authenticate through Organizer and it's here that I question my understanding when I configure nginx. Following https://docs.organizr.app/books/setup-features/page/serverauth#bkmrk-swag%2Fletsencrypt-doc I have: added and edited the /config/nginx/proxy-confs/organizr-auth.subfolder.conf file edited all /config/nginx/proxy-confs/*.subdomain.conf files by adding this in the first location block: include /config/nginx/proxy-confs/organizr-auth.subfolder.conf; auth_request /auth-4; I have only added the above in the first location block even if the config file have more location blocks and it seems to work, but is this correct? The next section (Subdomain and How to include the authorization block in a reverse proxy) in the instruction I don't understand. I though I was using subdomains and reverse proxy, but it seems to work any way? What am I missing and is there a way to get the Ombi app to work or should I just exclude that from authentication?

Yes, this was on the VM. Sorry if that was unclear. root@treebeard:/etc/rc.d# ping time1.google.com PING time1.google.com (216.239.35.0) 56(84) bytes of data. 64 bytes from time1.google.com (216.239.35.0): icmp_seq=1 ttl=109 time=27.1 ms 64 bytes from time1.google.com (216.239.35.0): icmp_seq=2 ttl=109 time=27.7 ms 64 bytes from time1.google.com (216.239.35.0): icmp_seq=3 ttl=109 time=27.7 ms 64 bytes from time1.google.com (216.239.35.0): icmp_seq=4 ttl=109 time=27.3 ms ^C --- time1.google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 27.074/27.427/27.650/0.240 ms root@treebeard:/etc/rc.d# ./rc.ntpd restart Stopping NTP daemon... Starting NTP daemon: /usr/sbin/ntpd -g -u ntp:ntp root@treebeard:/etc/rc.d# tail -50 /var/lo local/ lock/ log/ root@treebeard:/etc/rc.d# tail -50 /var/log/syslog Apr 30 15:45:08 treebeard ntpd[29429]: ntpd exiting on signal 1 (Hangup) Apr 30 15:45:09 treebeard ntpd[27358]: ntpd [email protected] Tue Oct 20 18:42:21 UTC 2020 (1): Starting Apr 30 15:45:09 treebeard ntpd[27358]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Apr 30 15:45:09 treebeard ntpd[27358]: ---------------------------------------------------- Apr 30 15:45:09 treebeard ntpd[27358]: ntp-4 is maintained by Network Time Foundation, Apr 30 15:45:09 treebeard ntpd[27358]: Inc. (NTF), a non-profit 501(c)(3) public-benefit Apr 30 15:45:09 treebeard ntpd[27358]: corporation. Support and training for ntp-4 are Apr 30 15:45:09 treebeard ntpd[27358]: available at https://www.nwtime.org/support Apr 30 15:45:09 treebeard ntpd[27358]: ---------------------------------------------------- Apr 30 15:45:09 treebeard ntpd[27360]: proto: precision = 0.040 usec (-24) Apr 30 15:45:09 treebeard ntpd[27360]: basedate set to 2020-10-08 Apr 30 15:45:09 treebeard ntpd[27360]: gps base set to 2020-10-11 (week 2127) Apr 30 15:45:09 treebeard ntpd[27360]: bind(16) AF_INET 127.0.0.1#123 flags 0x5 failed: Address already in use Apr 30 15:45:09 treebeard ntpd[27360]: unable to create socket on lo (0) for 127.0.0.1#123 Apr 30 15:45:09 treebeard ntpd[27360]: failed to init interface for address 127.0.0.1 Apr 30 15:45:09 treebeard ntpd[27360]: bind(16) AF_INET6 ::1#123 flags 0x5 failed: Address already in use Apr 30 15:45:09 treebeard ntpd[27360]: unable to create socket on lo (1) for ::1#123 Apr 30 15:45:09 treebeard ntpd[27360]: failed to init interface for address ::1 Apr 30 15:45:09 treebeard ntpd[27360]: Listening on routing socket on fd #16 for interface updates Apr 30 15:45:09 treebeard ntpd[27360]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Apr 30 15:45:09 treebeard ntpd[27360]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Apr 30 15:45:11 treebeard ntpd[27360]: bind(19) AF_INET 127.0.0.1#123 flags 0x5 failed: Address already in use Apr 30 15:45:11 treebeard ntpd[27360]: unable to create socket on lo (2) for 127.0.0.1#123 Apr 30 15:45:11 treebeard ntpd[27360]: failed to init interface for address 127.0.0.1 Apr 30 15:45:11 treebeard ntpd[27360]: bind(19) AF_INET6 ::1#123 flags 0x5 failed: Address already in use Apr 30 15:45:11 treebeard ntpd[27360]: unable to create socket on lo (3) for ::1#123 Apr 30 15:45:11 treebeard ntpd[27360]: failed to init interface for address ::1 Thanks for the help so far 👍

Perfect! Thank you. Here it is. treebeard-diagnostics-20210430-1429.zip

No, I still have this problem(?) I don't think I understand what you mean. All other services on my Unraid server that access outside resources have no problem. VM server on Unraid accessing the exact same outside recourses have no problem. I get a bind error from ntpd so that should be the Unraid server Why do you mean that the problem should be outside Unraid? I'm sorry, I do not understand. You mean this forum, the one I posted this in - a month ago?

Ok, thank you for info. I'm pretty new to Unraid. Can I ask where you would think the best place to ask for help in this matter is?

Ahhh, sorry, yes that works Thank you for testing! 👍 I think your log is the syslog - right? My log above if from standard out and I'm running with higher log level (-d). The lines without timestamp do not end up in the syslog Still, you have: Listen normally on 0 lo 127.0.0.1:123 Listen normally on 1 br0 192.168.9.182:123 Listen normally on 2 lo [::1]:123 I instead have: bind(16) AF_INET 127.0.0.1#123 flags 0x5 failed: Address already in use unable to create socket on lo (0) for 127.0.0.1#123 failed to init interface for address 127.0.0.1 bind(16) AF_INET6 ::1#123 flags 0x5 failed: Address already in use unable to create socket on lo (1) for ::1#123 failed to init interface for address ::1 Listening on routing socket on fd #16 for interface updates So something network is fishy, but I can't imagine why. That's why I gave the Ubuntu example from where seen from outside the Unraid box they are on the same network. I change the config of the time server with time1.google.com. I stop the ntp service and manually change the clock to "wrong" time. Start the service again and the time will be changed. May I ask which time servers you have set?

I don't have a plugin named "update". What do you mean? But the server works fine with a bunch of dockers, services and VMs

At the time of this test the server clock was som 9 minutes ahead /usr/sbin/ntpd -gd -u ntp:ntp 30 Apr 12:20:06 ntpd[11200]: ntpd [email protected] Tue Oct 20 18:42:21 UTC 2020 (1): Starting 30 Apr 12:20:06 ntpd[11200]: Command line: /usr/sbin/ntpd -gd -u ntp:ntp 30 Apr 12:20:06 ntpd[11200]: ---------------------------------------------------- 30 Apr 12:20:06 ntpd[11200]: ntp-4 is maintained by Network Time Foundation, 30 Apr 12:20:06 ntpd[11200]: Inc. (NTF), a non-profit 501(c)(3) public-benefit 30 Apr 12:20:06 ntpd[11200]: corporation. Support and training for ntp-4 are 30 Apr 12:20:06 ntpd[11200]: available at https://www.nwtime.org/support 30 Apr 12:20:06 ntpd[11200]: ---------------------------------------------------- 30 Apr 12:20:06 ntpd[11200]: proto: precision = 0.090 usec (-23) Finished Parsing!! 30 Apr 12:20:06 ntpd[11200]: basedate set to 2020-10-08 30 Apr 12:20:06 ntpd[11200]: gps base set to 2020-10-11 (week 2127) hack_restrict: op RESTRICT_FLAGS addr 0.0.0.0 mask 0.0.0.0 ippeerlimit -1 mflags 00000000 rflags 00000bd0 hack_restrict: op RESTRICT_FLAGS addr :: mask :: ippeerlimit -1 mflags 00000000 rflags 00000bd0 hack_restrict: op RESTRICT_FLAGS addr :: mask :: ippeerlimit -1 mflags 00000000 rflags 00000bd0 hack_restrict: op RESTRICT_FLAGS addr 127.0.0.1 mask 255.255.255.255 ippeerlimit -1 mflags 00000000 rflags 00000000 hack_restrict: op RESTRICT_FLAGS addr ::1 mask ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff ippeerlimit -1 mflags 00000000 rflags 00000000 move_fd: estimated max descriptors: 40960, initial socket boundary: 16 30 Apr 12:20:06 ntpd[11200]: bind(16) AF_INET 127.0.0.1#123 flags 0x5 failed: Address already in use 30 Apr 12:20:06 ntpd[11200]: unable to create socket on lo (0) for 127.0.0.1#123 30 Apr 12:20:06 ntpd[11200]: failed to init interface for address 127.0.0.1 30 Apr 12:20:06 ntpd[11200]: bind(16) AF_INET6 ::1#123 flags 0x5 failed: Address already in use 30 Apr 12:20:06 ntpd[11200]: unable to create socket on lo (1) for ::1#123 30 Apr 12:20:06 ntpd[11200]: failed to init interface for address ::1 30 Apr 12:20:06 ntpd[11200]: Listening on routing socket on fd #16 for interface updates newpeer(127.127.1.0) - ippeerlimit -1 ignored key_expire: at 0 associd 17054 peer_clear: at 0 next 1 associd 17054 refid INIT event at 0 LOCAL(0) 8011 81 mobilize assoc 17054 newpeer: <null>->127.127.1.0 mode 3 vers 4 poll 6 6 flags 0x9 0x1 ttl 0 key 00000000 newpeer(192.168.178.1) - ippeerlimit -1 ignored key_expire: at 0 associd 17055 peer_clear: at 0 next 2 associd 17055 refid INIT event at 0 192.168.178.1 8011 81 mobilize assoc 17055 newpeer: <null>->192.168.178.1 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl 0 key 00000000 kernel loop status 0x2041 (Clock Unsynchronized) 30 Apr 12:20:06 ntpd[11200]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized event at 0 0.0.0.0 c01d 0d kern kernel time sync enabled kernel loop status 0x2041 (Clock Unsynchronized) 30 Apr 12:20:06 ntpd[11200]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized event at 0 0.0.0.0 c012 02 freq_set kernel 0.000 PPM event at 0 0.0.0.0 c011 01 freq_not_set event at 0 0.0.0.0 c016 06 restart peer_name_resolved(time.google.com) rescode 0 newpeer(216.239.35.0) - ippeerlimit -1 ignored key_expire: at 0 associd 17056 peer_clear: at 0 next 3 associd 17056 refid INIT event at 0 216.239.35.0 8011 81 mobilize assoc 17056 newpeer: <null>->216.239.35.0 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl 0 key 00000000 peer_name_resolved(ntp.pool.org) rescode 0 newpeer(64.99.80.121) - ippeerlimit -1 ignored key_expire: at 0 associd 17057 peer_clear: at 0 next 0 associd 17057 refid INIT event at 0 64.99.80.121 8011 81 mobilize assoc 17057 newpeer: <null>->64.99.80.121 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl 0 key 00000000 refclock_transmit: at 1 127.127.1.0 refclock_receive: at 1 127.127.1.0 event at 1 LOCAL(0) 8014 84 reachable refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000 clock_filter: n 1 off 0.000000 del 0.000000 dsp 7.937500 jit 0.000000 auth_agekeys: at 1 keys 0 expired 0 30 Apr 12:20:08 ntpd[11200]: bind(19) AF_INET 127.0.0.1#123 flags 0x5 failed: Address already in use 30 Apr 12:20:08 ntpd[11200]: unable to create socket on lo (2) for 127.0.0.1#123 30 Apr 12:20:08 ntpd[11200]: failed to init interface for address 127.0.0.1 30 Apr 12:20:08 ntpd[11200]: bind(19) AF_INET6 ::1#123 flags 0x5 failed: Address already in use 30 Apr 12:20:08 ntpd[11200]: unable to create socket on lo (3) for ::1#123 30 Apr 12:20:08 ntpd[11200]: failed to init interface for address ::1 refclock_transmit: at 65 127.127.1.0 refclock_receive: at 65 127.127.1.0 refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000 clock_filter: n 2 off 0.000000 del 0.000000 dsp 3.937740 jit 0.000000 refclock_transmit: at 129 127.127.1.0 refclock_receive: at 129 127.127.1.0 refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000 clock_filter: n 3 off 0.000000 del 0.000000 dsp 1.937980 jit 0.000000 refclock_transmit: at 193 127.127.1.0 refclock_receive: at 193 127.127.1.0 refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000 clock_filter: n 4 off 0.000000 del 0.000000 dsp 0.938160 jit 0.000000 refclock_transmit: at 257 127.127.1.0 refclock_receive: at 257 127.127.1.0 refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000 clock_filter: n 5 off 0.000000 del 0.000000 dsp 0.438280 jit 0.000000 30 Apr 12:25:08 ntpd[11200]: bind(19) AF_INET 127.0.0.1#123 flags 0x5 failed: Address already in use 30 Apr 12:25:08 ntpd[11200]: unable to create socket on lo (4) for 127.0.0.1#123 30 Apr 12:25:08 ntpd[11200]: failed to init interface for address 127.0.0.1 30 Apr 12:25:08 ntpd[11200]: bind(19) AF_INET6 ::1#123 flags 0x5 failed: Address already in use 30 Apr 12:25:08 ntpd[11200]: unable to create socket on lo (5) for ::1#123 30 Apr 12:25:08 ntpd[11200]: failed to init interface for address ::1 refclock_transmit: at 321 127.127.1.0 refclock_receive: at 321 127.127.1.0 refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000 clock_filter: n 6 off 0.000000 del 0.000000 dsp 0.188355 jit 0.000000 select: combine offset 0.000000000 jitter 0.000000000 event at 321 LOCAL(0) 901a 8a sys_peer clock_update: at 321 sample 321 associd 17054 event at 321 0.0.0.0 c514 04 freq_mode local_clock: offset 0.000000000 jit 0.000000119 freq 0.000 stab 0.000 poll 6 select: combine offset 0.000000000 jitter 0.000000000 select: combine offset 0.000000000 jitter 0.000000000 select: combine offset 0.000000000 jitter 0.000000000 refclock_transmit: at 385 127.127.1.0 refclock_receive: at 385 127.127.1.0 refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000 clock_filter: n 7 off 0.000000 del 0.000000 dsp 0.063400 jit 0.000000 select: combine offset 0.000000000 jitter 0.000000000 clock_update: at 385 sample 385 associd 17054 select: combine offset 0.000000000 jitter 0.000000000 select: combine offset 0.000000000 jitter 0.000000000 select: combine offset 0.000000000 jitter 0.000000000 refclock_transmit: at 449 127.127.1.0 refclock_receive: at 449 127.127.1.0 refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000 clock_filter: n 8 off 0.000000 del 0.000000 dsp 0.000926 jit 0.000000 select: combine offset 0.000000000 jitter 0.000000000 clock_update: at 449 sample 449 associd 17054 select: combine offset 0.000000000 jitter 0.000000000 select: combine offset 0.000000000 jitter 0.000000000 select: combine offset 0.000000000 jitter 0.000000000 refclock_transmit: at 513 127.127.1.0 refclock_receive: at 513 127.127.1.0 refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000 clock_filter: n 8 off 0.000000 del 0.000000 dsp 0.000926 jit 0.000000 select: combine offset 0.000000000 jitter 0.000000000 clock_update: at 513 sample 513 associd 17054 select: combine offset 0.000000000 jitter 0.000000000 select: combine offset 0.000000000 jitter 0.000000000 select: combine offset 0.000000000 jitter 0.000000000 refclock_transmit: at 577 127.127.1.0 refclock_receive: at 577 127.127.1.0 refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000000 clock_filter: n 8 off 0.000000 del 0.000000 dsp 0.000926 jit 0.000000 select: combine offset 0.000000000 jitter 0.000000000 clock_update: at 577 sample 577 associd 17054 select: combine offset 0.000000000 jitter 0.000000000 select: combine offset 0.000000000 jitter 0.000000000 select: combine offset 0.000000000 jitter 0.000000000 30 Apr 12:30:08 ntpd[11200]: bind(19) AF_INET 127.0.0.1#123 flags 0x5 failed: Address already in use 30 Apr 12:30:08 ntpd[11200]: unable to create socket on lo (6) for 127.0.0.1#123 30 Apr 12:30:08 ntpd[11200]: failed to init interface for address 127.0.0.1 30 Apr 12:30:08 ntpd[11200]: bind(19) AF_INET6 ::1#123 flags 0x5 failed: Address already in use 30 Apr 12:30:08 ntpd[11200]: unable to create socket on lo (7) for ::1#123 30 Apr 12:30:08 ntpd[11200]: failed to init interface for address ::1

I stopped the service and started it again with higher log level. Can the bind error be a clue? https://pastebin.com/g2dV3p9T

NTP still doesn't work. Anyone having an idea regarding this? I installed a Ubuntu VM on the Unraid server and now set default NTP server to time.google.com on both of them. On Ubuntu VM time is set, on Unraid not. As I described I can set the time manually, but I like NTP to work.

Thank you @ados! I have now reach the point where I think this is the way to go. Will start with your writeup now. If I can make one comment regarding the whole subject of security it would be that for me, and I'm sure a lot of other people using unraid as a springboard for setting up your home server, this is really complicated. Getting the arrs up and running is not so hard even if you never done anything like this before and the result if you do something wrong is usually that it doesn't work as expected and you have to troubleshoot. I can get a multitude of security measures to work, but it's much more difficult to understand if it's actually secure - how would I do that?

Thank you @ados! I have now reach the point where I think this is the way to go. Will start with your writeup now. If I can make one comment regarding the whole subject of security it would be that for me, and I'm sure a lot of other people using unraid as a springboard for setting up your home server, this is really complicated. Getting the arrs up and running is not so hard even if you never done anything like this before and the result if you do something wrong is usually that it doesn't work as expected and you have to troubleshoot. I can get a multitude of security measures to work, but it's much more difficult to understand if it's actually secure - how would I do that?

Nice write-up! I was struggling with this three weeks ago when starting with reverse proxy. In the end I went with swag and did the job understanding that route. But if I had this information then it could have been different. Maybe it should be copied to other places also?

Which one is the new method? Is it this one? https://www.reddit.com/r/unRAID/comments/m7wn5j/guide_routing_containers_through_your_vpns/

This was the clue. I changed 'Basic' <AuthenticationMethod> in config.xml to 'None' for sonarr, lidarr and radarr (the ones I changed log level on) - and now I get in. But, how? What? could have made the 'Basic' authentication fail? What I did was changing loglevel in three dockers and restarting them??? And now I also get in to the GUI for jackett, sabnzbd and delugevpn again without changing anything in those dockers - and with the same credentia as I used before the problem started?!? I need to get another authentication method...

Thank you for answering, but that was me even f....g up the replace when I copied in the list. The 6 was the last byte in the IP address :-$ This is correct: binhex-delugevpn - bridge - [localhost] 8112,8118,58846,58946 binhex-jackett - bridge - [localhost] 9117 binhex-krusader - bridge - [localhost] 6080 binhex-lidarr - bridge - [localhost] 8686 binhex-plexpasshost - [localhost] binhex-radarr - bridge - [localhost] 7878 binhex-sabnzbd - bridge - [localhost] 8080,8090 binhex-sonarr - bridge - [localhost] 8989,9897 Cloudflare-DDNS - bridge - 172.17.0.7 duckdnshost [localhost]??? mariadb - bridge - [localhost] 3306 nextcloud - bridge - [localhost] 444 ombi - bridge - [localhost] 3579 swag - bridge - [localhost] 180,1443 tautulli - bridge - [localhost] 8181

My first Unraid server have been online for a couple of weeks now and everything have been pretty smooth sailing so far even if I'm a total noob at using anything of the SW listed here under. Thank you Binhex for making it easy (Y) ...until now - everything starting with binhex broke 😞 This is what I have running binhex-delugevpn - bridge - [localhost] .68112,8118,58846,58946 binhex-jackett - bridge - [localhost] .69117 binhex-krusader - bridge - [localhost] .66080 binhex-lidarr - bridge - [localhost] .68686 binhex-plexpasshost - [localhost] . binhex-radarr - bridge - [localhost] .67878 binhex-sabnzbd - bridge - [localhost] .68080,8090 binhex-sonarr - bridge - [localhost] .68989,9897 Cloudflare-DDNS - bridge - 172.17.0.7 duckdnshost [localhost]??? mariadb - bridge - [localhost] .63306 nextcloud - bridge - [localhost] .6444 ombi - bridge - [localhost] .63579 swag - bridge - [localhost] .6180,1443 tautulli - bridge - [localhost] .68181 I had SWAG setup to use my cloudflare subdomains running with DNS update so the only NAT I have configured is 443 (and the one for PLEX). Worked fine for a week... So my problem started when, and I have a hard time understanding that it would be because, I changed the log level on sonarr, radarr and lidarr to 'debug' (had som problem with lidarr and was looking for clues), restarted the containers; and now I can't get into the webUI to any binhex dockers (except binhex-plexpasshost). I get a 401 from LAN, and from WAN I get the browser log on messege for the services, but my usr/passwd is not accepted. or I get a 502 from nginx. Nextcloud, plex, tautulli and ombi are still working which all have the same basic setup as the binex dockers running through swag (where I set all x.subdomain.conf in appdata\swag\nginx\proxy-confs to LAN IP). So, it's not only binhex-sonarr, but I had to start somewhere. It must be something basic that I overlooked and/or don't understand when so much breaks at the same time 😞 The dockers starts fine, there are no general Error what I can see. I can reach the logfiles and have shell access to the dockers. Checking the logfiles for sonarr I see I'm running Version 3.0.6.1196 and requesting webUI from Unraid I get this line in the log: [Info] Auth: Auth-Unauthorized ip [LANpc] url 'http://[localhost]:8989' I have to admit that routing inside Unraid still is a little mysterious for me and I don't quite understand what I'm doing :-$

I noticed that the time on the server was way of and have been playing with the date & time settings. I have since server start been on default with using NTP and the servers set to time*.google.com If I change the Time Zone the time on the server will change relative to what the (wrong) current time is. I can choose to not use NTP and set a new time. If I then switch back to NTP my new time will not change, no matter if I have set it to correct time local time with correct Time Zone or set it totally wrong. I have tried entering different time servers with no change in behavior and I have tested that I can ping the servers from the terminal. Any ideas?