Client website need to connect to itself

Discussion in 'Server Operation' started by Dark Magician, Oct 23, 2018.

  1. Dark Magician

    Dark Magician New Member

    Hi All,

    A client has a website which is throwing errors because, according to the builder of the website, it can't do requests to itself. It says nginx gives an 404. Which is odd since the server is running apache2 and not nginx. He says the website needs to do a curl request to the backoffice to retrieve information and that this is now not possible.

    The error he gets is:
    HTTP status code: 404
    Redirect: -
    IP: <removed for obvious reasons>
    Response preview: <html>
    <head><title>404 Not Found</title></head>
    <body bgcolor="white">
    <center><h1>404 Not Found</h1></center>
    I can visit the url and don't get an 404.

    Aside from the nginx error does anyone has an idea what can cause api errors with apache/curl do to the website not able to do a request to itself?

    When i do a "wget" form the command line to the URL I get:
    ERROR: The certificate of ‘’ is not trusted.
    ERROR: The certificate of ‘’ hasn't got a known issuer.
    The certificate's owner does not match hostname ‘’

    So I assume there is an issue somewhere there but the website has a green lock and when checking the Let's Encrypt certificate it's valid until 18 januari 2019. So I don't understand why everything is ok with the SSL on the website but the WGET says it's not.

    The server is installed conform

    Thanks in advance for any reply.

Share This Page