Rank 2: Process
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.....
Votes
0
Replies
13
Participants
Unknown
Messages
14
Rank 2: Process
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.....
Rank 2: Process
Rank 2: Process
Rank 2: Process
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
Rank 5: Hypervisor
Is there anything other than OAuth that goes wrong if Appwrite is exposed on non-standard ports, currently?
Rank 5: Hypervisor
Assuming anything that creates a redirect URI, but I don't think there's anything outside of Auth that does that, currently?
Rank 5: Hypervisor
Function V3 endpoints, possibly
ssl cert generation
Rank 5: Hypervisor
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
Rank 2: Process
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