We have a working 3cx system, Ent License, hosted in AWS, v18.0.3.461, which is backing up to a Google Storage bucket and also archiving call recordings to a different directory in the same bucket. I can see the backups and recordings both from that 3cx instance and from google utilities.
I am working on setting up a failover machine BUT what I am running into is I can't get any other 3cx machine (test machines) to access the Google Storage Bucket that our original 3cx is pointed to. I don't have the original google json creds used on this machine but I've issued a 2nd set of credentials for the same google service account and verified it works with google command line tools. When I enter the Google credentials on a new 3cx machine it will display the bucket name but I can't get farther than that. It just clocks on the web ui and eventually gives me a bunch of timeout type popup errors on the 3cx screens.
I've gone so far as to create a 2nd bucket in the same project. WIth the same credentials on a test 3cx instance I can get into the 2nd bucket and list directories to place the backups and recordings in. I've also created a 2nd Service Account and have verified I can access the 2nd bucket but get the same results attempting to access the original bucket from a 3cx machine.
The bucket configs from GCP web console look identical. The Service Accounts are identical. I have verified the bucket and Service Accounts are setup according to the documentation. It has to be something about the original bucket but it looks identical to the new bucket from everything I can find.
I am very close to copying the contents of the original bucket to the new bucket and reconfiguring the original AND a new failover to use the new bucket.
Anyone have any ideas where I might find bucket access errors in the 3cx logs (I haven't found any) for additional troubleshooting? Or any other ideas? before I go copying data to a new bucket.
I am working on setting up a failover machine BUT what I am running into is I can't get any other 3cx machine (test machines) to access the Google Storage Bucket that our original 3cx is pointed to. I don't have the original google json creds used on this machine but I've issued a 2nd set of credentials for the same google service account and verified it works with google command line tools. When I enter the Google credentials on a new 3cx machine it will display the bucket name but I can't get farther than that. It just clocks on the web ui and eventually gives me a bunch of timeout type popup errors on the 3cx screens.
I've gone so far as to create a 2nd bucket in the same project. WIth the same credentials on a test 3cx instance I can get into the 2nd bucket and list directories to place the backups and recordings in. I've also created a 2nd Service Account and have verified I can access the 2nd bucket but get the same results attempting to access the original bucket from a 3cx machine.
The bucket configs from GCP web console look identical. The Service Accounts are identical. I have verified the bucket and Service Accounts are setup according to the documentation. It has to be something about the original bucket but it looks identical to the new bucket from everything I can find.
I am very close to copying the contents of the original bucket to the new bucket and reconfiguring the original AND a new failover to use the new bucket.
Anyone have any ideas where I might find bucket access errors in the 3cx logs (I haven't found any) for additional troubleshooting? Or any other ideas? before I go copying data to a new bucket.
