NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

aolney's avatar
aolney
Aspirant
Sep 19, 2021

Sorry,your timestamp is expired - SOLVED on Chrome

Saw others having this problem, but I guess I don't have the status to reply.

 

The problem is with the timestamp. When you try to log into the extender admin page, hit F12 on your browser to see the page source (Elements tab after you hit F12).

 

The form has a timestamp in the action field. Double click that field and delete the entire timestamp portion, e.g. timestamp=12345678. Leave the rest of the field alone. Then type into the form as directed.

 

It appears that if you delete the timestamp field from the form, whatever check is happening on the extender involving the timestamp is skipped.

 

Overall the work around is annoying, but it works.

11 Replies

  • Whatever that time stamp error is, or was, I can now  only get to the Setup new extender page instead of the login page! How do you fix that?

    • olympos1625's avatar
      olympos1625
      NETGEAR Employee Retired

      Hi SteveCampsOut1,

       

      Thank you for reaching out. May we know if this is a new wireless extender? What is the model number? Have you tried contacting our support team over the phone? Have you been able to complete the setup process before? What is the model of your extender?

       

      Please do not hesitate to let me know if you need further assistance. 

       

      Regards,

       

      Oliver

      Community Team

      • SteveCampsOut1's avatar
        SteveCampsOut1
        Tutor

        No, it's an old extender and it's been setup and is working I was just trying to update the fireware and got the timestamp message and no update. It's still working but now I'm completely locked out of it. I'm not going to mess with it as long as my network is still extended. It's the WN3000v3. I've had it for at least 5 year if not longer. (I'm old I forget). The solution posted above doesn't work in Firefox.

  • I had this issue for months. It was very frustrating.
    Finally I factory reset the router and it seems to be working afterwards.

     

    I couldn't find the timestamp value you referenced in the HTML unfortunately, but boy are there a lot of errors spitting out in the console in the web interface 😱