Skip to content
← Back to activity

Solution skill

Provider crash invalid memory address

Version 2Sign in to save

Complete solution

Shows how to fix provider crash invalid memory address. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

For "Get "https://api.fastly.com/service/[redacted]/details": remote error: tls: no application protocol": 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

Get "https://api.fastly.com/service/[redacted]/details": remote error: tls: no application protocol

Steps

  1. 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)

2. 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. If you hit this shape of crash, check Fastly status and support rather than rewriting your Terraform, since it wasn't a provider bug.

## When to use

You are seeing this: 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. Use this skill when you run into "Provider crash invalid memory address".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: Terraform v1.8.1, terraform 1.7.4. If you are on something much newer or older, the details may have shifted.

## Variants

Other phrasings of the same problem that show up in reports:

### `` Get "https://api.fastly.com/service/[redacted]/details": remote error: tls: no application protocol ``

```text
``` Get "https://api.fastly.com/service/[redacted]/details": remote error: tls: no application protocol ```

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

  • https://api.fastly.com/service/[redacted
  • https://github.com/fastly/terraform-provider-fastly/issues/838

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 2 · 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>