Thread Info
  • State Verified Answer
  • +4 person also asked this people also asked this
  • Locked Locked
  • Replies 12 replies
  • Subscribers 32 subscribers
  • Views 5437 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

Upgraded XG330 Appliance from 17.5.12 to 17.5.13 - Lost connection to Web console and user portal: "PR_END_OF_FILE_ERROR"

GernotMeyer

Hi all,

 

Upgraded XG330 Appliance from 17.5.12 to 17.5.13: After that update connection neither to web console nor to user portal is possible: browser says "PR_END_OF_FILE_ERROR".

Firewall is up and also working... but I am unable to manage any more.

Any hints?

Update: It seems, that the certificate for the webconsole access is gone: Browser says when checking the cert: Web Site Identity - Owner (This web site does not supply ownership information). No Button "show certificate" in any browser available when opening port 4444 or 1443. The certificate is gone.



This thread was automatically locked due to age.
  • +1 in reply to GernotMeyer

    Hi All,

    This issue is observed when the custom certificate used for WebAdmin and User portal access has a space character in the Certificate name.

    This issue is tentatively scheduled to be resolved in SFOS v17.5 MR14 and v18 MR3.

    Note: If the issue persists after attempting the workarounds below, please raise a support case and reference the ID NC-61956.

     

    Workarounds

    1. Re-import your client certificate with no spaces in the certificate name
    2. Reset the default Certificate
      • Reference this article to access your device via SSH: https://community.sophos.com/kb/en-us/133678 
        1. Access Sophos XG via console or SSH connection.
        2. Navigate to Option 2 "System Configuration".
        3. Select Option 4 "Reset Default Web Admin Certificate"
        4. Type 'Y' to continue.
  • 0 in reply to FloSupport

    Hi - I am showing the same behaviour, using internally generated certificates. Can I just confirm that it is the "CN" or "Certificate Name" field which may not contain spaces. Does this apply to any other fields - X.509 has a lot of "Name" fields!