Troubleshoot common Thunder Compute errors. Find solutions for connection issues, function errors, SSH problems, and access logs. Get support via Discord.
To assist troubleshooting, the GCP/AWS instance logs for each instance are saved to the file /var/log/syslog. On your local machine, you can view the CLI logs with cat ~/.thunder/logs. Sharing these with our team can help us quickly find a solution for your problem.
A common error you may encounter is some variant of “This function is not implemented.” What this means is that your program touches a portion of the CUDA API that we do not currently support. Check our prototyping mode guide for supported features, and if you encounter this, please contact us.
If you encounter SSH-related errors (like Error reading SSH protocol banner or permission issues), first retry the command.For quick fixes, back up critical data and recreate the instance. Instances cannot be stopped or restarted.For persistent SSH issues, see our SSH on Thunder Compute guide for alternative connection methods.
If you continue to experience compatibility issues or errors that cannot be resolved through the above methods, consider switching to Production mode. Production mode provides maximum stability and reliability with all low-level optimizations disabled, ensuring complete compatibility for workloads that encounter persistent issues in the prototyping tier.Instances cannot be converted to production mode after creation. Back up your data, create a new production tier instance, and restore your environment there. Production mode has a higher hourly cost but guarantees predictable performance and compatibility.
