Unable to connect to Engine: Ensure that your Engine is publicly accessible
What it means
Your Engine URL cannot be resolved on the public internet.
Common reasons include:
- Engine is running locally on your machine (e.g. http://localhost:3005).
- Engine is running on the cloud but does not have a public load balancer or hostname.
How to fix it
Running Engine locally
Follow the Self-Host instructions to use a self-signed certificate and have Engine accessible from https://localhost:3005. You may need to navigate to https://localhost:3005 and select Proceed to localhost (unsafe) to allow your browser to make requests to this domain.
Alternatively use an SSH tunnel service like ngrok to expose your local server over a public HTTPS hostname.
Running Engine on the cloud
Consult your cloud provider documentation to expose Engine publicly.
Test your Engine setup
Navigate to https://<engine_url> in your browser. Your Engine is publicly accessible if your browser returns a 200 response, { "message": "Engine is set up successfully..." }.
Alternatively, consider using a Cloud-hosted Engine managed by thirdweb.