TinyPilot is Not Running

You have connected successfully to your TinyPilot device, but the TinyPilot web application doesn't seem to be running.

This error can occur if you tried to access the TinyPilot page too quickly after starting your TinyPilot device.

Please reload the page.

If you continue to see this message, please try the following troubleshooting steps:

Solution 1: Restart the TinyPilot service

If you previously enabled SSH on your TinyPilot, you can check whether the TinyPilot service is running by logging in via SSH and running the following command:

sudo service tinypilot status

If the service is not listed as Active: active (running), restart the TinyPilot service with the following command:

sudo service tinypilot restart

After the command completes, reload this page.

Solution 2: Restart your TinyPilot

If you previously enabled SSH on your TinyPilot, log in via SSH and try restarting your TinyPilot by running the following command:

sudo reboot

If you don't have SSH access, wait two minutes before powering off your TinyPilot. Then, power on your TinyPilot, and wait a minute before reloading this page.

Solution 3: Reset your TinyPilot to factory settings

If you have just updated your TinyPilot, or if your TinyPilot recently experienced sudden power loss, your TinyPilot may have a corrupted filesystem.

A factory reset will restore your TinyPilot back to a working state.

Still having issues?

If the above options have failed, contact TinyPilot's support team with the following information:

• Model of your TinyPilot
• What you were doing before receiving this 502 error (e.g., updating your TinyPilot software)?
• A log URL from your TinyPilot (if you have SSH access)
  • SSH into your TinyPilot and run sudo /opt/tinypilot-privileged/collect-debug-logs