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
- Custom emails
What happen if I use a third party email provider to customize my emails and my plan run out of emails/month? Appwrite emails are used as fallback sending emai...
- Realtime with multiple connections
I need the Realtime on multiple Collections for diffrent applicational logic. So my question is: Is there a way to have only 1 Websocket connection or do I need...
- Can't login or deploy functions in Appwr...
Hello, since i updatet to the appwrite cli 6.1.0 i can't login or deploy functions with the cli. When i call the command: "appwrite get account --verbose" i ge...