router_host_not_found after Upgrading to 1.4.0

[jolly oyster]

Hello there
APP has been working well until I migrated to 1.4.0 and got "router_host_not_found"

"Error 404
Host is not trusted. This could occur because you have not configured a custom domain. Add a custom domain to your project first and try again.

Type

router_host_not_found"

[pastel coyote]

how are you accessing your appwrite instance?

[jolly oyster]

{"message":"Error: Server Error","code":500,"version":"1.4.0"}

I was accessing it via a custom domain domain

[glass patio]

Is this domain is set up in your .env file?

[jolly oyster]

And after migrating I refresh to see what's new but boom na error I ran to, I restarted but it's still there

YES

_APP_DOMAIN = example.com
_APP_DOMAIN_FUNCTIONS=example.com
_APP_DOMAIN_TARGET=appwrite.example.com
And It was working before the upgrade

[wind jolt]

I'm getting exactly the same message 😅:

[jolly oyster]

I replaced my domain name for example.com

[wind jolt]

You will need to put there your domain name

[jolly oyster]

Yes it carries my real domain, I change for the sake of example

[pastel coyote]

would you please run docker compose exec appwrite vars and validate the vars?

router_host_not_found after Upgrading to 1.4.0

[jolly oyster]

I run it but it just list out my .env items out

It shows
The "_APP_CONNECTIONS_MAX" variable is not set. Defaulting to a blank string.
before listing out other items in .env

[glass patio]

Follow the [MariaDB](#1146463435245228174 message) steps here

  mariadb:
    image: mariadb:10.7 # fix issues when upgrading using: mysql_upgrade -u root -p
    container_name: appwrite-mariadb
    <<: *x-logging
    restart: unless-stopped
    networks:
      - appwrite
    volumes:
      - appwrite-mariadb:/var/lib/mysql:rw
    environment:
      - MYSQL_ROOT_PASSWORD=${_APP_DB_ROOT_PASS}
      - MYSQL_DATABASE=${_APP_DB_SCHEMA}
      - MYSQL_USER=${_APP_DB_USER}
      - MYSQL_PASSWORD=${_APP_DB_PASS}
    command: 'mysqld --innodb-flush-method=fsync'

[wind jolt]

Oh, okay

[jolly oyster]

Tried that but still the same

[pastel coyote]

do you have a reverse proxy in front?

[jolly oyster]

Yes from cloudflare

I just disable the proxy but the same

[glass patio]

Cloudflare won't affect that's okay

[pastel coyote]

Nothing else?

[jolly oyster]

Nothing else

[pastel coyote]

This doesn't seem right...usually domain and domain target are the same.

Is the domain your accessing appwrite == that domain env var?

[jolly oyster]

Can I downgrade to previous version then upgrade again

[glass patio]

You have db backup?

[jolly oyster]

It's a new APP, no data yet

[glass patio]

Then you can just reinstall it
And also change the _APP_DOMAIN to match the _APP_DOMAIN_TARGET

[jolly oyster]

I'm acccesing Appwrite via appwrite.mydomain.com

[glass patio]

Then set _APP_DOMAIN to that domain

_APP_DOMAIN is not your outside app but is the Appwrite domain

After changing - if it's a live Appwrite - run

docker compose down && docker compose up -d

And you should be set to go

[jolly oyster]

Wow, it's working now
Thanks alot ✌🏽

[glass patio]

[jolly oyster]

And now it error 500

[glass patio]

For this part check [this](#1146463435245228174 message)

This is just a temporary solution till Appwrite will release the patch