Can't visit locally hosted Appwrite on local server.

[regal grove]

Hi all. I'm having trouble using Appwrite in my remote Linux server. On my local home network, I have a local appwrite server that works very well. However, when I move to a public server to host my services, I have trouble making it publically available. I don't know if there's a problem with firewall cuz I'm not really experienced with firewall. Here's the log

[regal grove]

😄 please help by

[static moth]

Please avoid tagging folks individually as it can be disruptive

[barren mortar]

Have you done port forwarding in your router?

On what ports are you running Appwrite?

[regal grove]

I run the default 80 and 443

My server is public, whoch means I can ssh to it from anywhere

[barren mortar]

Looks like you didn't have allowed 443 in the firewall?

[regal grove]

You mean I have to add 443 with sudo ufw ?

[mellow finch]

This is recommended, as 443 is for https.

[regal grove]

Yeah. I haven’t figured why it doesn’t work on ny public server

Everything works well on my local laptop, which is then being tuned to ngrok for public access

[elder cedar]

Yes, HTTPS runs on port 443

[regal grove]

I added but still can't curl localhost on port 80

[grim notch]

What's the output of docker ps?

[regal grove]

here is my output

[elder cedar]

Oh, I didn’t realise you were trying on localhost - no, that shouldn’t require any firewall changes. What exactly happens when you curl localhost:80?

[regal grove]

it doesnt return anything (timeout)

[elder cedar]

It just hangs forever? That’s strange…

Could you please try running docker compose logs appwrite -n 0 -f, then curl again, and see if anything comes up?

[regal grove]

Thanks. Here is the log for docker compose logs appwrite

[elder cedar]

How did you install Appwrite?

[regal grove]

I installed it with docker compose up -d and docker-compose.yml + .env

[wintry swan]

what happens if you use ports other than 80 & 443?

[elder cedar]

Where did you get the docker-compose.yml and the .env?

[regal grove]

I got docker compose from this https://appwrite.io/install/compose

same thing for .env https://appwrite.io/install/env

[elder cedar]

So you went the manual install route?

Just to make sure - you have the .env file in the appwrite/ directory?

Is there any reason you didn’t go the recommended install route?

[regal grove]

both of the docker-compose.yml and .env are in the same folder. I run docker compose in that folder 😄

[elder cedar]

And is there any reason you didn’t use the recommended install method?

[regal grove]

isn't docker-compose the recommended method for advanced settings?

[grim notch]

please try curl -i http://localhost:80

[regal grove]

doesnt work too 😄

same config hosted on my local laptop

it works on my local laptop but doenst work on my public gpu server

[grim notch]

something must be screwed up with the docker installation 🧐

[grim notch]

what about curl -I http://127.0.0.1 and have you tried letting it run without canceling?

[grim notch]

actually, let's try curl -v http://127.0.0.1

[regal grove]

I just checked docker compose versin on both computer. They all run docker compose version v2.24.5

btw my local laptop runs ubuntu 22 while the gpu server runs ubuntu 20

[grim notch]

how did you install docker?

[regal grove]

I installed following this tutorial https://docs.docker.com/compose/install/linux/

[grim notch]

this is compose. how did you install docker?

[regal grove]

I dont really remember how I installed it but basically I followed this tutorial https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository

here's my docker version

both of my server runs on the same docker version

[grim notch]

this should be fine...

[grim notch]

i know there can be problems with installing via snap. i think the versions may line up even if you install via snap, but then weird things happen

[regal grove]

yeah. I have no idea why

I also tried hosting a web server with npm on port 3000 and still works fine when I curl on this port

[grim notch]

what if you stop the appwrite stack and then curl?

[regal grove]

connection refused Lol 😄

[grim notch]

btw, you shouldn't need to use sudo with docker commands. you may have missed this step in the installation: https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user

can you try:

docker run -p 5678:5678 --rm -d hashicorp/http-echo -text="hello world"
curl -v http://localhost:5678

[regal grove]

thanks. Let me try it again

yeap it works

the problem remains the same

[grim notch]

ok docker and networking must be fine then..

how about you wipe this appwrite installation and install using https://appwrite.io/docs/advanced/self-hosting#install-with-docker

[regal grove]

Actually, I also tried that option but it didnt work neithr

[grim notch]

Let's try from different containers

docker compose exec appwrite curl -v http://localhost/
docker compose exec traefik wget -q -S -O- http://appwrite/

[elder cedar]

The recommeded method is with the single docker command here - https://appwrite.io/docs/advanced/self-hosting#install-with-docker

[regal grove]

same old thing ^^

[wintry swan]

does it work if you do a clean install and use ports other than 80/443? 👀

[regal grove]

I just tried sudo npm run dev -- port=80 to test my project on localhost port 80 and it still works fine!

[regal grove]

what do you mean by cleaning the install ? I tried removing all docker containers and started from scratch

[wintry swan]

thats what a clean install is 😅, starting from scratch.
Can you edit the docker-compose.yml and change the default ports to something like 4444 & 5555 & restart appwrite?

I've had issues on my local installs as well with 80 & 443, so I use other ports.

[elder cedar]

This is on the same server Appwrite is running on?!

[regal grove]

yeah 😄

[regal grove]

let me give it a go

[elder cedar]

Make sure you delete the volumes too, otherwise it's not really a new install

[grim notch]

👀

this would indicate the container isn't working right...i wonder if it's some IP V6 problem...

[regal grove]

I question that too

[regal grove]

yeah I did

[elder cedar]

Do you see anything in the Traefik logs? docker compose logs traefik

[grim notch]

he can't even hit appwrite from inside the appwrite container 👀

[elder cedar]

Good point. I don’t think it’s a V6 thing - you can see in the curl log “Connected to localhost”. Unless containers aren’t able to talk to each other, I guess?

[grim notch]

oh..good point..wait i might have read things wrong..

[grim notch]

you might have too many workers for the mariadb connection...

how many cores does the server have?

[regal grove]

48 in total

😌

[grim notch]

let's try setting _APP_WORKER_PER_CORE in your .env to 1

[regal grove]

doesnt workout too 😄

haizz