Hi nojutsu42,
Thanks for kind words. The container is the official one from Authelia, I just helped collect it all and get up for everyone to use after weeks of trying to get it going.
With regards to your issue can you confirm:
- After authenticating, are you able to hit (either manually or with the redirect): sonarr.domain.com?
Your rules look good. Going forward you will want to set specific subdomain rules but here's mine atm while I'm testing each subdomain:
access_control:
# Default policy can either be 'bypass', 'one_factor', 'two_factor' or 'deny'.
# It is the policy applied to any resource if there is no policy to be applied
# to the user.
default_policy: deny
rules:
# Rules applied to 'admins' group
- domain: "*.domain.com"
subject:
- "group:admins"
policy: one_factor
The instructions I wrote for NPM utilize snippets from those letsencrypt files to get it to work. So in theory, you should not really need to change much for Let'sEncrypt
In the letsencrypt\nginx\proxy-confs you can find the sample conf for Sonarr with the lines referencing Authelia. Do you have those?
And do you also have: authelia-location.conf, authelia-server.conf
Located here: \appdata\letsencrypt\nginx