Replies: 4 comments 1 reply
-
Hail, @henninfi 👋 Welcome to Fief's kingdom! Our team will get back to you very soon to help. In the meantime, take a minute to star our repository ⭐️ Farewell! |
Beta Was this translation helpful? Give feedback.
-
Fief server probably shows an error in its logs that may help us find out what's wrong. If you run the following command: docker logs -f fief-server You'll see the log output. Try to access your server again and see what happens. If an error stack trace appears, share it with us. |
Beta Was this translation helpful? Give feedback.
-
Thanks. I did that now. Dont know how much of it to copy/paste, but from the last line in my paste it seems i cant run it with sslmode=require. Is there a way to do this? 2023-11-30 20:35:45 2023-11-30 19:35:45,536 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. |
Beta Was this translation helpful? Give feedback.
-
I ended up creating a new postresql db. This seems to have byen the issue. I got the issue with a free db hosted by render. Swapped to free db from aiven, and things worked. Thanks for the tip anyway! |
Beta Was this translation helpful? Give feedback.
-
Hi
First off i want to thank all of you guys contributing to this project. A big shout-out to all of you.
Now, this is my first time asking for something in a repo, so please feel free to correct me if im doing this wrong.
I've used the quick-start docker-image exactly like it is from the guide (https://docs.fief.dev/self-hosting/quickstart/). At first run it runs perfectly. The docker container runs, i can access it, log in and everything seems to be working. But, as i do not want to run it as a sqlite db i've added the following to the docker run command:
-e "DATABASE_TYPE=POSTGRESQL"
-e "DATABASE_URL=postgresql://user:pw@host:port/db"
After this i cant access the localhost, as the browser shows this error:
"This page isn’t working right nowlocalhost didn’t send any data."
There do seem to be some kind of interaction to the DB because the docker run makes a new Schemas in the db by the name of a random UUID.
The same database works with the online FIEF-beta-solution, so the db-user should have suffecient permissions.
Beta Was this translation helpful? Give feedback.
All reactions