[AUTO SOLVED]After upgrading to v1.4.5 from v1.4.4 self host, the console is not working
- 0
- Self Hosted
- Web
I upgraded to v1.4.5 and after that I am getting weird errors in console. The routes do not work and many operations throw Network Request Failed errors.
https://backend.atomtalkpvtltd.com/v1/proxy/rules/65224b164eab7951e5a7 => throws network request failed
and the console is still on v1.4.4
I did all the steps for upgrade and restarted the server many times.
I did all the steps for upgrade and restarted the server many times.
- What did you do exactly?
- What's in your appwrite folder now?
- Would you please do a hard refresh to clear your cache?
- followed instructions on https://appwrite.io/docs/advanced/self-hosting/update
- backups, docker-compose.yml .env
- opened in incognito mode and the console loads properly
now the main domain's certificate is invalid and I am getting all kinds of errors for https as the letsencrypt ssl has expired. I thought the ssl was auto renewed.
ok so just used the command docker compose logs appwrite-worker-certificates for the main domain ssl. let'ss see when it is updated.
the certificate is valid now for main subdomain.
[AUTO SOLVED]After upgrading to v1.4.5 from v1.4.4 self host, the console is not working
by the way the console still shows 1.4.4 @Steven
you probably have a cache problem
Recommended threads
- Authentication on custom Websocket Serve...
Hi, I want to use a custom Websocket Server (using Bun) for my application. However I cant really figure out authentication on custom servers. Session cookies ...
- Realtime: Listener not triggered on upda...
I self host appwrite 1.8.1. The genereal functionallity works fine. But my realtime subscription isn't updating. I see "Received heartbeat response from realtim...
- Realtime for files() works almost well, ...
I have been trying to make use of realtime, today (14.03.26) I have pulled all the latest versions of docker images, and sdk available. Whats working: - Conn...