Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 Bug: Cannot connect to Google Cloud Storage #8534

Open
1 task done
despens opened this issue May 20, 2024 · 3 comments
Open
1 task done

🐛 Bug: Cannot connect to Google Cloud Storage #8534

despens opened this issue May 20, 2024 · 3 comments
Assignees

Comments

@despens
Copy link

despens commented May 20, 2024

Please confirm if bug report does NOT exist already ?

  • I confirm there is no existing issue for this

Steps to reproduce ?

  1. Create Bucket on Google Cloud Storage, such as 'my_bucket'
  2. In the bucket's Permissions tab, create service user with permissions to read and write to this bucket (role 'Legacy Bucket Owner'). The service user's email will be something like <name_you_choose>@<project_id>.iam.gserviceaccount.com
  3. In IAM → Service accounts, export the service user's key. (As JSON and PK12 key file.)
  4. Paste in nocodb UI for Google Cloud Storage:
    • Bucket Name: my_bucket
    • Client Email: <name_you_choose>@<project_id>.iam.gserviceaccount.com
    • Project ID: <project_id>
    • Private Key: either
      • decrypted PK12 key file, or
      • complete JSON keyfile

nocodb will always respond with an error on the UI level:

error:1E08010C:DECODER routines::unsupported

Docker log
nocodb-1  | [Nest] 10  - 05/20/2024, 2:13:51 PM   ERROR [MissingDBError] Error: error:1E08010C:DECODER routines::unsupported
nocodb-1  | [Nest] 10  - 05/20/2024, 2:13:51 PM   ERROR [GlobalExceptionFilter] error:1E08010C:DECODER routines::unsupported
nocodb-1  | Error: error:1E08010C:DECODER routines::unsupported
nocodb-1  |     at Sign.sign (node:internal/crypto/sig:128:29)
nocodb-1  |     at Object.sign (/usr/src/app/node_modules/jwa/index.js:152:45)
nocodb-1  |     at Object.jwsSign [as sign] (/usr/src/app/node_modules/jws/lib/sign-stream.js:32:24)
nocodb-1  |     at GoogleToken._GoogleToken_requestToken (/usr/src/app/node_modules/gtoken/build/src/index.js:235:27)
nocodb-1  |     at GoogleToken._GoogleToken_getTokenAsyncInner (/usr/src/app/node_modules/gtoken/build/src/index.js:180:97)
nocodb-1  |     at GoogleToken._GoogleToken_getTokenAsync (/usr/src/app/node_modules/gtoken/build/src/index.js:160:173)
nocodb-1  |     at GoogleToken.getToken (/usr/src/app/node_modules/gtoken/build/src/index.js:110:102)
nocodb-1  |     at JWT.refreshTokenNoCache (/usr/src/app/node_modules/google-auth-library/build/src/auth/jwtclient.js:173:36)
nocodb-1  |     at JWT.refreshToken (/usr/src/app/node_modules/google-auth-library/build/src/auth/oauth2client.js:166:24)
nocodb-1  |     at JWT.getRequestMetadataAsync (/usr/src/app/node_modules/google-auth-library/build/src/auth/oauth2client.js:312:28)

Desired Behavior

The exported key should be accepted and a connection to the bucket established.

Alternatively, provide detailed instructions on what data is expected in the "Configure Google Cloud Storage" dialog.

Project Details

NocoDB used as docker : true
NocoDB version : 207.1
Database used in NC_DB URL  : pg
Project was created  by clicking : New Project
Database on which spreadsheet is created : pg
OS on which NocoDB is running : Alpine Linux (docker)
Node.js version if running as node : 
Database version : Postgres 15

Attachments

No response

@dstala
Copy link
Member

dstala commented May 28, 2024

@pranavxc see if we can get any clue from the logs pasted here for the issue.

@despens
Copy link
Author

despens commented May 28, 2024

@pranavxc Let me know if you need any other type of log or information, I'm happy to provide.

@despens
Copy link
Author

despens commented Jun 24, 2024

Can confirm this still applies to release 0.250.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🏌️ Open
Development

No branches or pull requests

3 participants