Update Authentik configuration to use HTTPS and updated ports to allow compatability with 2026.8 update. - #627
Open
HeyItsJono wants to merge 1 commit into
Open
Update Authentik configuration to use HTTPS and updated ports to allow compatability with 2026.8 update.#627HeyItsJono wants to merge 1 commit into
HeyItsJono wants to merge 1 commit into
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Thanks for opening this pull request! Be sure to follow the pull request template!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
The latest version of Authentik (2026.8) requires an update to the Nginx config to pass the https protocol and 9443 (https) port, rather than the previous configuration passing the http protocol & port (9000).
Alternatively, a user can 'trust' a CIDN in their Authentik configuration's environment with the variable
AUTHENTIK_LISTEN__TRUSTED_PROXY_CIDRS=*Docker Subnet*, though there is very little documentation on this and users are not guided to do so, which means out-of-the-box without the changes in this PR, Authentik configurations served via SWAG will fail with the bugs outlined in this Authentik issue.This will also need an update to
authentik.subdomain.confto also change$upstream_prototohttps, and set$upstream_portto9443, but I couldn't find that file in this repo to include in my PR.Benefits of this PR and context:
Fixes the errors outlined in the Authentik issue linked above and allows SWAG Authentik configurations to work out-of-the-box.
If the overall feeling is that this shouldn't be corrected on SWAG's end, and users are instead encouraged to set up the alternative fix using the Authentik environment variable, then it may be worth including a comment in the
authentik-server.confandauthentik.subdomain.conffiles to suggest users set this environment variable.How Has This Been Tested?
Tested on my own personal SWAG / Authentik config, both of which are served from the same docker compose file on a Pop!_OS host.
Source / References:
goauthentik/authentik#25559