RUTX50 - 5GHz WiFi AP Issue Returns as warranty expires!! Me No Happy at all!
Purchased this router with a STD 2yr warranty on the 25th January 2023 and reported an issue here on the 19th February 2025 less than one month after the expiration of my warranty.
The problem re-0ccured this morning but with a difference insofar as my 5GHz devices could not find my 5GHZ WiFi access Point at all, it essentially didn’t exist. The only way i found to resolve the issue was to delete the WiFi AP’s profile and then recreate it. 12 days after experiencing the issue the first time and less than a month after it’s warranty expired.
What WiFi antennas are you using—stock or third-party ones? Are they screwed in properly? Have there been any changes made in the wireless settings?
When deleting the 5 GHz WiFi AP profile, are you removing the default SSID or a custom-created one?
Have you tried performing a hard reboot or, if feasible, a factory reset on your RUTX50? Moreover, is the environment in which your device runs not overcrowded with other wireless networks? You can check this in Status → Wireless → Channel Analysis to see potential interference from nearby APs.
Additionally, to investigate this issue further, I’ve sent you a form to fill out. Please use 12570 as the ticket ID when completing it. Once submitted, we will contact you privately to gather the necessary information when the issue reoccurs.
I’m using the WiFi antennas supplied at purchase. They are securely connected.
My 2.4GHz and my 5GHz are custom created at purchase and recreated after factory resets. I applied a firmware upgrade without saving settings to version 12.3 just before the issue started, and initially thought the issue may have been related.
There are only 3 other nearby WiFi access points. Well until i did the requested scan i thought i only had 3 other nearby WiFi AP’s!! The first time i scanned a message appeared onscreen saying “Failed to … 5GHz data” only done this once and i was too slow read and to capture the error message.
The problem was resolved along with other issues being experienced by downgrading the firmware to an older version and then upgrading before doing anything else.
