InfBoumcyCastle
Linkwarden + Authentik auth error
@Skullky @Stavros
https://github.com/runtipi/runtipi-appstore/blob/f8d18f65d3048535bcca9c7ef42a0b8c6141f428/apps/authentik/docker-compose.json#L5
https://github.com/runtipi/runtipi-appstore/blob/f8d18f65d3048535bcca9c7ef42a0b8c6141f428/apps/authentik/docker-compose.json#L37
16 replies
Linkwarden + Authentik auth error
It certainly makes sense to inspect the container to see if the env vars are applied.
Since the docker compose files get merged, they should use the same format for env vars
I hate to say it, but I had good results using chatgpt as troubleshooting help by feeding it config and logs.
16 replies
Linkwarden + Authentik auth error
well, looks similar to the output i get. i also used the same instructions you linked to.
i dont use NEXT_PUBLIC_AUTHENTIK_ENABLED, NEXTAUTH_URL and AUTHENTIK_CUSTOM_NAME maybe try w/o those? also, in case AUTHENTIK_CUSTOM_NAME is really blank - better remove it / comment it out.
otherwise - i dont see anything wrong so far
16 replies
Linkwarden + Authentik auth error
i am using oauth with linkwarden and authentik. my user-config for linkwarden is here:
https://github.com/falkheiland/user-config/tree/main/linkwarden
16 replies
docker compose volumes not mounting files
maybe a permission problem? i use homeassistant-1 but did not edit any files for the container. it seems though that the files has to be owned by root:root . are the affected files owned by root?
6 replies
docker compose volumes not mounting files
Every intended change to the standard compose has to be done in a user config. The compose in apps/ gets recreated at start to its original state.
https://runtipi.io/docs/guides/customize-app-config
6 replies
Freshrss with runtipi
i just copiloted: ( used LLM)
freshrss docker compose WARN: Probable invalid base URL in ./data/config.phpthe answer seems valid: ------------------- This warning typically indicates that the
base_url parameter in your config.php file is incorrect. It often happens if the URL or address of your FreshRSS instance has changed since the initial setup. Here's how you can address it:
1. Locate the config.php file:
- Navigate to the directory where your FreshRSS data is stored. For example, if you're using Docker, it might be in a volume like /path/to/data/www/freshrss/data/.
2. Backup the file:
- Before making any changes, create a backup of the config.php file:
3. Edit the config.php file:
- Open the file in a text editor:
- Look for the base_url parameter. It might look something like this:
- Update it to the correct URL of your FreshRSS instance:
4. Restart your Docker container:
- After saving the changes, restart your FreshRSS Docker container to apply the updates:
This should resolve the warning. If you continue to face issues, let me know, and we can troubleshoot further!
-------------------
copilot does not know about runtipi - so some paths / restart procedures are different2 replies
Wallos seemingly not applying TZ
one thing to test would be to use another timezone for testing. maybe its something with yours and the way wallos uses / sources it. i mean there would be a lot issues on github if this would not work generally i guess
18 replies
Wallos seemingly not applying TZ
hmm. i would blame wallos in that regard.
there is a similar issue https://github.com/ellite/Wallos/issues/291 that never really got a solution.
18 replies
