MsDarkDiva

Thanks @Endling. I'm actually using the CA template and the :latest tag on TSDProxy. In the tsdproxy.yaml the targetHostname was already set to 172.x.x.x, so I didn't change it and the defaultProxyProvider was also set to "default". I just changed tryDockerInternalNetwork to "true" and it's up and working with Label Maker.

Nevermind! I tinkered for a while and finally got it working. Thanks anyway.

Thanks for the updates. Unfortunately, no matter what I did or how long I let it sit, it never got working. After doing more research, I found the problem is not uncommon, but the suggested fixes didn't work for me... So, I switched to Deluge, which worked right off the bat. I may try it again at some point, however I'm just beginning to set everything up, which is enough of a challenge!

Hi! I have Emby running, use swag (nginx) as reverse proxy and Authelia as 2FA. I can access it via my localip:8096, but when I sign in by my subdomain, although Authelia doesn't give me a problem, when it redirects I get a 502 bad gateway error. In the nginx log I see this: 2021/03/08 15:36:07 [error] 510#510: *209 emby could not be resolved (3: Host not found) while sending to client, client: 94.247.177.39, server: emby.*, request: "GET / HTTP/1.1", host: "emby.myusername.com", referrer: "https://emby.myusername.com/authelia/2fa/push-notification?rd=https%3A%2F%2Femby.myusername.com%2F" 2021/03/08 15:36:07 [error] 510#510: *209 emby could not be resolved (3: Host not found) while sending to client, client: 94.247.177.39, server: emby.*, request: "GET /favicon.ico HTTP/1.1", host: "emby.myusername.com", referrer: "https://emby.myusername.com/" I'm sure I broke something after adding Authelia, but I don't know what to fix or what's missing. emby.subdomain.conf

I'm having issues getting qBit to download from Sonarr/Radarr etc. The containers are running through PrivoxyVPN. Sonarr grabs the files and qBit receives the requests, but the files keeps getting stuck on "Downloading Metadata" and nothing happens. I've checked to see if Privoxy is running and it's enabled via the webui. When I test a torrent link through Ipleak, I can see that qBit is using the proxy/VPN. I have qBit's incoming connection port set at 9585, but I've noticed that Ipleak always lists the port as 1 (even if I set the container to use random ports on start up). I've included the logs after a fresh start up. sonarr sprvsrd.log qB sprvsrd.log

...Aaand the fix has stopped working! qBit and the indexers are no longer connecting for me again. I changed qBit back to my original host ip address and it connected right away. I don't know what's going on.

I guess it finally caught up to all of us. Here are the answers from the faq:

I'm not sure why this has happened as well. Everything was working and suddenly something changed and I started getting 503 errors. All of my *arr containers could no longer connect with qBittorrent, plus, all of the indexers that I set up failed. By using the 172.*.*.* ip of the container in qBit, I am now able to connect, but how do you change the address in Jackett? Do I have to manually change the url of each indexer to update it to the 172.*.*.* address?

THIS! I definitely need something to tell me when I'm making a mistake! Downloading it now. Thanks!

I appreciate your assistance and patience Sycotix. I fixed the line as you instructed, which worked. Then I spent then I spent the rest of the day chasing errors (special characters in my passwords, my Gmail needed it's own app password to work and then my user credentials were bad...). All this to say, I finally got Authelia to start! The struggle isn't over, but thank you!

Well, I got a little farther. I followed your video which made editing everything much easier! However, when I try to start Authelia I get: "Error malformed yaml: line 200: did not find expected key". The only thing at line 200 for me is a comment hashtag. Is it referring to something else?

Thanks for this Sycotix! I had Krusader installed, so I navigated to the configuration file and under properties, I found that it actually allows you to change file permissions for the Owner, Group and Others. Once I changed that, the file opened up no fuss. Now, comes the task of editing the file properly, so your video has come out just in time!

Hi, I am very new to Unraid and I have just begun following the instructions to install Authelia. For some reason, I am getting a "You do not have permission to open this file..." error, when trying to edit the configuration.yml, using Notepad++ on Windows 10. How do I fix this? I know I am probably missing something basic.