Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 2 subscribers
  • Views 20940 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

Cannot update via HTTP Path

Markus W

 Hi guys,

I try to update the endpoints via the HTTP update method. I followed this guide: https://community.sophos.com/kb/en-us/38238 and had no errors.

The endpoints can't find "SAVXP" when using this url as update path. (Cannot download from server <url>) I can open the URL in my browser and it will open my index.html which I created for testing. So the url is reachable but somehow the endpoint cannot download the updates. 

The path where the index.html is and the URL is forwarding: C:\ProgramData\Sophos\Update Manager\Update Manager

The url: sophos-console.****.de/SophosUpdate

I don't know how to solve this issue, since our endpoints should be able to update their software also when not in the company.

 

Thank you for any help!



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

    Hello Markus W,

    could you show the ALUpdate log (URL's host blackened) with the failures? Also, what's the URL in your updating policy?
    the URL and index.html
    you shouldn't manually create/modify/delete arbitrary files in the update location. Anyway, what's the URL? and where in the local file system is index.html?

    Christian

  • 0 in reply to QC

    Hi Christian,

    I tried to find the ALUpdate.log file but there isn't a folder called AutoUpdate, neither in C:\Program Files\Sophos nor in C:\Program Files (x86)\Sophos

    The primary path in the endpoint software is this one: sophos-console.*****.de/.../

    The index.html is the path C:\ProgramData\Sophos\Update Manager\Update Manager, the same path IIS is using.

     

     

    Thank you in advance

    Markus

  • 0 in reply to Markus W

    Hello Markus,

    the ALUpdate.log
    there's at least one article which gives only the incorrect "legacy" location. For all supported versions the logs are under %ProgramData%.
    Primary path and published folder look correct (and index.html in this location is "safe"). It works here with the same setup.

    Christian

  • 0 in reply to QC

    Ok I found it, it's quite large (pressed Update Now in the Tray and took only the log from there one).

    I uploaded the log to pastebin, hope that's ok for you! https://pastebin.com/acEjCFGx

     

    Markus

  • 0 in reply to Markus W

    Hello Markus,

    hm, it returns 80040f04, meaning server couldn't be contacted. Looking at the URL, or rather a product's URL I see *.de/SophosUpdate/savxp. For an SEC managed install the path should contain /CIDs/Snnn/SAVSCFXP/.
    As the log doesn't show an update attempt for RMSNT this seems to be a stand-alone install where you've entered the update location in the local GUI or during install (manually or pre-configured). The update location configured on an endpoint must contain to path up to SAVSCFXP (in case of Windows).

    Christian

Reply
  • 0 in reply to Markus W

    Hello Markus,

    hm, it returns 80040f04, meaning server couldn't be contacted. Looking at the URL, or rather a product's URL I see *.de/SophosUpdate/savxp. For an SEC managed install the path should contain /CIDs/Snnn/SAVSCFXP/.
    As the log doesn't show an update attempt for RMSNT this seems to be a stand-alone install where you've entered the update location in the local GUI or during install (manually or pre-configured). The update location configured on an endpoint must contain to path up to SAVSCFXP (in case of Windows).

    Christian

Children
Unfiltered HTML