To stay updated on your favorite discussions, please create an account or log in. Then, click the Bookmark icon to subscribe and receive notifications.

Why is my Server Manager Console not registering ?

HomerD
HomerD Member Posts: 2 Security Scout
in Business Suite

Hello everyone,

I have a Policy Manager Console under Windows Server 2016 and my product cannot be registered because the website that you can see in the screenshot displays a 404 HTTP error. The trafic is not blocked by Windows firewall nor our firewalls, I can see the trafic being authorised and going out in the logs. How can I register my product ?

Thank you in advance.

image.png

Answers

  • Sethu Laks
    Sethu Laks Staff, Moderator Posts: 272 W/ Moderator
    edited September 27

    Hi @homerD

    Thank you for reaching out to the WithSecure Community,

    The first thing you should do, if you get this error message, is to check that you are running a supported version of Policy Manager Server. Check that the Policy Manager version you are running on your server is not listed as end-of-life: Product lifecycle announcement | WithSecure™

    If your Policy Manager Server is supported, check your network configuration to make sure that Policy Manager Server is able to access the registration server.

    Steps to test the connectivity from the same host where Policy Manager Server is installed:

    • You need Command Prompt and curl.exe to run the following command:
      curl https://corp-reg.fsapi.com
      • Connection can be treated as successful if you get the html output containing the following: 
        <title>Error 404 Not Found</title>
        <body><h2>HTTP ERROR 404 Not Found</h2>
      • If you use a HTTP proxy, test the connectivity via this proxy: 
        curl https://corp-reg.fsapi.com --proxy [protocol://]proxy_address[:port]
      • If you cannot use curl, try to access https://corp-reg.fsapi.com via Browser
    • If the connection is blocked, make sure you have allowed the DNS names *. f-secure.com and*. fsapi.com to your firewall, as described here.
    • If the browser test is showing that the site is not trusted, it would mean that your host does not trust Amazon Root CA 1 root certificate or intermediate ones.
    • If you are using a HTTP proxy, please configure it in the fspms.proxy.config. After the configuration, restart the Policy Manager Service. Depending on the Policy Manger versions and operating system the config file is located at:
      • Windows:
        • version 15: C:\Program Files (x86)\F-Secure\Management Server 5\data\fspms.proxy.config
        • version 16: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\fspms.proxy.config
      • Linux: /var/opt/f-secure/fspms/data/fspms.proxy.config

Categories