Tiny Pilot performance and certificate issue
- @david
Some browsers work fine with https://tinypilot/ and others refuse to connect unless I add .local to the end (https://tinypilot.local/)
The problem is if I connect with tinypilot.local, I get this connection is not secure. How can I correct it so the device accepts connections from either tinypilot.local or tinypilot
If I use https://app.remote.it/#/ it always tries to use MPEG instead of H.264 and there is a considerable delay (12 to 20 second). Is there anything that can be done to improve performance using remote.it?
David @david2023-12-18 12:35:42.041ZHi @gettingstarted.app, I'm sorry you're running into these issues.
if I connect with tinypilot.local, I get this connection is not secure.
This warning usually appears when TinyPilot secures the HTTPS connection using a key that your client machine doesn't know about yet. Can you follow our FAQ guide to fix these browser privacy warnings?
How can I correct it so the device accepts connections from either tinypilot.local or tinypilot
This seems to depend on a few different factors, like your browser and network configuration. I tend to use https://tinypilot.local since most setups seem to support that format. If https://tinypilot.local works across your devices, I'd recommend using that instead of without the .local suffix.
Is there anything that can be done to improve performance using remote.it?
We've typically found that remote.it is a bit slower than alternative cloud access tools. I personally recommend Tailscale. However, one way to improve performance with remote.it is to reduce bandwidth by adjusting your TinyPilot's video settings.
Since your TinyPilot seems to fall back to MJPEG streaming mode instead of using the more efficient H.264, could you try specifying a STUN server? Specifying a STUN server requires TinyPilot Pro 2.6.2. Using H.264 streaming mode should help improve performance here too.
I hope that helps! Please let me know if you have any other questions.