{"id":24380,"date":"2022-05-06T19:21:37","date_gmt":"2022-05-06T17:21:37","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=24380"},"modified":"2024-10-05T21:31:59","modified_gmt":"2024-10-05T19:31:59","slug":"sophos-intercept-x-neuinstallation-oder-update-stirbt-mit-http-error-403-6-mai-2022","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2022\/05\/06\/sophos-intercept-x-neuinstallation-oder-update-stirbt-mit-http-error-403-6-mai-2022\/","title":{"rendered":"Sophos Intercept X Install or Update ends with HTTP Error 403 (May 6, 2022)"},"content":{"rendered":"

\"Stop[German<\/a>]Brief information for administrators of a Sophos Intercept X endpoint solution. The vendor seems to be informing its customers about a serious problem. After a fresh installation of Sophos Intercept X Endpoint for Windows or an update, sus.sophosupd.com is no longer accessible, but reports an HTTP Error 403. In the meantime, Sophos has published a corresponding advisory (KB-000043980 dated May 6, 2022) about this problem. Here is some information about this issue.<\/p>\n

<\/p>\n

Sophos Intercept X Endpoint<\/h2>\n

\"\"Sophos Intercept X Endpoint<\/a>\u00a0 is a complete endpoint protection solution. According to the specifications, the product offers Endpoint Detection and Response (EDR), Extended Detection and Response (XDR), an anti-ransomware feature and more. The product is expected to be used in corporate environments to secure endpoints.<\/p>\n

Install\/Update ends with HTTP Error 403<\/h2>\n

German blog reader Stefan V. just informed me via Facebook about an issues with Sophos Intercept X Endpoint (thanks for the hint) and wrote:<\/p>\n

Hello, just received from Sophos via sms. Intercept X commits suicide<\/p><\/blockquote>\n

Nice paraphrase of the issue. Sophos has published an ADVISORY: New installations fail with HTTP Error 403 from https:\/\/sus.sophosupd.com\/ (KB-000043980) with the following error description:<\/p>\n

Issue<\/p>\n

New Installation and\/or Device updates fail with HTTP Error 403 from *ttps:\/\/sus.sophosupd.com\/
\nThis error is seen in C:\\ProgramData\\Sophos\\AutoUpdate\\SophosUpdate.log<\/p>\n

022-05-04T07:10:28.803Z [10656: 9772] I 403 from https:\/\/sus.sophosupd.com\/v3\/9745d246-c789-44c8-8d39-24555b7d9703\/151c12e7-04d6-490b-ba82-a19425c990be with proxy: <direct; no proxy>\r\n112022-05-04T07:10:28.804Z [10656: 9772] W Error refreshing service config: will sync using stale SUS config: No reachable update service locations \r\n122022-05-04T07:10:28.810Z [10656: 9772] E No reachable update service locations<\/pre>\n
And C:\\ProgramData\\Sophos\\CloudInstaller\\CloudInstaller.log<\/p>\n
2022-05-01T23:19:59.5312323Z INFO : 403 from https:\/\/sus.sophosupd.com\/v3\/d1cb1aee-737a-4892-a1f2-30812118b04a\/cfb2de67-b963-459c-985e-a75bedf4ecb0 with proxy: <direct; no proxy> \r\n112022-05-01T23:19:59.5312323Z ERROR : Error: No reachable update service locations \r\n122022-05-01T23:19:59.5312323Z ERROR : DownloadCommand::onRun() failed with std::exception: SDDS3 sync failed<\/pre>\n<\/blockquote>\n
The bug affects Sophos Intercept X Endpoint for Windows, which occurs due to issues with the endpoint record in Sophos Central. Customers experiencing the issue during an installation can work around it by renaming the hostname of the device and retrying the installation. This will create a new endpoint record in Sophos Central.<\/p>\n
Customers experiencing this error during updates can currently only fix the problem by reinstalling the product with a new hostname, Sophos wrote in its notice. It is only product updates that fail. Supplemental updates continue to work as intended, so protection is not currently affected.<\/p>\n","protected":false},"excerpt":{"rendered":"
[German]Brief information for administrators of a Sophos Intercept X endpoint solution. The vendor seems to be informing its customers about a serious problem. After a fresh installation of Sophos Intercept X Endpoint for Windows or an update, sus.sophosupd.com is no … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,580,1547,22],"tags":[466,1544],"class_list":["post-24380","post","type-post","status-publish","format-standard","hentry","category-issue","category-security","category-software","category-update","tag-problem","tag-software"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/24380","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=24380"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/24380\/revisions"}],"predecessor-version":[{"id":35844,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/24380\/revisions\/35844"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=24380"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=24380"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=24380"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}