Back

[SOLVED] Console not reachable anymore after making updating variables in the .env file

  • 0
  • Self Hosted
vollzeitemo
22 Nov, 2023, 13:04

Hi, I am trying to setup appwrite at the moment. I followed the guide in the documentation for self hosting. Ran the docker command, to setup the environment. After everything was created and started, I stopped the running containers and made changes to the .env file, adding smtp config etc.

When I am trying to restart the container with the command docker-compose up -d in the appwrite dir, everthing seems to be fine. Taking a look into the browser on the url I am using for the appwrite environment shows me an error message: {"message":"Error: Server Error","code":500,"version":"1.4.9"}

When I run the docker exec appwrite doctor command the output is the following (Picture as an attachment)

I am wondering if I have to change the things before powering the containers up or is there another way, than stopping, making changes and power the containers up again?

Thanks in advance!

TL;DR
Title: [SOLVED] Console not reachable after updating variables in .env file Messages: User ran the `install` command using Docker to set up Appwrite. After the containers were created and started, the user stopped them and made changes to the .env file (added SMTP config). When trying to restart the containers with `docker-compose up -d`, an error message "Error: Server Error" appeared. Running `docker exec appwrite doctor` showed an error. User asks if they should make changes before starting the containers or if there is another way. Solution: User made changes to the .env file after starting the
vollzeitemo
22 Nov, 2023, 13:05

If needed I can attach the logs of each container

D5
22 Nov, 2023, 13:10

Seems it didn't got installed properly. None of the databases are available

D5
22 Nov, 2023, 13:11

Are you using manual install?

vollzeitemo
22 Nov, 2023, 13:12

I used the install with docker

D5
22 Nov, 2023, 13:12

What's the command you ran?

vollzeitemo
22 Nov, 2023, 13:13
TypeScript
docker run -it --rm \
    --volume /var/run/docker.sock:/var/run/docker.sock \
    --volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \
    --entrypoint="install" \
    appwrite/appwrite:1.4.9
D5
22 Nov, 2023, 13:14

That looks correct

vollzeitemo
22 Nov, 2023, 13:14

After running this command I stopped the containers to edit the mariadb user and password, setting another smtp host etc.

D5
22 Nov, 2023, 13:14

That was the issue

D5
22 Nov, 2023, 13:14

You made it in the docker compose file?

vollzeitemo
22 Nov, 2023, 13:15

Yes, I made changes in the docker-compose.yml file which has been created by the install command

D5
22 Nov, 2023, 13:15

And did you have changed it from the DB directly?

D5
22 Nov, 2023, 13:15

Or only from docker compose file?

vollzeitemo
22 Nov, 2023, 13:16

Only in the docker-compose.yml, but I think now I know the issue. I have to make the changes to all running containers in the containers itself to apply them

D5
22 Nov, 2023, 13:16

That's the issue then

D5
22 Nov, 2023, 13:16

You should let the Redis DB password as default

D5
22 Nov, 2023, 13:17

And if you want to change the MariaDB password you should do it like in any other instance

vollzeitemo
22 Nov, 2023, 13:18

Ok, got that. Makes sense, should think about it one more time in the future before making any changes and wondering about why the stuff is not working 😅

vollzeitemo
22 Nov, 2023, 13:18

Thanks for the help!

vollzeitemo
22 Nov, 2023, 13:19

[SOLVED] Console not reachable anymore after making updating variables in the .env file

D5
22 Nov, 2023, 13:19

If you need help while setting the password, tell me

D5
22 Nov, 2023, 13:19

In case you still want to change it

vollzeitemo
22 Nov, 2023, 13:19

Will do that, thanks!

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more