Issue Connecting 3CX to Google Cloud Storage – OAuth Errors (400 & 409)

[Paul-2024]

Hi everyone,

I’m having trouble connecting 3CX Backup to Google Cloud Storage. I’ve already created a GCS bucket, set up the permissions, and exported the Private Key (JSON) to be used in 3CX. However, when I try to select a folder from within 3CX, I consistently get this error message:

“Unable to access the directory. Check connection, configuration, credentials, private key, or directory path.”

Everything appears correctly configured on the Google side (Service Account has Storage Admin and Storage Object Admin roles), but 3CX doesn’t seem to establish the connection.

Then I attempted to use the Google Integration feature instead but it resulted in OAuth errors.
I’m getting the following Google errors (see attached screenshots):

• Error 400: access_not_configured
• Error 409: malformed request

Both seem to happen during the OAuth authentication flow.

 

[midwest1]

I'm having same issue but weirdly is with only one of my servers. I connect more than 80 servers using same API - JSON; I know isn't network. I even reinstalled 3cx server from scratch (restore backup after purge and reinstall 3CX problem still there

 

[midwest1]

Hi everyone,

I’m having trouble connecting 3CX Backup to Google Cloud Storage. I’ve already created a GCS bucket, set up the permissions, and exported the Private Key (JSON) to be used in 3CX. However, when I try to select a folder from within 3CX, I consistently get this error message:



Everything appears correctly configured on the Google side (Service Account has Storage Admin and Storage Object Admin roles), but 3CX doesn’t seem to establish the connection.

Then I attempted to use the Google Integration feature instead but it resulted in OAuth errors.
I’m getting the following Google errors (see attached screenshots):

• Error 400: access_not_configured
• Error 409: malformed request

Both seem to happen during the OAuth authentication flow.

Hi Paul,

Did you fix your problem?

 

[midwest1]

Paul,
My issue just got resolved after fix ntp. Server wasn't syncyng - 15 min offset -
sudo apt update && sudo apt install ntp -y