Immutable solution version
Provider crash invalid memory address
Complete solution
A practical guide for Fastly CDN. A provider crash with 'invalid memory address' (nil pointer) on fastly_tls_subscription traced back to a Fastly API-side incident (remote error: tls: no application protocol from api.fastly.com), not your config. The API issue was resolved by Fastly.
The problem
Issue fastly/terraform-provider-fastly#838 (closed, 10 comments): ### Terraform Version Terraform v1.8.1 But also happening in terraform 1.7.4 ### Affected Fastly Terraform Resource(s) It seems to be fastly_tls_subscription but I use several resources (compute and service_vcl) `` Get "https://api.fastly.com/service/[redacted]/details": remote error: tls: no application protocol ### Terraform Configuration Files ``hcl # Copy-paste your Terraform configuration here.
The fix
A provider crash with 'invalid memory address' (nil pointer) on fastlytlssubscription traced back to a Fastly API-side incident (remote error: tls: no application protocol from api.fastly.com), not your config. The API issue was resolved by Fastly. If you hit this shape of crash, check Fastly status and support rather than rewriting your Terraform, since it wasn't a provider bug.
Notes
Thread: https://github.com/fastly/terraform-provider-fastly/issues/838. Verified against the closed issue and the maintainer/accepted answer there.
Evidence
In https://github.com/fastly/terraform-provider-fastly/issues/838, the reporter asked: Issue fastly/terraform-provider-fastly#838 (closed, 10 comments): ### Terraform Version Terraform v1.8.1 But also happening in terraform 1.7.4 ### Affected Fastly Terraform Resource(s) It seems to be fastly_tls_subscription but I use several resources (compute and servicevcl) `` Get "https://api.fastly.com/service/[redacted]/details": remote error: tls: no application protocol ### Terraform Configuration Files ``hcl # Copy-paste your Terraform configuration here. The verified answer: A provider crash with 'invalid memory address' (nil pointer) on fastlytls_subscription traced back to a Fastly API-side incident (remote error: tls: no application protocol from api.fastly.com), not your config. The API issue was resolved by Fastly. If you hit this shape of crash, check Fastly status and support rather than rewriting your Terraform, since it wasn't a provider bug. Source thread: https://github.com/fastly/terraform-provider-fastly/issues/838
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_xUD0v99VVMuhlID1vLxfLw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Provider crash invalid memory address <span>— Vectle</span></a>