[BUG] Authelia requests redirects to 404 on latest version

[ofersadan85]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Updating the latest files after this message

 ┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
 │  old date  │  new date  │ path                                                                   │
 ├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
 │ 2024-03-16 │ 2025-03-25 │ /config/nginx/authelia-server.conf                                     │
 └────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘

Completely broken the normal authelia (latest version) setup. All auth redirects are sent to /authelia which seems to have been removed in 15a3bc9 and 8caf2a1 despite the fact that the commit messages for those do not indicate this change

Expected Behavior

Authelia auth requests should work as expected, redirects to /authelia specifically

Steps To Reproduce

Activate the "swag" container with "authelia" as an auth service

Environment

- OS:Ubuntu 24.04
- How docker service was installed: distro's package manager

CPU architecture

x86-64

Docker creation

This docker compose file (with other details removed)

services:
  authelia:
    image: authelia/authelia
    container_name: authelia
    # OTHER CONFIGURATION REMOVED

  swag:
    image: linuxserver/swag
    container_name: swag
    # OTHER CONFIGURATION REMOVED

Container logs

**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2024-03-16 │ 2025-03-25 │ /config/nginx/authelia-server.conf                                     │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘

[ofersadan85]

Additional note: the change also included authelia-location.conf but that change did not break anything, only authelia-server.conf seems to break

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[ofersadan85]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

No feedback from OP? Is there anything else needed from me?

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[HannesJo0139]

Ping @nemchik

[drizuid]

i will just type a few notes

1. the authelia config has been fully validated by the authelia team themselves. we work directly with them on any changes we make. the current configs are aligned with authelia's latest documentation and version and have been thoroughly tested
2. there is an expectation that you are running an up to date version of authelia, if you are NOT, you should not use up to date versions of the authelia confs in swag.

[HannesJo0139]

i will just type a few notes

1. the authelia config has been fully validated by the authelia team themselves. we work directly with them on any changes we make. the current configs are aligned with authelia's latest documentation and version and have been thoroughly tested

2. there is an expectation that you are running an up to date version of authelia, if you are NOT, you should not use up to date versions of the authelia confs in swag.

Well, following up some notes from my side:

1. Authelia in its current version supports a subdomain and a subfolder config.
2. So far, also Swag supported subfolder configs of Authelia.
3. I can nowhere find any notes that subfolder support had been dropped. Not on the Authelia, nor on the Swag side
4. Swag silently dropped subfolder handling of it's Authelia config with the latest refactorization.
5. At this point, updating Swag will break any subfolder Authelia setup.
6. It is not a Authelia update breaking things, it is a Swag update.
7. In fact, the latest Swag refactor breaks subfolder Authelia setups. May it be validated or not does not matter actually.

[ofersadan85]

i will just type a few notes

1. the authelia config has been fully validated by the authelia team themselves. we work directly with them on any changes we make. the current configs are aligned with authelia's latest documentation and version and have been thoroughly tested
2. there is an expectation that you are running an up to date version of authelia, if you are NOT, you should not use up to date versions of the authelia confs in swag.

Just to be clear, the Authelia container is updated, and so is SWAG to report this break. I had to revert SWAG (and not Authelia) for it to work.

If you look at the commits I highlighted in OP, you can clearly see that this change was not even specified: the commit message is about removing comments for an older version, but it also removed location blocks

[drizuid]

ill go ahead and close this, we have no plans to change anything. We dropped subfolder support at Authelia's request it won't be coming back.

I didn't read the rest of this because as i mentioned, authelia validated the configs as being at the point they are willing to support, they were not willing to support directly prior to the latest commits.