Using remote.it to access tinypilot allows me to see the screen, but the keyboard does not work and at the bottom it says disconnected
Using remote.it to access tinypilot allows me to see the screen, but the keyboard does not work and at the bottom it says disconnected. Has this been encountered before? Just some more info, I have the Pro version and made the DIY version. The Pro version works perfectly, the DIY version does not have https enabled. If I upgrade my DIY version to a paid version, will that fix the issue? Also, once my Pro 1-year support runs out will it still work with Remote.it? Thanks in advance for the info.
- 3 replies
If you see the 'disconnected' message on TinyPilot web interface, that suggests that the image of the screen you can see is a still image from before your TinyPilot disconnected. You can confirm this by checking if the time updates on the target machine once disconnected.
Did you run through our tutorial for setting up remote.it on your DIY TinyPilot?
I believe you need to select the service type (HTTPS or HTTP) in remote.it when you're setting it up. For a DIY TinyPilot, you'll need to make sure you're using HTTP service, rather than HTTPS. If you require HTTPS on your DIY TinyPilot, you will need to purchase a TinyPilot Pro license.
Also, once my Pro 1-year support runs out will it still work with Remote.it?
When you purchase TinyPilot Pro software, it's your to keep and retains TinyPilot Pro features even once the license expires. However, if your license expires, you stop receiving future updates.
Okay, I got it working. After reading the link you sent me I still had a problem but I solved it. So the DYI version does not have a certificate in place by default. This means when you launch the remote.it session you will see the screen updating (run the linux command, top) but the keyboard will not work. Go to the URL and if it starts with https, change it to http. This is not secure, but still has a use case if you are building machines all the time.