Tomato Issue

Discussion in 'Tomato Firmware' started by GreenThumb, Apr 4, 2012.

  1. GreenThumb

    GreenThumb Addicted to LI Member

    Hi, I've been using Tomato for a few years on my WRT54GL without issue. Today I noticed that I can not connect to the Tomato screen within my router ( Every time I try, I get a browser error message about not being able to connect. "Firefox can't establish a connection to the server at" Same thing happens on Chrome, and it doesn't matter if I am using my Windows partition or my Linux partition.

    I have reset the router several times to no avail. I have noticed my Internet "mostly" works, but I am getting general connection errors here and there.

    Is it time for a new router or is there some way to troubleshoot this?

    I believe I am using tomato v1.28 if my memory serves.

  2. Monk E. Boy

    Monk E. Boy Network Guru Member

    A 30-30-30 reset is extremely likely to bring it completely back to life, but will reset everything to default settings. If your WAN uses DHCP then you should be up and running pretty much instantly, though obviously having lost all non-default settings. If you have a .cfg (configuration) backup you can go into the administrative interface and restore settings from it and get them all back... but you have to make that backup before you were having problems.

    A 30-30-30 reset is where you have the router plugged in and otherwise working (give it 30 seconds to boot if you plug it in fresh, right before starting into the reset procedure) then hold the reset button on the back for 30 seconds, continue holding in the reset button and disconnect power from the router, hold the reset button for 30 seconds, continue holding in the reset button and connect power, then hold for a final 30 seconds and release. At the end of it you will have held the reset button down for a continuous 90 seconds, just removing/connecting power for two of the 30 second periods.

    This is likely the easiest way for someone not familiar with Linux to get it back. If you were familiar with Linux you could possibly telnet or ssh into the router and then see what's gone wrong with the http server on the router (though if telnet/ssh is disabled then even that's a no-go).
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice