Skip to content
Back

How to self host 1.8.x

  • 0
  • Self Hosted
apperside
1 Sep, 2025, 06:50

Hello, I have a running self hosted instance of appwrite 1.7.4 installed some month ago, but I read the latest announcements and a lot of cool stuff seem to have been added and I wanted to try them out. I tried to clone and run the project from the 1.8.x branch, but running the following:

docker compose build docker compose up

and navigating to localhost:9501, leads to to not found page (attached screenshot), and every navigation attempt leads also to this.

all the containers seem to be running as you can see in the screenshots.

Attached you find the "appwrite" container logs.

It actually happens also in the main branch. When I am switching branches I am always deleting containers and volumes with

docker compose down -v

So I think I am starting fresh every time.

I also tried to run a 1.8.0 docker image, but doesn't actually seem to exist, so how do I try out the new exciting things with self hosting?

Thank you

TL;DR
Developers are having trouble self-hosting Appwrite 1.8.x on ports 80 or 443. The solution involves tweaking the docker-compose file, removing port configuration from the Appwrite container, and editing the Traefik part. By assigning the internal container's port (e.g., 9501) to port 80 and accessing localhost:80, the issue can be resolved.
Chirag Aggarwal
1 Sep, 2025, 07:06

navigating to localhost:9501

go to localhost:80

apperside
1 Sep, 2025, 07:19

Uhm, but the container Is cinfigured with 9501:80 🤔

apperside
1 Sep, 2025, 07:20

So 80 should be the internal container's port

apperside
1 Sep, 2025, 07:52

Since I already have something running on 80, I managed it by tweaking the docker-compose file, removing the port confguration from appwrite container and editing the traefik part

diff --git a/docker-compose.yml b/docker-compose.yml index 1234567..abcdefg 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -27,8 +27,8 @@ services: - --entrypoints.appwrite_websecure.address=:443 - --accesslog=true ports:

  • TypeScript
     - 80:80
    
  • TypeScript
     - 8080:80
    
  • TypeScript
     - 9501:80
    
  • TypeScript
     - 9502:80
     - 443:443
     - 9500:8080
    
    volumes: @@ -52,8 +52,6 @@ services: args: DEBUG: false TESTING: true VERSION: dev
  • ports:
  • TypeScript
     - 9501:80
    
    networks: - appwrite labels:
Chirag Aggarwal
1 Sep, 2025, 09:14

9501 is the internal port 80 is ur system's port

Chirag Aggarwal
1 Sep, 2025, 09:14

Since I already have something running on 80

yeah so that was the issue

ideclon
1 Sep, 2025, 09:44

I'm pretty sure that's not the case. And if it were, they wouldn't have gotten an Appwrite error page.

ideclon
1 Sep, 2025, 09:47

Unfortunately, Appwrite doesn't really play nice with being run on a port which isn't 80 / 443, anymore. It used to be fine, but I believe that changed with 1.7. Appwrite now strictly matches the domain, and simply won't respond properly to requests to any other domain name (I believe this is because of Sites).

I believe your only real option is to set up a reverse proxy so you're still able to access Appwrite on port 80.

D5
1 Sep, 2025, 13:57

You can use a reverse proxy to route to the appwrite port, but if it's something different from trafik, I think it could conflict

D5
1 Sep, 2025, 13:58

Of course trafik needs to be running at the 80/443 but you can separate it by assigning a domain/subdomain to it

ideclon
1 Sep, 2025, 14:11

Been working perfectly well for me for the past however many years it’s been. I have Appwrite running locally on 8080/8443, then reverse proxy.

Samuel Kings
1 Sep, 2025, 16:47

Erm, is version 1.8x released yet? Like, can we start using it?

D5
1 Sep, 2025, 20:45

Not for self-hosting afaik

Fab0ne
17 Sep, 2025, 17:28

I have the same issu but when I Check it said that is currecly install

ideclon
17 Sep, 2025, 17:53

You’re going to /443, which doesn’t exist. I presume you’re trying to use :443 (SSL port) - which you’re on anyway

Fab0ne
17 Sep, 2025, 17:57

I try port 80 same thing

ideclon
17 Sep, 2025, 17:58

I’m not really sure what you’re saying here? Looks like Appwrite is working fine to me in your screenshot

Fab0ne
17 Sep, 2025, 17:58

Yes but the webpage don🖥´t load

ideclon
17 Sep, 2025, 17:59

It loaded in your screenshot

Fab0ne
17 Sep, 2025, 17:59

If I choose port 80 or 443 for https same error page

ideclon
17 Sep, 2025, 18:00

The error page is because you’re going to a page that doesn’t exist, as I said before.

There is no such page in Appwrite http://localhost/443

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