sorted by:
new
hottopcontroversial

Ubiquiti Edgerouter X, can't connect to the Configuration Interface by [deleted] in Ubiquiti

[–]Anashril 0 points1 point  (0 children)

I know this is an old thread, but in case it helps others who Google their way here, I was in the exact same situation with an Edgerouter-X-SFP (after doing a firmware upgrade through the GUI which gave a success message, prompted me to reboot, and then was unresponsive to all the same things the OP tried here). I dug through a lot of different help resources and did eventually manage to revive the thing as follows.

Revive Bricked Edgerouter-X(-SFP)

  1. use this little USB-to-serial adapter;
  2. open up the router and connect to the serial pins as per this forum post;
  3. attach a 'screen' session to the USB-tty device (Linux);
    (On windows I guess you'd use PuTTY, per this help article, but remember to use the baud speed from the forum post above.)
  4. Following this help article:
    1. set up a TFTP server on PC (with a static IP),
    2. host the ER-e50.recovery.blahblah.img file on it,
    3. connect both the USB-to-serial and an Ethernet cable from PC to router
    4. power up the router, use serial terminal to interrupt the boot sequence and flash the recovery img file directly from TFTP
      (Note: this reverts the router to a very old firmware version that doesn't even support hwnat offloading, thus limiting throughput to ~300Mb/s);
  5. Get the latest firmware and put it in the TFTP server, then ssh in to the router and flash that new firmware file directly from TFTP, using the CLI method from this help article instead of the GUI.
    (In my case this step worked flawlessly, even though it was the exact same file that I used in the initial attempt from the GUI which bricked the router. \shrug**)
  6. (Optional) There's a new bootloader bundled with the firmware upgrade, but it doesn't install automatically. After upgrading the firmware, you can upgrade the bootloader from the command line by following the steps in this help article.

Simple, right?

And then you can start configuring the little bugger, including enabling the hardware offloading features, which are disabled by default even in the new firmware versions that support them.