Community
User Guides
Support
Community
Help Forums
English Forum
General
About our Community
General Discussion
News and Feedback
Products
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Beta programs
Feature Requests
Finnish Forum (Tukifoorumi)
Tuotteet Kotiin
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Muut tietoturvatuotteet
Support Articles
Language
English
Suomi
Deutsch
Français
日本語
Svenska
Dansk
Italiano
Nederlands
Norsk
Polski
中文 (繁體)
Products & Services
F-Secure TOTAL
F-Secure SAFE / Internet Security / Anti-Virus
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Common topics
User Guides
Support
Login
|
Register
Security Cloud Client is not connected on Server Security / Client Security - F-Secure Community
<main> <article class="userContent"> <h3 data-version="19" data-article="000014893" data-id="issue">Issue:</h3> <p>Security Cloud Client is not connected on Server Security / Client Security</p> <h3 data-id="resolution">Resolution:</h3> <p></p><p>You need to ensure that the affected F-Secure host is allowed to connect to the URL:</p> <ul><li>* <a href="https://a.karma.sc2.fsapi.com" rel="nofollow">https://a.karma.sc2.fsapi.com</a></li><li>* <a href="https://api.doorman.fsapi.com" rel="nofollow">https://api.doorman.fsapi.com</a></li></ul><p>You can try to open <a href="https://a.karma.sc2.fsapi.com/healthcheck" rel="nofollow">https://a.karma.sc2.fsapi.com/healthcheck</a> and <a href="https://api.doorman.fsapi.com/doorman/v1/healthcheck" rel="nofollow">https://api.doorman.fsapi.com/doorman/v1/healthcheck</a> in web browser on the host. If connectivity works you shall see "OK" message in return.<br><br>Also, do take note that the URLs are subject to change in the near future. We recommend to allow the connectivity to *.f-secure.com and *.fsapi.com. To validate the connectivity to F-Secure backend, you can run the F-Secure Connectivity Tool using all accounts including LOCAL SYSTEM and Network Service account: <a rel="nofollow" href="https://download.sp.f-secure.com/connectivitytool/ConnectionChecker.exe">https://download.sp.f-secure.com/connectivitytool/ConnectionChecker.exe</a><br><br>If this host requires a connection via HTTP proxy to access this URL, you have to configure these settings via the F-Secure Policy Manager Console:</p> <ol><li>Log on to your <b>F-Secure Policy Manager Console</b>.</li><li>Select the <b>Policy domain</b> <img alt="User-added image" src="https://f-secure--c.eu41.content.force.com/servlet/rtaImage?eid=ka167000000JcNT&feoid=00Nb000000AP6yL&refid=0EM0X000001gp47" class="embedImage-img importedEmbed-img"></img> or <b>Host </b><img alt="User-added image" src="https://f-secure--c.eu41.content.force.com/servlet/rtaImage?eid=ka167000000JcNT&feoid=00Nb000000AP6yL&refid=0EM0X000001gp4C" class="embedImage-img importedEmbed-img"></img> / <img alt="User-added image" src="https://f-secure--c.eu41.content.force.com/servlet/rtaImage?eid=ka167000000JcNT&feoid=00Nb000000AP6yL&refid=0EM0X000001gp4H" class="embedImage-img importedEmbed-img"></img> where you want to edit the policy on.</li><li>Switch to the <b>Standard view</b>.</li><li>Go to <b>Centralized management > Internet connections</b></li><li>Modify the value to suit your HTTP proxy requirements, for example, '<a href="http://my.domain.com:1234'" rel="nofollow">http://my.domain.com:1234'</a>;</li><li>Ensure that the setting "Use HTTP proxy" is not configured to "No"</li><li>Distribute the policy (Ctrl + D)</li></ol><p><b>Note: </b>Server Security 14.00 and Client Security 14.x do not support proxy authentication. We recommend to install the latest Server Security 15.00 and Client Security 15.10 for proxy authentication support. At the same time, do take note that the new product release support basic and NTLM authentication type only.</p> <p><br>If issue is still happening, you can try to clear the cache, by doing the following:</p> <ol><li>Open a Command prompt as an administrator</li><li>Stop the services by running commands: <ul><li>net stop fsulhoster</li><li>net stop fsulnethoster</li></ul></li><li>Open the Windows Registry editor (regedit), backup and clear values under <ul><li>HKEY_USERS\S-1-5-20\SOFTWARE\F-Secure\Ultralight\<b>Doorman</b></li></ul></li><li>Remove all files from "C:\Windows\ServiceProfiles\NetworkService\AppData\Local\F-Secure\fsscor"</li><li>Start the services by running commands: <ul><li>net start fsulhoster</li><li>net start fsulnethoster</li></ul></li></ol><p>Article no: 000014893</p> </article> </main>