starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

Authentik 'update' not upgrading embedded outpost #446

New Issue
Closed
opened 2026-02-04 18:55:43 +03:00 by OVERLORD · 10 comments
OVERLORD commented 2026-02-04 18:55:43 +03:00
Owner
Copy Link

Originally created by @Musrha on GitHub (Feb 5, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Authentik

📂 What was the exact command used to execute the script?

update (inside Authentik LXC)

📝 Provide a clear and concise description of the issue.

After updating Authentik to 2024.12.3 from 2024.12.2 using 'update', the update went successfully, but the Outpost heal inside Authentik is red. When I go to Embedded Outposts part of the admin panel it says that the outpost is still in the old version.

"2024.12.2, should be 2024.12.3"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  • Have Authentik 2024.12.2
  • Update by 'update' command.

❌ Paste the full error output (if available).

✔️ No update required. Authentik is already at vhttps://api.github.com/repos/goauthentik/authentik/tarball/version/2024.12.3
root@authentik:~#

If you try to update again it says is not needed.

🖼️ Additional context (optional).

No response

Originally created by @Musrha on GitHub (Feb 5, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Authentik ### 📂 What was the exact command used to execute the script? update (inside Authentik LXC) ### 📝 Provide a clear and concise description of the issue. After updating Authentik to 2024.12.3 from 2024.12.2 using 'update', the update went successfully, but the Outpost heal inside Authentik is red. When I go to Embedded Outposts part of the admin panel it says that the outpost is still in the old version. "2024.12.2, should be 2024.12.3" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. - Have Authentik 2024.12.2 - Update by 'update' command. ### ❌ Paste the full error output (if available). ✔️ No update required. Authentik is already at vhttps://api.github.com/repos/goauthentik/authentik/tarball/version/2024.12.3 root@authentik:~# If you try to update again it says is not needed. ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 18:55:43 +03:00
OVERLORD commented 2026-02-04 18:56:00 +03:00
Author
Owner
Copy Link

@mablerf commented on GitHub (Feb 6, 2025):

I feel better that this isn't just me. I thought I'd mucked something up when upgrading previous docker instance, then moved the database over to the lxc. It's possible I still mucked it, but not guaranteed.

@mablerf commented on GitHub (Feb 6, 2025): I feel better that this isn't just me. I thought I'd mucked something up when upgrading previous docker instance, then moved the database over to the lxc. It's possible I still mucked it, but not guaranteed.
OVERLORD commented 2026-02-04 18:56:12 +03:00
Author
Owner
Copy Link

@Musrha commented on GitHub (Feb 6, 2025):

I feel better that this isn't just me. I thought I'd mucked something up when upgrading previous docker instance, then moved the database over to the lxc. It's possible I still mucked it, but not guaranteed.

I tought about doing that myself but rebuilt all my applications and providers from scratch, so doesn't seem to be related

@Musrha commented on GitHub (Feb 6, 2025): > I feel better that this isn't just me. I thought I'd mucked something up when upgrading previous docker instance, then moved the database over to the lxc. It's possible I still mucked it, but not guaranteed. I tought about doing that myself but rebuilt all my applications and providers from scratch, so doesn't seem to be related
OVERLORD commented 2026-02-04 18:56:28 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 6, 2025):

what are "outposts" ? Where can i take a look what this is?

@MickLesk commented on GitHub (Feb 6, 2025): what are "outposts" ? Where can i take a look what this is?
OVERLORD commented 2026-02-04 18:56:30 +03:00
Author
Owner
Copy Link

@Musrha commented on GitHub (Feb 7, 2025):

Outposts are services which lets something connect to Authentik API. (As their documentation says)

Authentik comes with an embedded outpost. For example in authentik/outposts/models.py there is a variable of Outpost version and one of Authentik version (OUR_VERSION), they are the ones that mismatch.

@Musrha commented on GitHub (Feb 7, 2025): Outposts are services which lets something connect to Authentik API. (As [their documentation](https://docs.goauthentik.io/docs/add-secure-apps/outposts/) says) Authentik comes with an [embedded outpost](https://docs.goauthentik.io/docs/add-secure-apps/outposts/embedded/). For example in [authentik/outposts/models.py](https://github.com/goauthentik/authentik/blob/daebeb1192ec9d36e2a9dfb8654e362b45a38ca5/authentik/outposts/models.py#L429) there is a variable of Outpost version and one of Authentik version (OUR_VERSION), they are the ones that mismatch.
OVERLORD commented 2026-02-04 18:56:41 +03:00
Author
Owner
Copy Link

@SplendidAppendix commented on GitHub (Feb 12, 2025):

I am experiencing this issue as well.

@SplendidAppendix commented on GitHub (Feb 12, 2025): I am experiencing this issue as well.
OVERLORD commented 2026-02-04 18:56:58 +03:00
Author
Owner
Copy Link

@vidonnus commented on GitHub (Feb 13, 2025):

Bugfix PR opened for this issue.

@vidonnus commented on GitHub (Feb 13, 2025): Bugfix PR opened for this issue.
OVERLORD commented 2026-02-04 18:57:16 +03:00
Author
Owner
Copy Link

@vidonnus commented on GitHub (Feb 13, 2025):

If someone has already attempted to upgrade and encountered this issue, subsequent upgrades will fail as the script identifies the version of the application as up-to-date. Because this is true and there is no easy way to check for the embedded outpost version, I recommend anyone stuck in this limbo to:

  • log into your Authentik CT console
  • run the following command: bash -c "$(wget -qLO - https://github.com/vidonnus/ProxmoxVE/raw/bugfix/2037-force-upgrade/ct/authentik.sh)"

This will update your outpost version. Subsequent updates will work as expected using the update command.

@vidonnus commented on GitHub (Feb 13, 2025): If someone has already attempted to upgrade and encountered this issue, subsequent upgrades will fail as the script identifies the version of the application as up-to-date. Because this is true and there is no easy way to check for the embedded outpost version, I recommend anyone stuck in this limbo to: - log into your Authentik CT console - run the following command: `bash -c "$(wget -qLO - https://github.com/vidonnus/ProxmoxVE/raw/bugfix/2037-force-upgrade/ct/authentik.sh)"` This will update your outpost version. Subsequent updates will work as expected using the `update` command.
OVERLORD commented 2026-02-04 18:57:29 +03:00
Author
Owner
Copy Link

@Musrha commented on GitHub (Feb 13, 2025):

Worked like a charm. Thank you very much!

@Musrha commented on GitHub (Feb 13, 2025): Worked like a charm. Thank you very much!
OVERLORD commented 2026-02-04 18:57:42 +03:00
Author
Owner
Copy Link

@mablerf commented on GitHub (Feb 13, 2025):

Resolved that error for me as well.

@mablerf commented on GitHub (Feb 13, 2025): Resolved that error for me as well.
OVERLORD commented 2026-02-04 18:57:54 +03:00
Author
Owner
Copy Link

@atol71 commented on GitHub (Aug 24, 2025):

And how would one perform this in non-root container that is recommended? There is no wget in default Authentik container.

@atol71 commented on GitHub (Aug 24, 2025): And how would one perform this in non-root container that is recommended? There is no wget in default Authentik container.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#446
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?