Skip to content

GCS errors

Note: The command prompts were omitted. These log excerpts appear during operations such as connect move, connect copy, or connect list when working with GCS endpoints.

Terminal window
2024/12/20 14:34:41 INFO License valid to: 2026-04-13 18:06:28
2024/12/20 14:34:41 INFO Licensed for: Ultimate
2024/12/20 14:34:41 INFO Testing connection to gs://mybucket
2024/12/20 14:34:41 ERROR Error while testing connection: dial tcp storage.googleapis.com:443: i/o timeout

GCS client was unable to establish a TCP connection to the Google Cloud Storage endpoint within the allowed timeout period.

Possible causes:

  • GCS endpoint is down or unreachable
  • network issues (different subnets, no route, or disconnected network)
  • a firewall (on the client, target, or intermediate network) is blocking connections
  • timeout is too short
  • DNS resolution issues preventing connection to GCS endpoint
Terminal window
2024/12/31 09:15:26 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 09:15:26 INFO Licensed for: Ultimate
2024/12/31 09:15:26 INFO Testing connection to gs://mybucket
2024/12/31 09:15:26 ERROR Error while testing connection: dial tcp storage.googleapis.com:443: connect: connection refused

GCS client was unable to establish a TCP connection to the GCS endpoint as the connection was actively refused by the target machine.

Possible causes:

  • GCS endpoint is not running or is misconfigured
  • firewall is blocking the target port (typically 443 for HTTPS)
  • proxy configuration issues
  • network restrictions preventing access to Google Cloud services
Terminal window
2024/12/31 08:54:52 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 08:54:52 INFO Licensed for: Ultimate
2024/12/31 08:54:52 INFO Testing connection to gs:///path/to/key.json@mybucket
2024/12/31 08:54:52 ERROR GCS service account key file not found: /path/to/key.json

GCS client is trying to use a service account key file for authentication, but the file does not exist.

Possible causes:

  • service account key file does not exist at the specified path
  • path to the key file is incorrect
  • key file was moved or deleted

Failed to get GCS client - invalid credentials

Section titled “Failed to get GCS client - invalid credentials”
Terminal window
2024/12/31 10:42:16 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 10:42:16 INFO Licensed for: Ultimate
2024/12/31 10:42:16 INFO Testing connection to gs://mybucket
2024/12/31 10:42:18 ERROR failed to get GCS client: googleapi: Error 401: Invalid Credentials

GCS client attempted to connect to Google Cloud Storage but was unable to authenticate successfully with the provided credentials.

Possible causes:

  • service account key file is invalid or malformed
  • service account key has expired or been revoked
  • service account does not have sufficient permissions for the requested operation
  • credentials are being used with the wrong project or bucket
  • JSON key file is corrupted or has invalid format

Failed to get GCS client - Application Default Credentials not configured

Section titled “Failed to get GCS client - Application Default Credentials not configured”
Terminal window
2024/12/31 10:42:16 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 10:42:16 INFO Licensed for: Ultimate
2024/12/31 10:42:16 INFO Testing connection to gs://mybucket
2024/12/31 10:42:18 ERROR failed to get GCS client: googleapi: Error 401: Default credentials not available

GCS client attempted to use Application Default Credentials (ADC) but no valid credentials were found.

Possible causes:

  • GOOGLE_APPLICATION_CREDENTIALS environment variable is not set
  • not running in a Google Cloud environment (Compute Engine, GKE, Cloud Run)
  • gcloud auth application-default login has not been run
  • ADC is not configured for the current environment
Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Licensed for: Ultimate
2024/12/31 13:15:57 INFO Testing connection to gs://mybucket
2024/12/31 13:15:58 ERROR Bucket does not exist

GCS client attempted to access a bucket that does not exist in the specified Google Cloud project.

Possible causes:

  • bucket name is misspelled or incorrect
  • bucket exists in a different Google Cloud project
  • bucket was deleted or renamed
  • incorrect project ID or credentials are for the wrong project
Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Licensed for: Ultimate
2024/12/31 13:15:57 INFO Testing connection to gs://mybucket
2024/12/31 13:15:58 ERROR permission denied for bucket

GCS client attempted to access a bucket but does not have sufficient permissions.

Possible causes:

  • service account does not have storage.objects.get permission for the bucket
  • IAM policy does not grant access to the service account
  • bucket exists in a different Google Cloud project
  • service account is disabled or has insufficient IAM roles
Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Testing connection to gs://
2024/12/31 13:15:58 ERROR GCS bucket name cannot be empty

GCS client encountered a connection string with an empty bucket name.

Possible causes:

  • bucket name is missing in the connection string
  • connection string format is incorrect

Correct format: gs://bucket/path or gs:///path/to/key.json@bucket/path

Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Getting files from gs://mybucket/path/
2024/12/31 13:15:58 ERROR not found: No such object: path/file.txt

GCS client attempted to access an object that does not exist in the specified bucket.

Possible causes:

  • object key (file path) is incorrect or does not exist
  • object was deleted or moved
  • object path has incorrect case (GCS keys are case-sensitive)
  • prefix/path separator issues (e.g., missing or extra /)
Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Getting file from gs://mybucket/file.txt
2024/12/31 13:15:58 ERROR failed to get source file info: googleapi: Error 404: Not Found

GCS client attempted to get metadata for an object that does not exist.

Possible causes:

  • object does not exist in the bucket
  • object key is incorrect
  • object was recently deleted
Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Copying gs://src-bucket/file.txt gs://dst-bucket/file.txt
2024/12/31 13:15:58 ERROR GCS does not support concurrent copy

GCS client attempted a concurrent copy operation which is not supported by GCS.

Possible causes:

  • attempting to copy between two GCS endpoints using concurrent mode
  • GCS does not support random access writes required for concurrent copying

Solution: The tool will automatically fall back to sequential copying for GCS-to-GCS transfers.

Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Getting files from gs://mybucket/file.txt
2024/12/31 13:15:58 ERROR failed to create destination folder: no such file or directory

GCS client attempted to download a file but the local destination directory does not exist.

Possible causes:

  • local destination directory does not exist
  • path to destination directory does not exist
  • insufficient permissions to create the directory
Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Sending files to gs://mybucket/
2024/12/31 13:15:58 ERROR failed to open source file: no such file or directory

GCS client attempted to upload a file but the local source file does not exist.

Possible causes:

  • local source file does not exist
  • file path is incorrect
  • insufficient permissions to read the file
Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Listing gs://mybucket/
2024/12/31 13:15:58 ERROR failed to iterate GCS objects: googleapi: Error 403: Insufficient Permission

GCS client encountered an error while iterating through objects in a bucket.

Possible causes:

  • service account does not have storage.objects.list permission
  • IAM policy does not grant list access to the service account
  • bucket ACLs or IAM bindings are misconfigured
Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Listing gs://mybucket/
2024/12/31 13:15:58 ERROR unable to parse source string

GCS client encountered an invalid source string that could not be parsed.

Possible causes:

  • source string format is incorrect
  • invalid pattern or regex syntax
  • malformed connection string
Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Listing gs://mybucket/
2024/12/31 13:15:58 ERROR Error while matching file regex: error parsing regexp

GCS client encountered an error while trying to match files using a regular expression.

Possible causes:

  • regex pattern is invalid or malformed
  • regex syntax is not supported (RE2 regex is required)
  • special characters in regex are not properly escaped
Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Listing gs://mybucket/
2024/12/31 13:15:58 ERROR Error listing gcs files: googleapi: Error 403: Access Denied

GCS client encountered an error while trying to list files in a bucket.

Possible causes:

  • service account does not have storage.objects.list permission
  • bucket does not exist
  • insufficient IAM permissions for the bucket
  • network connectivity issues
Terminal window
2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 13:15:57 INFO Testing connection to gs://mybucket
2024/12/31 13:15:58 ERROR Error while testing connection: googleapi: Error 403: Forbidden

GCS client encountered an error while testing the connection to the bucket.

Possible causes:

  • service account does not have storage.buckets.get permission
  • bucket does not exist
  • insufficient IAM permissions
  • network connectivity issues
  • incorrect project ID or credentials
Terminal window
2024/12/31 08:54:52 INFO License valid to: 2026-04-13 18:06:28
2024/12/31 08:54:52 INFO Licensed for: Ultimate
2024/12/31 08:54:52 ERROR GCS bucket name cannot be empty

GCS client encountered a connection string with an empty bucket name.

Possible causes:

  • bucket name is missing in the connection string
  • connection string format is incorrect

Correct format: gs://bucket/path or gs:///path/to/key.json@bucket/path