# Tether Interface Causing BlueOS connection issue

**URL:** <https://discuss.bluerobotics.com/t/tether-interface-causing-blueos-connection-issue/22255>\
**Category:** Communication Interfaces\
**Tags:** blueos, fathom-x\
**Created:** [January 9, 2026, 4:47pm UTC](https://discuss.bluerobotics.com/t/tether-interface-causing-blueos-connection-issue/22255 "2026-01-09T16:47:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xavi12](https://avatars.discourse-cdn.com/v4/letter/x/b5a626/32.png) [@xavi12](https://discuss.bluerobotics.com/u/xavi12)\
**Post date:** [January 9, 2026, 4:47pm UTC](https://discuss.bluerobotics.com/t/tether-interface-causing-blueos-connection-issue/22255/1 "2026-01-09T16:47:59Z")

</div>

We are assembling a BlueROV that was purchased over the Summer 2025. When confirming communications to the ROV via BlueOS, we were unable to load the webpage (blueos.local). On the interface box, the ‘power’ and ‘link active’ LEDs are illuminated. Additionally, these LEDs are illuminated on the board within the electronics enclosure.

We used a different tether interface box while troubleshooting and were able to confirm BlueOS connectivity. We swapped USB cables to rule that out. We also swapped the black front face where the tether connects to to rule out any damage to the internal blue and white comms wires.

Are there any other recommended steps for troubleshooting? There are similar posts within the forum but we have yet to find any that directly relate to this issue.

---

<div class="post-metadata">

**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/18385_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\
**Post date:** [January 9, 2026, 5:48pm UTC](https://discuss.bluerobotics.com/t/tether-interface-causing-blueos-connection-issue/22255/2 "2026-01-09T17:48:07Z")

</div>

Hi @xavi12 -  
If the link light is on for both th topside and vehicle, and you don’t have connection, it can _only_ be due to an IP address misconfiguration. Did you properly set your computers IP address on the USB ethernet interface that appears when the FXTI box is connected, as the instructions [document](https://bluerobotics.com/learn/bluerov2-software-setup/#network-setup)?

You could also try reaching the ROV directly at 192.168.2.2.

You will need to wait ~ 2 minutes after connecting power for the Raspberry Pi to finish starting BlueOS before you can reach the interface. Typically a blue light will start flashing on the Navigator at this point, and the thrusters emit a beep.

---

<div class="post-metadata">

**Author:** ![xavi12](https://avatars.discourse-cdn.com/v4/letter/x/b5a626/32.png) [@xavi12](https://discuss.bluerobotics.com/u/xavi12)\
**Post date:** [January 9, 2026, 6:04pm UTC](https://discuss.bluerobotics.com/t/tether-interface-causing-blueos-connection-issue/22255/3 "2026-01-09T18:04:04Z")

</div>

Hi @tony-white

The laptop has been configured in the past for connecting via a previous tether interface box we’ve used. We’ve utilized this laptop for BlueOS, QGroundControl, and Cockpit. I am assuming there is not any difference in the network configuration based on a change in interface boxes.

We did try connecting using the IP address (192.168.2.2). This worked on the alternative box we used for troubleshooting. Additionally, we did wait a few minutes for full initialization of the system with full illumination of LEDs in the electronics enclosure.

---

<div class="post-metadata">

**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/18385_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\
**Post date:** [January 9, 2026, 6:10pm UTC](https://discuss.bluerobotics.com/t/tether-interface-causing-blueos-connection-issue/22255/4 "2026-01-09T18:10:26Z")

</div>

Hi @xavi12

> [@xavi12](#):
>
> The laptop has been configured in the past for connecting via a previous tether interface box we’ve used.

The assumption that setup is not required for the new FXTI box is incorrect! Each USB to ethernet module has a different MAC address, and so needs to be configured in your OS to have the right IP

---

<div class="post-metadata">

**Author:** ![xavi12](https://avatars.discourse-cdn.com/v4/letter/x/b5a626/32.png) [@xavi12](https://discuss.bluerobotics.com/u/xavi12)\
**Post date:** [January 9, 2026, 6:17pm UTC](https://discuss.bluerobotics.com/t/tether-interface-causing-blueos-connection-issue/22255/5 "2026-01-09T18:17:01Z")

</div>

I see. We will circle back to this portion of the setup.

Thank you for the help @tony-white ! If the issues persist, I will update.