nojutsu42

Members
  • Content Count

    6
  • Joined

  • Last visited

Everything posted by nojutsu42

  1. @Sycotix It's fixed - all I did was delete the users_database.yml let Authelia recreate the file. I edited the new file with new credentials and its back up normal now.
  2. Kinda looks like it has something to do with the static username file interacting with the db.
  3. Hey Sycotix, I updated the docker with the new container uploaded to CA - I am now getting some strange database panic. Have you seen this before? panic: Invalid schema of database: Users.MYUSERNAME.DisplayName: non zero value required Prior to the update the container was functioning proper.
  4. This was super helpful. I have it functioning now! I had to edit the letsencrypt /config/nginx/autheila-server.conf and the autheila-location.conf to recognize the subdomain and not the folder. I setup DUO as well - on the "Free Trial" account, was able to get setup on the DUO dashboard, and send the 2fA. (No idea what occurs when the 30 days are up on the trial)
  5. Thanks for the reply and your suggestions. With regards to your issue can you confirm: - After authenticating, are you able to hit (either manually or with the redirect): sonarr.domain.com? Currently - before making any conf adjustments. From outside of my LAN I am able to resolve 'auth.mydomain.com' when I complete the TOTP it forwards me to a wordpress I have setup as the mydomain.com. That is the expected route as 'mydomain.com' is set as default_redirection_url: in my configuration.conf. When I resolve https://sonarr.mydomain.com it only prompts me with the sona
  6. Hi Sycotix! Really cool container thank you for building it. This is my first forum post. I pulled down the container from CA and configured it following the directions best I could. I have proper DNS resolution on the container, https://auth.mydomain.com resolves and I am able to get the google authenicator to function. On my mobile I receive the google auth code, input the code and container accepts the key and completes the request forwarding me to the default_redirection_url: https://mydomain.com/. I am on a lets encrypt container not NPM, and I have been struggling t