Project runs locally, but not on Teenode?
First, check your build logs using the CLI: teenode deployment logs [deployment-id]. Common issues include missing environment variables, incorrect build commands, or incompatible dependencies.
Use the attestation API endpoint provided with your instance. See our attestation verification guide for detailed instructions.
Yes! For Micro VM and Pro VM plans, you have full root access via SSH. Add your SSH key through the dashboard or CLI, then connect using the provided credentials.
Use the CLI command: teenode env set KEY=value. Changes take effect on the next deployment. You can also manage environment variables through the dashboard.