2 hours ago, Waddoo said:

Remember to replace username with the username for the user you want to create.

 

Also this command is ment for docker compose, if you are not using docker compose this will not work.

 

Lastly, the docker compose command should be run in Urnaids console not Authentiks.

 

Thanks for the information.

 

When i run it in unraids terminal it says "unknown flag: --rm"

 

Thanks..

 

 

3 minutes ago, cheww said:

 

Thanks for the information.

 

When i run it in unraids terminal it says "unknown flag: --rm"

 

Thanks..

 

 

Unfortunately I am not familiar with that command and likewise unsure if Unraid's docker compose implementation is playing a role. Reach out to their discord, they are helpful there as well. Be sure to search first!

 

Unfortunately, I have stopped using Authentik, it became too much to maintain and connect all of my services with the amount of time I have in my day.

18 minutes ago, Waddoo said:

Unfortunately I am not familiar with that command and likewise unsure if Unraid's docker compose implementation is playing a role. Reach out to their discord, they are helpful there as well. Be sure to search first!

 

Unfortunately, I have stopped using Authentik, it became too much to maintain and connect all of my services with the amount of time I have in my day.

 

Oh i fixed it, i don't know how i worked it out but i did this..

 

Terminal from Unraid

type in `docker exec -it authentik /bin/bash`  (authentik being the docker app)

 

then i got a new prompt and then type in `ak` (got this from the second line from authentiks website "kubectl exec -it deployment/authentik-worker -c worker -- ak create_admin_group username") all this text popped up on the screen so i thought Hmm..

 

then type in 'ak create_admin_group username' (the user name i am using on asuthentik)

 

Then all this text came on the screen and right down the bottom i see..

 

"User 'username' successfully added to the group 'authentik Admins'."

 

Well i do say, i am very proud. lol

 

Thank you for helping.

Hi All

Just want to say that if you have the Authelia docker and its not running/starting then there is a breaking change in the last update.
I fixed it by rolling back on the DB (it made some changes) and rolled back to the older version.

Everything is running again now 🙂

Is anyone experiencing the same issue? UPDATE: i ROLLED BACK TO:

authelia/authelia:4.38.18

 

and remember to restore the DB back to when this was running the old version.
Must be some breaking changes that does not work with the new version: https://www.authelia.com/blog/4.39-release-notes/ 

If anyone have a work around for the new version then please let me know (My setup is the one Ibracorp have in there guide)
 

 

Edited March 17, 20251 yr by casperse

Someone reported that you only have to add a missing folder?
"is the /config/asset/ folder present?
I had to create that myself over the weekend to get the container to start on v4.39.0"
Can anyone confirm this?

 

On 3/17/2025 at 12:18 PM, casperse said:

Someone reported that you only have to add a missing folder?
"is the /config/asset/ folder present?
I had to create that myself over the weekend to get the container to start on v4.39.0"
Can anyone confirm this?

 

I can't get anthelia to start. I'm pretty sure my config is workable. The container won't start. I'm pulling my hair out with this.

Getting this error and authelia will not start

time="2026-01-28T09:09:21-06:00" level=info msg="Storage schema is already up to date"

time="2026-01-28T09:09:22-06:00" level=error msg="Error occurred running a startup check" error="the system clock is not synchronized accurately enough with the configured NTP server" provider=ntp

time="2026-01-28T09:09:22-06:00" level=fatal msg="One or more providers had fatal failures performing startup checks, for more details check the error level logs" providers="[ntp]" stack="github.com/authelia/authelia/v4/internal/commands/root.go:93 (*CmdCtx).RootRunE\ngithub.com/spf13/[email protected]/command.go:1015 (*Command).execute\ngithub.com/spf13/[email protected]/command.go:1148 (*Command).ExecuteC\ngithub.com/spf13/[email protected]/command.go:1071 (*Command).Execute\ngithub.com/authelia/authelia/v4/cmd/authelia/main.go:10 main\ninternal/runtime/atomic/types.go:194 (*Uint32).Load\nruntime/asm_amd64.s:1693

I have been using this for along time using IbraCorps guide and NTP server was not define. I am going to add that to my config file to see if it helps.

Update you will have to define a NTP server if did not have one before this fixed the error.

Edited January 28Jan 28 by ijuarez

Hello, I hope this is the correct forum, if not I apologize. I also apologize if this is a stupid question, but I'm a noob and I'm trying to just understand. Im might add that I use containers and not docker compose. I'm trying to set up Crowdsec with Traefik and I can't put the Traefik logs in /var/log/traefik. I have the latest Traefik up and running.

In the docs on Ibracorp.io the logs are defined as:

log:
level: INFO
format: json
accessLog:
format: json

So I have put the following in the traefik.yaml as per every description I've found (but that are for docker compose, so I don't know if it should be the same in the container)

log:

level: "INFO"

filePath: "/var/log/traefik/traefik.log"

accessLog:

filePath: "/var/log/traefik/access.log"

But there is no files in /var/log/traefik and of course there are an error in CrowdSec:

level=warning msg="No matching files for pattern /var/log/traefik/*.log" module=acquisition.file type=file

Just to verify I tried to create a new log folder in the Traefik appfolder for the logs and changed the path in Traefik.yaml to:

filePath: "/mnt/user/appdata/traefik/logs"

and voila there was the log files (it makes me wonder if it some permission issue). But that means that I break the link to the log viewer and if I try to put /mnt/user/appdata/traefik/logs/*.log in the acquis.yaml for CrowdSec it gives me the same error as when /var/log/traefik/.

While I've been investigating and trying stuff I also can say that the CrowdSec container setup reference to folders that do not exist in /var/log/ (screenshot attached). There is no folder named crowdsec or syslog, there is a folder named auth.log, but it sound as if it should be a file? Are thes folders necessary ie do they need to be created or can these be erased? Is this container made for Unraid?

As I said I'm a noob and right now I just don't understand. Maybe I'm just misunderstanding something fundamental about routing in docker. Most I've learned I've done thanks to YouTube so my knowledge about docker and such is at best spotty.

I would very much appreciate some guidance.

Thank you!

Best regards

11 hours ago, Smib666 said:

I realised two things. First I made a typo. Instead of filePath: "/mnt/user/appdata/traefik/logs" , I wrote filePath: /logs.traefik.log and filePath: /logs.access.log and that placed the log files in the folder in Traefik. The other thing is I believe is that I don’t understand how to reference the log files because I don’t understand where they live in Traefik.