Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 10 replies
  • Subscribers 29 subscribers
  • Views 33891 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

Firmware Upgrade - New Firmware could not be uploaded

Jason Shimmin

Trying to upload SFOS_16.05.6_MR-6 on to our CR35iNG but the manual upload process fails with:

New Firmware could not be uploaded. Please refer to online help for possible reasons

Have tried FF, IE and Chrome, with the same results.

Currently running SFOS 16.05.5 MR-5 and the disk util is:

Config: 30%
Content: 64%
Report: 4%

The Content seems quite high, but until now, I've never really paid too much attention to it.

Any suggestions?



This thread was automatically locked due to age.
Parents
  • 0

    This is a known issue. The following usually helps:

    1. Please use Chrome to upload (If this doesn't help, try firefox instead)

    2. Please make sure, you do upload Firmware via a fast LAN Connection (Not via a slow Internet Connection, this probably makes the Upload fail)

  • 0 in reply to HuberChristian

    I've tried using FF, Chrome and IE, but I get the same issue. I'm performing the upload from a fast LAN connection.

  • 0 in reply to Jason Shimmin

    Then the following steps are next:

    • Proof, you really try to upload the correct Firmware (Version).
    • Reboot Firewall, Try again.

    If that still doesn't help you should consider Sophos Support... It's maybe related to your Cyberoam Hardware which I do not know very well.

  • 0 in reply to HuberChristian

    I'll open a support ticket and report back with whatever the solution is.

  • 0 in reply to Jason Shimmin

    Update: The tech support guys suggested using CRLoader to upgrade the firmware, however, when I tried that, I get informed that this firmware can't be used with the current loader. This would explain why the firmware upload is failing in the web interface, just a pity I had to the take the firewall offline to discover that I need an updated loader.

  • +1 in reply to Jason Shimmin

    UPDATE and RESOLUTION:

    After a week with dealing with Sophos support, and several hours of remote support, it was finally discovered that I'd somehow managed to download the firmware for the virtual appliance, rather than for the dedicated firewall.  Oops!!

    In my defence, both the filenames are very similar, and the Sophos support guys didn't even realise either, even though they had tried to upload it themselves.

    Dedicated firewall firmware filename is: HW-SFOS_16.05.6_MR-6.SF210-266.gpg

    Virtual firewall firmware filename is: SW-SFOS_16.05.6_MR-6.SFW-266.gpg

    It's only now that the filenames are obviously different, but I was obviously paying too much attention to the versions numbers in the middle.

Reply
  • +1 in reply to Jason Shimmin

    UPDATE and RESOLUTION:

    After a week with dealing with Sophos support, and several hours of remote support, it was finally discovered that I'd somehow managed to download the firmware for the virtual appliance, rather than for the dedicated firewall.  Oops!!

    In my defence, both the filenames are very similar, and the Sophos support guys didn't even realise either, even though they had tried to upload it themselves.

    Dedicated firewall firmware filename is: HW-SFOS_16.05.6_MR-6.SF210-266.gpg

    Virtual firewall firmware filename is: SW-SFOS_16.05.6_MR-6.SFW-266.gpg

    It's only now that the filenames are obviously different, but I was obviously paying too much attention to the versions numbers in the middle.

Children