Endpoint Protection

Expand all | Collapse all

SEP 14.3 : no console access after upgrading from 14.2RU2MP1

  • 1.  SEP 14.3 : no console access after upgrading from 14.2RU2MP1

    Posted 18 days ago
    Hello,
    We had a working SEPM 14.2 RU2MP1 on windows server 2016
    Just upgraded it to 14.3.0 (14.3.558.0)

    But after upgrade, impossible to launch console (java or web).
    http://myserverfqdn:9090/ corrrectly renders
    I can even dowload the server certificate http://myserverfqdn:9090/downloadServerCertificate iand it is correct (generated from our internal PKI, not a self signed certificate)
    but https://myserverfqdn:8443/console/apps/sepm is refused by browser : TLS can't be negociated

    furthermore, connectivity tests for client communication are corrects :
    https://myserverfqdn/secars/secars.dll?hello,secars correctly replies a 200 OK. Checked it allows TLS1.2 and 1.0

    Anybody has a clue how to repair the console ??
    Thank you in advance


  • 2.  RE: SEP 14.3 : no console access after upgrading from 14.2RU2MP1

    Posted 17 days ago
    I would suggest opening up a Support Ticket for this issue.

    ------------------------------
    John Owens
    Principal Product Support
    Symantec
    United States
    ------------------------------



  • 3.  RE: SEP 14.3 : no console access after upgrading from 14.2RU2MP1

    Posted 16 days ago
    Thank you. Case opened, not yet a solution....


  • 4.  RE: SEP 14.3 : no console access after upgrading from 14.2RU2MP1

    Posted an hour ago
    Hello, have you got any solution for this case? I experienced very similar behavior with our SEPM, also  after 14.2RU2MP1 -> 14.3 upgrade. Web console shows some kind of certificate issue in different browsers - ERR_SSL_PROTOCOL_ERROR, and local console shows "Unexpected server error", also when all of the services are running.