Solved Certificate error with internal webclient

Discussion in '3CX Phone System - General' started by perfectcast, Dec 19, 2017.

Thread Status:
Not open for further replies.
  1. perfectcast

    Joined:
    Apr 27, 2016
    Messages:
    7
    Likes Received:
    1
    Hi,
    When browsing to the webclient on my customer's internal network I get the following certificate error on edge and chrome

    "There’s a problem with this website’s security certificate"

    I can continue to the webclient login page and use all functionality
    When I look at the certificate details I can see a warning ! against the following key details
    Key usage & Key constraints

    If I browse to the webclient externally everything is fine.

    Has anyone else seen this?
    Appreciate your feedback on this as its disconcerting for the users

    cheers
    Neil.
     
  2. sip.bg

    sip.bg Active Member

    Joined:
    Nov 7, 2016
    Messages:
    704
    Likes Received:
    219
    Have you installed 3CX using internal FQDN or IP address ?
    Is FQDN resolving internally to the internal address of the PBX ?

    If not, use: http://<internal_address_of_PBX>:5000 to access the PBX.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. perfectcast

    Joined:
    Apr 27, 2016
    Messages:
    7
    Likes Received:
    1
    Hi,
    3CX is running on an internal network
    The fqdn resolves to the public ip of the pbx so I'm trying to access the webclient on the internal network I'm using the internal server ip.
    accessing from remote locations via the fqdn works perfectly without error

    https://<internal_3CX_server_ip:5001/webclient

    as per the link in the welcome mail sent to user extension

    Neil.
     
  4. sip.bg

    sip.bg Active Member

    Joined:
    Nov 7, 2016
    Messages:
    704
    Likes Received:
    219
    Certificate is linked with FQDN.
    If you are trying https at internal address, there is no valid certificate for it, cerificates don't work on addresses. Try DNS splitting, if you can, in order FQDN to resolve internal address of the PBX, when used internally, or use http and port 5000 instead of https and port 5001 on internal address.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. perfectcast

    Joined:
    Apr 27, 2016
    Messages:
    7
    Likes Received:
    1
    Hi,
    thats perfect thanks for your help, using 5000 has resolved the issue
    have a good christmas
    cheers
    Neil.
     
Thread Status:
Not open for further replies.