How to self host 1.8.x

[plucky scroll]

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

[signal sinew]

navigating to localhost:9501

go to localhost:80

[plucky scroll]

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

So 80 should be the internal container's port

[plucky scroll]

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:

•  - 80:80
  

•  - 8080:80
  

•  - 9501:80
  

•  - 9502:80
   - 443:443
   - 9500:8080
  

  volumes:
  @@ -52,8 +52,6 @@ services:
  args:
  DEBUG: false
  TESTING: true
  VERSION: dev

• ports:

•  - 9501:80
  

  networks:
  - appwrite
  labels:

[signal sinew]

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

Since I already have something running on 80

yeah so that was the issue

[low rock]

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

[low rock]

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.

[frail river]

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

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

[low rock]

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.

[white plover]

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

[frail river]

Not for self-hosting afaik

[blissful fossil]

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

[low rock]

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

[blissful fossil]

I try port 80 same thing

[low rock]

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

[blissful fossil]

Yes but the webpage don🖥´t load

[low rock]

It loaded in your screenshot

[blissful fossil]

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

[low rock]

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

The only routes (routes you’d ever be accessing) are /console and /v1

[blissful fossil]

The issue was the api

Thank you

[low rock]

Still not really sure what you were having a problem with (or how you dealt with it), but I'm glad to hear it's all working now