Authentik

Name of the Script

Authentik

Script Type

CT (LXC Container)

📋 Script Details

Authentik Readd

The following commit caused the script to break:
192452a

This is due to the removal of the check_for_gh_tag function and the tag mode of the fetch_and_deploy_gh_release function from the tools.func file.
I tried to convert the script to use the check_for_gh_release function, which works, but fetch_and_deploy_gh_release does not work properly without the tag mode, along with the authentic release mode.
The problem with the operation is that the program version must be specified in the following way so that the functions mentioned above can find it: version/2026.2.0 However, this causes an error during the download due to the following line:
filename="${app_lc}-${version}.tar.gz"
since the version is in the name of the file but the version must be specified in the above way, the code causes an illegal character / to be inserted into the filename, which interrupts the script's execution.
If I just specify the version as 2026.2.0 fetch_and_deploy_gh_release will not find the file to download.
If the tools.func file remains as is, I will have to develop my own deployment method for the script to work.

Okay, I just found the fetch_and_deploy_from_url function. Based on the first test, it might work.

@MickLesk

@MickLesk shouldn't the fetch_and_deploy_gh_release take tags into account as well?

AUTHENTIK_VERSION="version/2026.2.0"
fetch_and_deploy_gh_release "authentik" "goauthentik/authentik" "tarball" "${AUTHENTIK_VERSION}" "/opt/authentik"

like immich

Okay, my mistake, I configured the test environment incorrectly. I tested again and modified the script to use fetch_and_deploy_gh_release .

Are there plans to fully configure the install, like omitting Postgres and supplying credentials instead?

I know it's in development still

If this isn't the place to ask, my bad : )

Are there plans to fully configure the install, like omitting Postgres and supplying credentials instead?

I know it's in development still

If this isn't the place to ask, my bad : )

Sorry, I'm a bit confused, I don't really understand what you mean.

Authentik stores user data, application and provider settings and many other settings in the postgres database, so it can't be omitted.

After installation, you have to configure these according to your own environment.

If you are currently using docker-based authentik, I can describe the steps needed to migrate your data.

I believe he meant to use a preexisting postgres database rather than redeploying a new one

@ysnt-yes

@ysnt-yes normally our scripts try to include all of the things needed for the app to run in one container, however you can definitely adapt that to your own need afterwards by supplying your own database to authentik config, just with caution and you may need to update things for example pgsql by yourself.

It seems the file manager in Authentik cannot work due to some check done in Authelia itself:
https://github.com/goauthentik/authentik/blob/f60527ce94c00ad11b9165b55d4f77ef52416b02/authentik/admin/files/backends/file.py#L55

    def manageable(self) -> bool:
        # Check _base_dir (the mount point, e.g. /data) rather than base_path
        # (which includes usage/schema subdirs, e.g. /data/media/public).
        # The subdirectories are created on first file write via mkdir(parents=True)
        # in save_file(), so requiring them to exist beforehand would prevent
        # file creation on fresh installs.
        return (
            self._base_dir.exists()
            and (self._base_dir.is_mount() or (self._base_dir / self.usage.value).is_mount())
            or (settings.DEBUG or settings.TEST)
        )

However, the /opt/authentik-data folder is not a mount.
A solution for this may be to create a second volume for the Authentik CT and mount it to /opt/authentik-data.

It seems the file manager in Authentik cannot work due to some check done in Authelia itself: https://github.com/goauthentik/authentik/blob/f60527ce94c00ad11b9165b55d4f77ef52416b02/authentik/admin/files/backends/file.py#L55
    def manageable(self) -> bool:
        # Check _base_dir (the mount point, e.g. /data) rather than base_path
        # (which includes usage/schema subdirs, e.g. /data/media/public).
        # The subdirectories are created on first file write via mkdir(parents=True)
        # in save_file(), so requiring them to exist beforehand would prevent
        # file creation on fresh installs.
        return (
            self._base_dir.exists()
            and (self._base_dir.is_mount() or (self._base_dir / self.usage.value).is_mount())
            or (settings.DEBUG or settings.TEST)
        )
However, the /opt/authentik-data folder is not a mount. A solution for this may be to create a second volume for the Authentik CT and mount it to /opt/authentik-data.

Thanks for the comment.
I'm working on the solution.

Installed and have been using for a few weeks, works great, no issues. Using it as an OIDC provider for Proxmox using local users in Authentik.

give us a go, if we can merge it to VE (Live)

Are you sure that we shouldn't investigate the GitHub resolve error further? I would guess even more people will have problems with it, if we release like this

Its not our issue.

I deleted the previous LxC and did a completely new installation. The old one asked if I wanted to upgrade Proxmox components, which I did, but the new one didn't. Perhaps something didn't work properly there. In summary, with the new installation and without updating Proxmox, everything went smoothly.

New one didn't ask, because you updated the needed dependency on the previous install

tested the install and seems to work fine for me.

New one didn't ask, because you updated the needed dependency on the previous install

of course, that's what I said, first - update needed dependency (error), and second without update works ok

Confirmed ok to go.

For the guys who have authentik in productive usage, you can run inside your pve node:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/refs/heads/main/tools/pve/switch_from_VED_to_VE.sh)"

=> but before, add following tag to your authentik: community-script-dev
that migrate the container to VE.

If its fail (i dont think so), maybe you should reinstall it after Live merge.

For the guys who have authentik in productive usage, you can run inside your pve node:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/refs/heads/main/tools/pve/switch_from_VED_to_VE.sh)"

=> but before, add following tag to your authentik: community-script-dev that migrate the container to VE.

If its fail (i dont think so), maybe you should reinstall it after Live merge.

You already have a community-script tag, and my proxmox didn't want to add a community-script-dev.
Instead of add, i've change the community-script tag in community-script-dev and it worked well.

Navigation Menu

Repository navigation

Authentik #1500

Name of the Script

Script Type

📋 Script Details

I know it's in development still

If this isn't the place to ask, my bad : )

I know it's in development still

If this isn't the place to ask, my bad : )

48 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Authentik #1500

Description

Name of the Script

Script Type

📋 Script Details

Activity

thieneret commented on Feb 28, 2026

thieneret commented on Feb 28, 2026

CrazyWolf13 commented on Mar 2, 2026

MickLesk commented on Mar 2, 2026

thieneret commented on Mar 2, 2026

ysnt-yes commented on Mar 19, 2026

I know it's in development still

If this isn't the place to ask, my bad : )

thieneret commented on Mar 19, 2026

I know it's in development still

If this isn't the place to ask, my bad : )

Alienlog commented on Mar 26, 2026

CrazyWolf13 commented on Mar 26, 2026

grumlu commented on Apr 12, 2026

thieneret commented on Apr 14, 2026

jwindfelder commented on Apr 21, 2026

48 remaining items

MickLesk commented on May 10, 2026

ZtormTheCat commented on May 11, 2026

MickLesk commented on May 11, 2026

qristo76 commented on May 11, 2026

ZtormTheCat commented on May 11, 2026

CrazyWolf13 commented on May 11, 2026

qristo76 commented on May 11, 2026

CerberusStyle commented on May 11, 2026

MickLesk commented on May 12, 2026

e4glenight commented on May 12, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions