Common Errors
Commonly encountered errors when using a tunnel in your HTTP Request or Send Email Action and how to troubleshoot.
TUNNEL_CONNECTION_ERROR
We were unable to establish a tunnelled connection for tunnelName
This may be an issue with either the endpoint being called from the action request or the tunnel being down.
Please check the following:
Your tines-tunnel container is active.
The tunnel is properly configured and healthy.
The action request endpoint used is a valid hostname / url.
You can see the health status of your tines tunnel by visiting /admin/tunnel and viewing the tunnel status.
TUNNEL_OPEN_TIMEOUT_ERROR
We encountered a timeout while opening the tunnel connection for tunnelName.
This may be an issue with either the endpoint being called from the action request or the tunnel being down.
Please check the following:
Your tines-tunnel container is active.
The tunnel is properly configured and healthy.
The action request endpoint is a valid hostname / url.
You can see the health status of your tines tunnel by visiting /admin/tunnel and viewing the tunnel status.
If the tunnel is configured correctly, the server may not be responding promptly.
To troubleshoot further:
Copy your Tines Action as a curl command and run it in your container (on your server).
If it works, it's likely a timeout issue. Increase the timeout on your HTTP Request Action to at least 60 seconds.
SSL_ERROR
An SSL connection error was returned for the request.
SSL certificate verification failed. This may be caused by an outdated SSL certificate, incorrect URL, network issues, or misconfigurations.
To resolve, check the following:
Renew or Update SSL Certificate: Ensure it's current.
Check URL and Parameters of action request are correct.
Network Configuration: Inspect for issues.
Disable SSL verification temporarily: Consider setting 'disable_ssl_verification' to true, in the action options.
Health statuses
Commonly encountered healt statuses for Tunnel and any remediations
Healthy
The tunnel is active and serving traffic through four connections to the Cloudflare global network.
Degraded
One or more tunnel containers are active and serving traffic, but at least one individual connection has failed. Further degradation in tunnel availability could risk the tunnel going down and failing to serve traffic.
We recommend restarting the tunnel container to resolve the issue. If the status continues to be in a degraded state after restart, please reach out to support with the debug logs. You can find the instructions on how to turn on debug logs for your tunnel container by visiting /admin/tunnel in your Tines tenant.
Inactive
This usually happens when tunnels have been created, but have never been run. It should clear away after your first run.
Down
One or more tunnel containers cannot serve traffic as it has no connections to the Cloudflare global network. Please ensure that the tunnel container is up and running.