Skip to main content
Version: 4.6.1-saas

Troubleshooting

This document provides common issues and solutions that may occur when using NetFUNNEL Fastly Agent.

Installation and Initialization​

Fastly CLI Installation Failure​

Symptoms: Fastly CLI installation fails or command cannot be found.

Solutions:

  • Verify that Homebrew is installed
  • Run brew install fastly/tap/fastly command again
  • Restart terminal and try again

Compute Service Creation Failure​

Symptoms: Compute Service creation fails.

Solutions:

  • Verify that Compute Services support is enabled in Fastly account
  • Verify that Service name is valid
  • Verify that domain is entered correctly

CNAME Registration Failure​

Symptoms: CNAME registration fails or TLS certificate is not issued.

Solutions:

  • Verify that CNAME record is correctly set in DNS provider
  • Verify that CNAME value matches the value provided by Fastly
  • Wait sufficient time considering DNS propagation time

Operation Issues​

Queue Not Applied​

Symptoms: Trigger rules are set but the queue is not applied.

Solutions:

  • Verify that segment trigger rules are correctly set in the NetFUNNEL console
  • Verify that URLs match the trigger rules
  • Verify that CLIENT_ID setting in Config Store is correct
  • Verify that agent is correctly deployed to Compute Service
  • Perform Compute Purge to apply changes

Not Redirecting to Waiting Room​

Symptoms: Waiting response is received but not redirected to waiting room.

Solutions:

  • Check VWR_PAGE_DOMAIN setting in Config Store
  • Check host settings in Compute Service
  • Check Compute Purge status

Deployment Issues​

Agent Deployment Failure​

Symptoms: fastly compute deploy command fails.

Solutions:

  • Verify that Fastly API token is correctly set
  • Verify that service_id in fastly.toml file is correct
  • Verify that Fastly CLI is up to date
  • Check network connection status

toml File Error​

Symptoms: toml file is modified but deployment fails.

Solutions:

  • Verify that toml file syntax is correct
  • Verify that service_id and cloned_from values match
  • Verify that all required fields are entered

Configuration Issues​

Config Store Values Not Applied​

Symptoms: Config Store is set but values are not reflected.

Solutions:

  • Verify that Config Store is correctly linked to Compute Service
  • Verify that Key and Value are entered correctly
  • Verify that Compute Purge was performed
  • Wait sufficient time (a few minutes) after Compute Purge is complete

Compute Purge Not Complete​

Symptoms: Compute Purge takes too long or does not complete.

Solutions:

  • Check Purge status and wait until it completes
  • Retry if Purge failed
  • Check Fastly service status