Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 1752 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Webadmin port no longer works?

dswartz

Running a very recent 9.6 (I can't tell you which, as webadmin is broken right now).  I got up this morning, and saw this in my email:

The following Firmware Up2Date package has been successfully downloaded and
is now available for installation: 9.602003

For more information about this package please see the attached information.
        
-- 
HA Status          : HA MASTER (node id: 1)
System Uptime      : 12 days 0 hours 7 minutes
System Load        : 0.18
System Version     : Sophos UTM 9.601-5

Please refer to the manual for detailed instructions.

I went to port 4444, but it just times out.  I don't think the update was applied automatically, and I never had a chance to do it.  I haven't been logged in to the webadmin for a couple of days, so I can't tell you when it broke.  I tried restoring the auto-backup from Saturday morning.  No joy.  I rebooted.  No joy.  What is the next step (hopefully short of a reinstall?)

 



This thread was automatically locked due to age.
  • 0

    Interesting results from an experiment.  I can login via ssh.  It claims port 444 is being listened to:

    <M> gateway:/root # netstat -anp|grep 4444
    tcp        0      0 0.0.0.0:4444            0.0.0.0:*               LISTEN      7116/httpd          

    Yet if I try to telnet to port 4444, tcpdump in the ssh session shows:

    <M> gateway:/root # tcpdump -i eth0 -lnn host 10.0.0.30   
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
    11:21:21.255758 IP 10.0.0.30.59582 > 10.0.0.1.4444: Flags [S], seq 2134266275, win 29200, options [mss 1460,sackOK,TS val 67061676 ecr 0,nop,wscale 7], length 0
    11:21:22.257524 IP 10.0.0.30.59582 > 10.0.0.1.4444: Flags [S], seq 2134266275, win 29200, options [mss 1460,sackOK,TS val 67062678 ecr 0,nop,wscale 7], length 0

    It's like port 4444 is locked out via iptables?

  • 0 in reply to dswartz

    Oh good lord, save me from monday mornings.  I forgot that I changed my workstation IP address.  I had management access control to only allow that host :)

Unfiltered HTML