Forum Discussion

Frank_Slicer's avatar
6 years ago

Alert Can't connect https, but can curl from collector

Got an issue where getting a status "5", can't connect on https-443 to a web server on AWS EC2.  But can connect to https site from public browser and using curl from the collector, without issue.

Running diagnostics through LM shows a timeout. The "Poll Now" data looks fine except Normal Datapoints shows errors.  These errors cannot be confirmed.



6 Replies

Replies have been turned off for this discussion
  • It does look like it's not able to communicate with the web server. Status 5 is "Network error" and it isn't showing any content or headers. Have you tried using the debug console !http command to see what it shows? It supports using https as a url. Do you have a proxy? I don't think LM collector will look at the windows/IE proxy settings while other software might.


  • I'm able to send !http curl https://<url> . and !http https://<url> from the debug..... from the later I get....

    HTTP response received at at: 2018-09-26 15:17:38.362. Time elapsed: 40ms
    HTTP/1.1 200 OK
    x-powered-by: node.js/8.9.2
    accept-ranges: bytes
    content-type: text/html
    server: (Linux)
    allow: GET, HEAD, OPTIONS
    cache-control: no cache, no-store, must-revalidate
    pragma: no-cache
    expires: 0
    last-modified: Tue, 25 Sep 2018 12:51:43 GMT
    etag: "3375771597"
    transfer-encoding: chunked
    x-response-time: 0.38 ms
    date: Wed, 26 Sep 2018 15:17:38 GMT
    connection: close

    <!DOCTYPE html>
        <meta charset="utf-8">
        <meta http-equiv="X-UA-Compatible" content="IE=edge">
        <meta name="description" content="">
        <meta name="viewport" content="width=device-width, initial-scale=1">

    followed by the contents of the home page........

  • Very odd, was your "HTTPS-" DataSource modified? Perhaps worth checking the Repository if there is an updated version of or difference in that DataSource from core.

    Otherwise I would dig thru the wrapper and other collector logs or reach out to LM support.

  • I had the same issue and was able to resolve it with the following steps:

    1. Open ServerManager in host
    2. Add Roles and Features
    3. Before You Begin...Next,
    4. Install Type...Next,
    5. Server Selection...Next,
    6. Select Web Server (IIS) > Select Add Features...Next
    7. Web Server Role (IIS)...Next
    8. Roles Services...Next
    9. Confirmation...Install

    10. Select the new IIS option from Left Pane > Right click your server name > Internet Information Services Manager

    11. Expand hostname > Right click Default Website > Edit Bindings > Add > type: Https > SSL Certificate: My ADFS Cert > close.

    12. Right click Default Web Site > Manage Website > Start

    13. Go to your LMportal > ADFS Host > HTTPS-443 > Raw Data > poll now.