Skip to main content
Version: 4.6.1-saas

Troubleshooting

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

Installation and Initialization​

Lambda Function Deployment Failure​

Symptoms: Lambda function version creation or deployment fails.

Solutions:

  • Verify that the package.json file format is correct
  • Verify that there are no syntax errors in the Lambda function code
  • Verify that IAM role permissions are correctly set
  • Verify that the Lambda function is created in the us-east-1 region

IAM Role Configuration Error​

Symptoms: IAM role error occurs when creating Lambda function.

Solutions:

  • Verify that Trust Entity includes edgelambda.amazonaws.com and lambda.amazonaws.com
  • Verify that IAM policy is correctly attached
  • Verify that CloudWatch log permissions are included

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 clientID setting in Lambda function is correct
  • Verify that Lambda@Edge is correctly connected to CloudFront Distribution
  • Verify that CloudFront invalidation is complete

Not Redirecting to Waiting Room​

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

Solutions:

  • Check vwrPageDomain setting in Lambda function
  • Check Lambda@Edge connection in CloudFront Distribution
  • Check CloudFront invalidation status

Network Issues​

Lambda@Edge Execution Failure​

Symptoms: Lambda@Edge does not run or errors occur.

Solutions:

  • Verify that there are no errors in the Lambda function code
  • Verify that the Lambda function is created in us-east-1 region
  • Check IAM role and policy settings
  • Check error messages in CloudWatch logs

Configuration Issues​

Lambda Config Values Not Applied​

Symptoms: Lambda config is set but values are not reflected.

Solutions:

  • Verify that [Deploy] button was clicked in Lambda function
  • Verify that [Publish new version] was clicked in [Versions] tab
  • Verify that Lambda function version was updated in CloudFront Distribution
  • Verify that CloudFront invalidation was performed
  • Wait sufficient time (a few minutes) after CloudFront invalidation is complete

CloudFront Invalidation Not Complete​

Symptoms: CloudFront invalidation takes too long or does not complete.

Solutions:

  • Check invalidation status and wait until it completes
  • Retry if invalidation failed
  • Check CloudFront service status