jogriOriginal post
Rank 1: Thread
I run appwrite on my server behind nginx and only use it via local connections. Since I regularly ran into problems on updates where the local address was not accessable anymore or couldnt update appwrite in the first place, I setup a public domain for the console that I would put behind basic auth access restriction - since in my case I dont want the client to access appwrite directly at all. I'm not happy with this solution and the last update broke local connections again. I see why this doesnt make sense for appwrite cloud, but I guess for many self-hosted usecases this extra layer of restriction makes sense. So I was wondering if someone found a stable setup that works.
Summary
The user is hosting Appwrite on a server behind Nginx and wants to use it solely via a local network. They've encountered issues with local access after updates, prompting them to set up a public domain for the Appwrite console with basic auth restrictions. However, this solution is unsatisfactory and has broken local connections again after a recent update. They seek a more stable setup for self-hosting Appwrite that maintains local access without the need for a public domain.
A stable solution suggested in the thread involves configuring Nginx to correctly proxy requests to Appwrite while ensuring local network access remains intact during updates. Users also recommend regularly checking