🐛 Bug Report: OAuth2 does not add port number to redirect uri

[dro-1]

👟 Reproduction steps

When I started my appwrite server, I set it to run on port 3000 for http and left all other values as their defaults.
I added Google OAuth by following all the required steps:

• I created the Client ID and set its redirect URI as http:https://localhost:3000/v1/account/sessions/oauth2/callback/google/[PROJECT_ID]
• I also added the App ID and App Secret to Appwrite
• I was building a React App and it's endpoint was 'http:https://localhost:3001/' as it was running on port 3001
• The react app had the appwrite sdk installed so I called the function for creating a new Oauth Session passing 'google' as the provider and the success and failure links

👍 Expected behavior

I expected the redirect URI to have port 3000

👎 Actual Behavior

I get an error saying:

and I noticed that the redirect_uri didn't have the port 3000 on it.

One of the maintainers helped track down the issue to line 292 in this file

🎲 Appwrite version

Different version (specify in environment)

💻 Operating system

Windows

🧱 Your Environment

I'm using version 0.11.0

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[dro-1]

Hello, Can I be assigned to this issue?

[eldadfux]

I have assigned you to this issue, let me know if you need any help.

[dro-1]

I already opened a PR on it but couldn't write the proper tests as I'm a PHP noob.
Check the PR #2368

[skyface753]

Hello, I have the same problem. Is there any solution?

[stnguyen90]

@skyface753, for now, I recommend exposing Appwrite on the standard ports. If you need other apps on the same server on standard ports, you can out a reverse proxy in front.

[stnguyen90]

@skyface753, for now, I recommend exposing Appwrite on the standard ports. If you need other apps on the same server on standard ports, you can out a reverse proxy in front.

[kilroyjones]

@stnguyen90 When you say exposing appwrite on the standard ports, I'm assuming that means 80/443, which won't work if you're developing locally, no? I see there was some progress made in the PR 2368.

[stnguyen90]

@kilroyjones, what's wrong with running Appwrite on 80/443 locally?

[eq-devs]

Hello, I have the same problem. Is there any solution?

[KaranJagtiani]

Is this issue up for grabs? If yes, I would like to work on this @stnguyen90

[stnguyen90]

@KaranJagtiani, as part of working on this, can you test how this behaves if there's a reverse proxy in front of appwrite?

Many people have configured Appwrite to run on non-standard ports like 8080 and 4443, but expose Appwrite nonstandard ports through a reverse proxy. It's crucial for the redirect to still use the ports from the original request that the reverse proxy receives.

[krishnaa192]

Can I work on this issue?

[ahmadrayz007]

Try to change the appwrite port to the standard one, i think it's 80:80 CMIIW
Because google says it's in localhost/v1, not in localhost:3000/v1
I think there is a mismatch between appwrite redirect url and google if we change the port.

[stnguyen90]

@krishnaa192, are you still interested in working on this?