Hi, I recently purchased my second tinypilot (TinyPilot Voyager 2a). My first tinypilot is TinyPilot Voyager 2.
How exactly do you install Tailscale on my second TinyPilot Voyager 2a?
I tried to follow the installation steps as my first TinyPilot Voyager 2 but it doesnt seem to work...
EDIT: just to add:
I've managed to add my first tinypilot to tailscale, changed its hostname from the Tinypilot interface, call it "TP1".
However, i'm unable to ssh into the second tinypilot. Already tried command "ssh pilot@[ip address]" but got an error in return:
"ssh: connect to host 10.189.184.104 port 22: Connection refused".
Please help with my second tinypilot setup.
- 7 replies
- In reply toFireofCourage⬆:
Hi @FireofCourage, sorry that you were running into this issue.
Thanks for confirming that changing your TinyPilot's hostname solved your first issue.
Please let me know if you have any other issues or questions.
I have not been able to successfully ssh into the second tinypilot.
When i tried to change the hostname from the tinypilot interface: System > hostname, i got the error below:
Failed to Redirect
Cannot reach TinyPilot under the new hostname. The device may have failed to reboot, or your browser is failing to resolve the new hostname.
- In reply todavid⬆:
What happened was I first changed the first tinypilot hostname from the tinypilot interface, let's call it TP1.
When I changed my second tinypilot hostname from the tinypilot interface known as TP2.
But now according to my router's DHCP client table, its showing both of my IP addresses linked to "TP2". I think this is where tinypilot is being confused and is unable to recognize my second tinypilot. I need to know how to assign the right tinypilot hostname to the right tinypilot in the DHCP.
That's an unusual situation.
Just to clarify, you can
sshinto TP1. But you can't access TP2 at all (web interface or
ssh) after the hostname change?
Can you disconnect TP1 from your network and see if you can access TP2 via the web interface or
ssh? Depending on your network setup, you might be able to re-assign the IP address of TP2. Or, when you reconnect TP1 to the network, your router may assign TP1 a different IP address if it clashes with TP2.
Alternatively, since you can access TP1, you could try setting a static IP address to avoid clashing.
- FIn reply toFireofCourage⬆:@FireofCourage
It's cliche to say, but a good old reboot of my PC fixed the issue!
I realized i forgot to enable SSH earlier. After enabling it, maybe cuz i tried to change the hostnames too many times so it got confused.
Anyway, rebooted then got back on track and it's working!
Thanks everyone for your supportReplySolution