All Errors

Terraform detected a circular dependency in your infrastructure configuration where resources depend on each other directly or through a chain, preventing Terraform from determining creation order. Break the cycle by refactoring resource relationships or using intermediate resources.

The "Value for undeclared variable" warning occurs when you provide a value for a variable that has not been declared in your Terraform configuration. Fix it by adding a variable block to declare the variable or removing the unused value assignment.

This error occurs when Terraform cannot acquire a lock on your state file, typically due to a previous incomplete operation or concurrent access. It happens most often with S3 backends using DynamoDB for state locking.

The "Timeout while waiting for state" error occurs when Terraform cannot detect that a resource has reached its desired state within the configured timeout period. This typically indicates either a slow-running operation, resource constraints in your cloud provider, or network connectivity issues.

The duplicate resource error occurs when Terraform detects two or more resources with the same resource address in your configuration. This typically happens when resource blocks are defined twice in the same module or when using meta-arguments like count or for_each incorrectly.

Terraform failed to download a plugin or binary during initialization. This typically happens due to network connectivity issues, registry problems, or misconfigured version constraints.

The "read-only file system" error occurs when Terraform cannot write to directories needed for state files, plugins, or temporary operations. This typically happens in containerized or restricted environments. Fix by ensuring writable directories are available and properly mounted.

The x509 certificate error occurs when Terraform cannot verify the SSL/TLS certificate of a server. This typically happens with self-signed certificates, custom CAs, or corporate proxies. Resolve by adding the certificate to your system's trust store or configuring Terraform to recognize the CA.

InvalidClientTokenId occurs when Terraform cannot authenticate with AWS because the provided security credentials are invalid, expired, or misconfigured. This typically happens due to incorrect access keys, special characters in secrets, or expired temporary credentials.

The "failed detecting s3 prefix" error occurs when Terraform Enterprise cannot list objects in an S3 bucket during state detection. This typically indicates missing IAM permissions, incorrect credentials, or network connectivity issues with your S3 backend.

Terraform timed out waiting for a resource to reach its desired state during creation. This typically happens when cloud API operations take longer than expected, network connectivity is interrupted, or resource dependencies aren't properly configured.

This error occurs when Terraform cannot locate the S3 bucket specified for the remote backend. The bucket must be created before Terraform can store state files in it.

This error occurs when Terraform times out waiting for a resource (especially AWS routes) to reach its desired state. The operation exceeds the timeout threshold, often due to misconfigured timeouts, network issues, or provider bugs.

The Module not installed error occurs when Terraform cannot find or load a referenced module. This happens when you reference a module in your configuration but haven't run terraform init or the module source is invalid.

The "Unsupported block type" error occurs when your Terraform configuration uses a block that is not recognized or expected in that context. This typically happens due to provider version incompatibility, incorrect block syntax, or outdated HCL syntax.

This error occurs when apt cannot verify GPG signatures for package repositories because a required GPG key is missing, expired, or outdated. It prevents package updates and installations.

The "E: Unmet dependencies. Try using -f" error occurs when apt package dependencies are broken. The -f flag (or --fix-broken) tells apt to automatically install missing dependencies and resolve conflicts to repair your package system.

The /etc/apt/preferences.d directory is missing from your system, causing APT to warn it cannot read pinning preferences. Recreating this directory resolves the warning.

This PostgreSQL error occurs when you try to create a unique constraint or primary key on a partitioned table without including all partition key columns. PostgreSQL enforces uniqueness only within each partition, so the constraint must include the partition key columns to ensure proper behavior. The fix requires adding all partition key columns to your constraint definition.

This error indicates your Firebase Cloud Function threw an unhandled exception. It happens when your code crashes without proper error handling, preventing the function from returning a valid response to the client.