Appwrite server local install, v1.4.1
Seems Appwrite is passing the wrong redirect to Google for OAuth? Server is hosted on port 81, but port seems to be this is missing when passed to Google.....
Note url on google error dialog is missing port 81
a quick fix is setup a local domain and use port 80
as of today, Appwrite must be exposed/accessed on standard ports for everything to work correctly.
FYI, this is the related issue: https://github.com/appwrite/appwrite/issues/2365
Is there anything other than OAuth that goes wrong if Appwrite is exposed on non-standard ports, currently?
Assuming anything that creates a redirect URI, but I don't think there's anything outside of Auth that does that, currently?
Function V3 endpoints, possibly
ssl cert generation
Is cert generation using standard ACME? Becuase I don't think there's any way to have ACME use a non standard port
yes standard acme
ACME supports non-standard ports via DNS challenges. Unfortunately if Appwrite is using Traefic proxy then I believe that uses HTTP challenges, which are limited to ports 80/443 as you say.
yes, we are using http challenge
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...