This device was purchased two years ago and I attempted to configure it as a failover for my Gen2 Starlink. After many hours, I could not get the failover to work, and the unit remained in storage until today when I attempted to configure it for a new application. Now, I can’t access the ADMIN panel at 192.168.1.1 even after resetting the device. After about 5 minutes on this address, I get a screen that says “STARLINK You are connected to Starlink”. Starlink is not active, and there is only an ethernet cable connecting the unit to the computer.
Any ideas, or is the RUTX50 ready for the trash heap?
Try downloading a copy of the latest firmware and then try flashing the device using bootloader.
Thank you very much for the response.
I followed the procedure (adapted for Win11) with the firewall turned off and with Chrome in Incognito mode, and in a fixed IP computer address of 192.168.1.2, I am not able to access the bootloader at 192.168.1.1/index.html. After about a minute I get a browser message “took too long to respond”.
Any other ideas?
When your PC is connected to the RUTX ethernet LAN port, and it has no other cable / WiFi connections, does the RUTX assign it an IP, and is it different to something in the 192.168.1.xxx range? Don’t forget to turm off your static IP first.
Can you also check if you can connect to the RUTX WiFi.
Hello,
If I understood correctly, when you try to reach your RUTX50, you reach the starlink instead? If so, it sounds like an IP conflict to me (your Starlink is under the same subnet / has the same IP address as the RUTX50). I did a quick Google search, and can see that Starlink routers also default under 192.168.1.1, meaning that if your PC is in any way connected to the Starlink router, whether it’d be Wi-Fi or Ethernet, you’ll be redirected to it.
My suggestion - instead of trying to reset the RUTX50, try turning it on, grabbing your phone, and connecting to the Wi-Fi network of the RUTX50 (you’ll see the credentials on the back of the device), then try accessing 192.168.1.1 from your phone once connected to the Wi-Fi. I’m pretty certain that you’ll have no trouble reaching the interface whatsoever.
However, if it still ends up with the fact that you’re unable to reach the device, then kindly follow the Bootloader process as @Mike has suggested; however, ensure that your PC is in no way connected to the Starlink (no Wi-Fi, no ethernet). Also, pre-download the firmware file for the RUTX50, since you’ll more than likely have no internet: RUTX50 Firmware Downloads - Teltonika Networks Wiki
Regards,
M.