Issues upgrading to Authelia 4.38 using SWAG in Unraid #7250
Replies: 2 comments
-
Please note this response was created using generative AI leveraging previously available information from the repository. This information may be helpful however it is our strong recommendation that you carefully consider the information before blindly applying it. It seems like you are facing two main issues after upgrading Authelia to version 4.38 and attempting to integrate it with SWAG for your
For both issues, ensure that all configurations are reloaded properly after making changes, and consider restarting both the Authelia and SWAG containers to apply any updates. If these steps do not resolve the issues, you may need to delve deeper into the logs or consult the Authelia community or documentation for more specific guidance based on the version changes. This comment was generated by Glime. |
Beta Was this translation helpful? Give feedback.
-
Regarding the NTP Startup Check Error, the AI's suggestion of increasing the |
Beta Was this translation helpful? Give feedback.
-
Before Authelia 4.38 I had SWAG working with it correctly for my frigate.domain.com webpage. I auto upgraded my authelia container to 4.38, but I had not updated my
configuration.yml
file, resulting in frigate.domain.com being inaccessible due to obvious config issues when authelia would start.I have attempted to update my
configuration.yml
file in Authelia, as well as updating myauthelia-location.conf
andauthelia-server.conf
files in SWAG to the most recent versions. Starting up both containers, I am not met with any warnings or errors in either of their logs.I have a few issues that I am not sure how to resolve.
The first has been the most difficult for me, and that is that any time I attempt to access frigate.domain.com the below is reported in the authelia log and I am met with an error 403 on the webpage, never seeing the authelia login screen. I am able to access the frigate container from its local IP just fine, since that isnt going through swag and authelia when I try an access it through frigate.domain.com.
It seems like Authelia is being passed a anonymous user, but I never get to the Authelia login landing page when I go to frigate.domain.com, in order to attempt to login and try and access the webpage as a non-anonymous user.
Further, if I attempt to access Authelia locally via its Web UI, it produces the following error:
And the following page:
Edit: Second issue below is resolved.
The second issue is that if I dont setntp.disable_startup_check
totrue
, I am always met with the following:And I am not really sure how to resolve this. If I set itntp.disable_startup_check
tofalse
in order to get the container to start, I can rundate
within it which clearly matches the host's date, which is the exact local time. I had these exact same settings enabled and working (presumably - there certainly wasnt a startup error like this before) before this 4.38 upgrade.Below is my Authelia
configuration.yml
:Beta Was this translation helpful? Give feedback.
All reactions