Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    1.2.3-RC3 problem: 404 - not found Admin Gui

    Scheduled Pinned Locked Moved 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
    3 Posts 2 Posters 8.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      ridnhard19
      last edited by

      emb/nano image built on Wed Sep 9 20:59:49 UTC 2009

      http://192.168.1.1/cgi-bin/check_hijack.html

      404 - Not Found

      When going to http://192.168.1.1 you get redirected to the address, http://192.168.1.1/cgi-bin/check_hijack.html

      This results in 404 - Not Found error. You can remove the cgi-bin/check_hijack.html and it works.  When u revisit it cant find it, remove the cgi…. works again.

      seems like that file is missing.

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        That's not a part of pfSense and never has been, if you're getting directed to that page, you're not connecting to pfSense. Seems like it's a part of Netgear routers.
        http://forum1.netgear.com/showthread.php?t=29689

        1 Reply Last reply Reply Quote 0
        • R
          ridnhard19
          last edited by

          That is odd… I've never owned a netgear router.  I do have my wireless and wired turned on and both active but the 192.168.1.0 subnet is only visable on the wired side X-Link to the newly flashed router..... No routing required to get to the admin interface. I just entered the 192.168.1.1 address again and my browser attempts to connect to something  ??? but i know there is no 192.168.1.* devices on my network its been unplugged since last night.... Crazy.

          Thanks for the kick :)

          Looking at my regular router's state table:

          tcp 192.168.1.1:80 <- 172.17.xx.xxx:51968 CLOSED:SYN_SENT
          tcp 172.17.xx.xxx:51968 -> EXT_IP:1813 -> 192.168.1.1:80 SYN_SENT:CLOSED

          Looks like someone's plugged something in to the wrong port! LOL

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.