Hello all,
I recently upgraded my pioreactor network to access them remotely using Tailscale. I managed to have my network up and running yet I do not receive any information from my pio’s when I am remotely. I can still control them somehow via the UI. I only get the information back when I am connected on the local network.
Any suggestions is greatly appreciated!
Best,
Arthur
Hi @ArthurV,
It sounds like the MQTT connection is failing. When you’re on the Pioreactors page, do you see the green dot next to their name, or do you see the status of any activities after you start them? I’m guessing no.
In your configuration, did you change the [mqtt]
section to the IPv4 address (see step 7 here)
Can you show me your [mqtt]
section in your configuration files?
-
No I do not see their status, I have a grey dot next to them saying “waiting for information”.
-
Yes, I did change the IPv4 address to match the one provided by Tailscale. Here is the leader config file:
And the shared config:
Changing the broker address in each config file individually does not fix the issue.
Hm, I believe it should be the opposite:
- the shared config file should have the ipv4. This is the config that the browser uses to connect to the leader’s MQTT. So your browser/personal machine needs to fetch from the ipv4 address (there isn’t a
biohalo-leader.local
on your personal machine’s network when your machine is remote, but there is a ipv4). - The workers (if any) should have the
.local.
address. - Your leader’s config should also have the .local address, or
localhost
is fine, too.
Yes, that was the problem. I misunderstood which config file should have the IPv4 address. Now it is working like a charm.
Thanks a lot for your time!
I’ll update the docs to make it more clear!