Curl http query not working on Ispconfig 3.1b2

Discussion in 'Installation/Configuration' started by iletelier, Jun 26, 2016.

  1. iletelier

    iletelier New Member

    First of all Thanks a lot. Amazing Software!

    I have this problem with Curl... i couldn't find any information about it. So plz help.

    If you use Curl with https, it works:
    Code:
    # curl https://www.AnyDomain.com -v
    * Rebuilt URL to: https://www.AnyDomain.com
    * Hostname was NOT found in DNS cache
    *   Trying XXX.XXX.XXX.XXX...
    * Connected to www.AnyDomain.com (XXX.XXX.XXX.XXX) port 443 (#0)
    * successfully set certificate verify locations:
    *   CAfile: none
      CApath: /etc/ssl/certs
    * SSLv3, TLS handshake, Client hello (1):
    * SSLv3, TLS handshake, Server hello (2):
    * SSLv3, TLS handshake, CERT (11):
    * SSLv3, TLS handshake, Server key exchange (12):
    * SSLv3, TLS handshake, Server finished (14):
    * SSLv3, TLS handshake, Client key exchange (16):
    * SSLv3, TLS change cipher, Client hello (1):
    * SSLv3, TLS handshake, Finished (20):
    * SSLv3, TLS change cipher, Client hello (1):
    * SSLv3, TLS handshake, Finished (20):
    * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
    * Server certificate:
    *  subject: OU=Domain Control Validated; OU=PositiveSSL; CN=www.AnyDomain.com
    *  start date: 2016-05-05 00:00:00 GMT
    *  expire date: 2017-05-05 23:59:59 GMT
    *  subjectAltName does not match www.AnyDomain.com
    * SSL: no alternative certificate subject name matches target host name 'www.AnyDomain.com'
    * Closing connection 0
    * SSLv3, TLS alert, Client hello (1):
    curl: (51) SSL: no alternative certificate subject name matches target host name 'www.AnyDomain.com'
    
    But if you use http it doesn't.
    Code:
    # curl http://www.AnyDomain.com -v
    * Rebuilt URL to: http://www.AnyDomain.com
    * Hostname was NOT found in DNS cache
    *   Trying XXX.XXX.XXX.XXX...
    * connect to XXX.XXX.XXX.XXX port 80 failed: Connection timed out
    * Failed to connect to www.AnyDomain.com port 80: Connection timed out
    * Closing connection 0
    curl: (7) Failed to connect to www.AnyDomain.com port 80: Connection timed out
    
    The connection over 80 port also works well:
    Code:
    #wget http://www.somedomain.com/wp-content/themes/test/images/brand_logo.png
    converted 'http://www.somedomain.com/wp-content/themes/test/images/brand_logo.png' (ANSI_X3.4-1968) -> 'http://www.somedomain.com/wp-content/themes/test/images/brand_logo.png' (UTF-8)
    --2016-06-26 05:01:28--  http://www.somedomain.com/wp-content/themes/test/images/brand_logo.png
    Resolving www.somedomain.com (www.somedomain.com)... XXX.XXX.XXX.XXX
    Connecting to www.somedomain.com (www.somedomain.com)|XXX.XXX.XXX.XXX|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 8448 (8.2K) [image/png]
    Saving to: 'brand_logo.png'
    brand_logo.png      100%[=====================>]   8.25K  --.-KB/s   in 0s    
    2016-06-26 05:01:29 (152 MB/s) - 'brand_logo.png' saved [8448/8448]
    
    Any idea about ?

    Thanks in advance!
     
  2. Jesse Norell

    Jesse Norell Active Member

    If wget on port 80 works, I don't know of any reason why curl couldn't as well, so I probably won't have any help but will ask one obvious question: your curl and wget examples use www.anydomain.com vs. www.somedomain.com - can you use curl to access the same 'somedomain' url that wget can? Ie. it's not simply that 'anydomain.com' has port 80 blocked, right?
     
  3. iletelier

    iletelier New Member

    Hello Jesse, thank you!
    yes, anydomain.com and somedomain.com both are the same. That was just to show that the port 80 is not closed.

    Thanks!
     

Share This Page