I think you did not change the application type to Desktop. The desktop application does not require configuring a redirect URI. It should accept any localhost redirect URI.

As for the service accounts — you have to log in as a Google user and authorize the app to access your Google Drive. Would this behavior be possible with service accounts? I haven't checked this, but I think that won't be possible.

heya, @hamon-e, I think I'm having the same issue ending at a 127.0.01 refused to connect when trying to set up the account (i did set the application type to Desktop App). Can you tell me where I can access the Authorized redirect URIs to be able to add http://127.0.0.1:8085?

same issue here,, the redirect URIs only possible to setup when use web application type

If you’re trying to configure gdrive on a remote server but are stuck with the 127.0.0.1 redirect during the OAuth process, here’s what you can do:

1. Set up the account on a local machine (gdrive account add):
   Since the OAuth process requires browser access to authorize, complete the account setup on a computer where you have a browser available.
2. Export the account from the local machine (gdrive account export myaccount):
   Once the account is set up locally, export the account credentials to a file. This file will contain all the necessary information for gdrive to access your Google Drive.
3. Transfer the exported file to your remote server:
   Use any file transfer method (like SCP) to copy the exported credentials file to your remote server.
4. Import the account on the remote server (gdrive account import /path/to/destination/myaccount):
   On the remote server, import the credentials file into gdrive. This will make the account accessible on the server without requiring another OAuth setup.
5. Verify everything is working (gdrive files list):
   Test gdrive on the remote server to ensure it can access your Google Drive files and upload or download as needed.