I’m trying to wget to my own box, and it can’t be an internal address in the wget (so says another developer).
When I wget, I get this:
wget http://example.com
--2013-03-01 15:03:30-- http://example.com/
Resolving example.com... 172.20.0.224
Connecting to example.com|172.20.0.224|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://www.example.com/ [following]
--2013-03-01 15:03:30-- https://www.example.com/
Resolving www.example.com... 172.20.0.224
Connecting to www.example.com|172.20.0.224|:443... connected.
OpenSSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Unable to establish SSL connection.
I believe it is because I do not have the certificate setup properly. Using openssl:
openssl s_client -connect example.com:443
CONNECTED(00000003)
15586:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:588:
While if I do the same command on another site, it shows the entire cert.
Perhaps the ssl cert was never setup in the conf file on Apache for that domain?
If so, what should I be specifying in the virtualhost? Is there any alternative other than specifying --no-check-certificate because I don’t want to do that?
JoeG
7,03110 gold badges58 silver badges103 bronze badges
asked Mar 1, 2013 at 21:11
meder omuralievmeder omuraliev
181k70 gold badges385 silver badges428 bronze badges
1
SSL23_GET_SERVER_HELLO:unknown protocol
This error happens when OpenSSL receives something other than a ServerHello in a protocol version it understands from the server. It can happen if the server answers with a plain (unencrypted) HTTP. It can also happen if the server only supports e.g. TLS 1.2 and the client does not understand that protocol version. Normally, servers are backwards compatible to at least SSL 3.0 / TLS 1.0, but maybe this specific server isn’t (by implementation or configuration).
It is unclear whether you attempted to pass --no-check-certificate or not. I would be rather surprised if that would work.
A simple test is to use wget (or a browser) to request http://example.com:443 (note the http://, not https://); if it works, SSL is not enabled on port 443. To further debug this, use openssl s_client with the -debug option, which right before the error message dumps the first few bytes of the server response which OpenSSL was unable to parse. This may help to identify the problem, especially if the server does not answer with a ServerHello message. To see what exactly OpenSSL is expecting, check the source: look for SSL_R_UNKNOWN_PROTOCOL in ssl/s23_clnt.c.
In any case, looking at the apache error log may provide some insight too.
Sam
11.7k9 gold badges48 silver badges68 bronze badges
answered Mar 1, 2013 at 22:50
3
In my case I had not enabled the site ‘default-ssl’. Only ‘000-default’ was listed in the /etc/apache2/sites-enabled folder.
Enable SSL site on Ubuntu 14 LTS, Apache 2.4.7:
a2ensite default-ssl
service apache2 reload
answered May 2, 2015 at 1:03
1
Just a quick note (and possible cause).
You can have a perfectly correct VirtualHost setup with _default_:443 etc. in your Apache .conf file.
But… If there is even one .conf file enabled with incorrect settings that also listens to port 443, then it will bring the whole SSL system down.
Therefore, if you are sure your .conf file is correct, try disabling the other site .conf files in sites-enabled.
answered Dec 2, 2015 at 9:04
Nostalg.ioNostalg.io
3,6341 gold badge27 silver badges31 bronze badges
2
There are a few possibilities:
- Your workstation doesn’t have the root CA cert used to sign your server’s cert. How exactly you fix that depends on what OS you’re running and what release, etc. (I suspect this is not related)
- Your cert isn’t installed properly. If your SSL cert requires an intermediate cert to be presented and you didn’t set that up, you can get these warnings.
- Are you sure you’ve enabled SSL on port 443?
For starters, to eliminate (3), what happens if you telnet to that port?
Assuming it’s not (3), then depending on your needs you may be fine with ignoring these errors and just passing —no-certificate-check. You probably want to use a regular browser (which generally will bundle the root certs directly) and see if things are happy.
If you want to manually verify the cert, post more details from the openssl s_client output. Or use openssl x509 -text -in /path/to/cert to print it out to your terminal.
jww
95k88 gold badges396 silver badges860 bronze badges
answered Mar 1, 2013 at 21:22
Dave S.Dave S.
6,24930 silver badges33 bronze badges
2
I had this problem when setting up a new EC2 instance. I had not added HTTPS to my security group, and so port 443 was not open.
answered Nov 9, 2015 at 20:35
Steve EllisSteve Ellis
4945 silver badges13 bronze badges
For me a DNS name of my server was added to /etc/hosts and it was mapped to 127.0.0.1 which resulted in
SL23_GET_SERVER_HELLO:unknown protocol
Removing mapping of my real DNS name to 127.0.0.1 resolved the problem.
answered Mar 13, 2018 at 10:26
Kirill OficerovKirill Oficerov
2,0522 gold badges15 silver badges11 bronze badges
I meet this same question. The port 443 wasn’t open in Centos.
Check the 443 port with the following command:
sudo lsof -i tcp:443
In the first line of /etc/httpd/conf.d/ssl.conf add this two lines:
LoadModule ssl_module modules/mod_ssl.so
Listen 443
answered Mar 31, 2017 at 9:47
GeekHadesGeekHades
3,0303 gold badges18 silver badges15 bronze badges
This problem happened for me only in special cases, when I called website from some internet providers,
I’ve configured only ip v4 in VirtualHost configuration of apache,
but some of router use ip v6, and when I added ip v6 to apache config the problem solved.
answered May 31, 2019 at 16:18
masoud2011masoud2011
8459 silver badges8 bronze badges
The problem I faced was in client server environment. The client was trying to connect over http port 80 but wanted the server proxy to redirect the request to some other port and data was https. So basically asking secure information over http. So server should have http port 80 as well as the port client is requesting, let’s say urla:1111subB.
The issue was server was hosting this on some other port e,g urla:2222subB; so the client was trying to access over 1111 was receiving the error. Correcting the port number should fix this issue. In this case to port number 1111.
answered Dec 23, 2013 at 9:32
Wget SSL error can occur due to many different reasons that include Wget not supporting HTTPS downloads, no-check-certificate, the issue with secure protocol option, and son on.
Wget command help in downloading files from the Internet through the command line.
At Bobcares, we often receive requests to fix this error as part of our Server Management Services.
Today, let’s discuss how our Support Engineers fix this error easily for our customers.
Top causes and fixes for the Wget SSL error
It is a very generic error. When the Wget SSL error occurs, it normally pops an error message “Unable to establish SSL connection”.
Here are a few causes of the error. Let’s discuss them in detail.
Wget not supporting https downloads resulting in Wget SSL error
This error occurs when Wget does not support the https downloads in some distributions.
If we find any such error our Support Engineers fix this by compiling the source code manually using OpenSSL. After that, we can do https downloads.
Errors with the secure protocol option
Sometimes, the error may be with the secure protocol option. In such cases, our Support Engineers fix this by adding a secure-protocol option with a suitable protocol argument.
We set this using the command below.
secure-protocol=protocolWe can set the protocol to any of these ‘auto’, ‘SSLv2’, ‘SSLv3’,‘TLSv1_1’, ‘TLSv1_2.
And, this can resolve the error easily. However, the older versions of TLS are vulnerable.
Wget error due to Date/time
Date/time mismatch can be a cause for the error to popup.
We double-check the date/time and refresh the SSL certificate to fix this error. We use the command below for refreshing.
/usr/sbin/update-ca-certificates --freshNo-check-certificate
Similarly, we can also fix the error by setting “–no-check-certificate“. On setting this, Wget does not check for servers certificate.
This will generally prompt for a password check. But this method is not always recommended.
[Need any further assistance with the Wget errors? – We can help you fix it!]
Conclusion
In short, when the Wget SSL error occurs, it pops an error message “Unable to establish SSL connection” which is a generic error. In today’s article, we discussed how our Support Engineers resolve this error easily for our customers.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
var google_conversion_label = «owonCMyG5nEQ0aD71QM»;
Содержание
- Wget returning error: «Unable to establish SSL connection.»
- 7 Answers 7
- Unable to establish SSL connection upon wget on Ubuntu 14.04 LTS
- 4 Answers 4
- Windows wget unable to establish ssl connection
- Re: wget unable to establish ssl connection
- Re: wget unable to establish ssl connection
- Re: wget unable to establish ssl connection
- Re: wget unable to establish ssl connection
- Re: wget unable to establish ssl connection
- Невозможно установить SSL-соединение при wget в Ubuntu 14.04 LTS
- 4 ответа
- OpenSSL: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version #93
- Comments
- abmudd commented Oct 29, 2017
- prvnmora commented Feb 23, 2018
- prvnmora commented Feb 23, 2018
- mixxael commented Feb 23, 2018
- ravisingla commented Mar 5, 2018
- jonathan1055 commented Mar 5, 2018
- ravisingla commented Mar 5, 2018
- jonathan1055 commented Mar 5, 2018 •
- hukai916 commented Mar 7, 2018
Wget returning error: «Unable to establish SSL connection.»
When I try to run Wget with the following options:
I get the error: Unable to establish SSL connection. The website that I am trying to download is safe.
I have also tried to change the protocol to SSLv3, but it still is not working.
Can someone tell me why it is doing this and how to get around it?
7 Answers 7
As SSL Labs shows, only TLSv1.0 and above are supported by minecraft.net. You can’t use SSLv3 with it. It’s likely that your version of wget doesn’t support this (possibly due to being too old). Try upgrading it.
You can find a newer version here: Windows binaries of GNU Wget
It works fine, I had the same problem.
Had a similar error, but in my case only “Unable to establish SSL connection.” was shown without explanation. I have used a WinWget, which included a wget compiled without SSL support. Solved by downloading full version from https://eternallybored.org/misc/wget/
Check also if installed OpenSSL supporting TLS by running:
I had this problem and using a newer wget as mentioned in other answers solved it. However I’m not into installing binaries from random sites, if you’re on Windows as the OP is and have WSL installed with Ubuntu then you can open a bash shell and have the latest ubuntu wget. If wget not installed:
sudo apt install wget
You can easily get to your windows stuff via cd /mnt/c (or d or whichever drive)
adding to the accepted answer: if you’re on windows and don’t find or don’t trust a reasonably new wget, try curl instead. As mentioned here it may already be included in Windows 10.
Источник
Unable to establish SSL connection upon wget on Ubuntu 14.04 LTS
I tried to download an image through wget but I got an error: Unable to establish SSL connection.
Another variable is that the www.website.com uses TLS 1.0. I don’t have an idea how this affects wget. But if I wget an image from TLS 1.2 websites I don’t get any ssl connection errors from both test cases.
Is Ubuntu 14.04 or wget 1.15 not compatible with TLS 1.0 websites? Do I need to install/download any library/software to enable this connection?
4 Answers 4
you must be using old version of wget i had same issue. i was using wget 1.12.so to solve this issue there are 2 way: Update wget or use curl
. right now it happens only to the website I’m testing. I can’t post it here because it’s confidential.
Please note that it might be other causes, but this one is the most probable and without getting access to the site everything is just speculation anyway.
The assumed problem in detail: Usually clients use the most compatible handshake to access a server. This is the SSLv23 handshake which is compatible to older SSL versions but announces the best TLS version the client supports, so that the server can pick the best version. In this case wget would announce TLS1.2. But there are some broken servers which never assumed that one day there would be something like TLS1.2 and which refuse the handshake if the client announces support for this hot new version (from 2008!) instead of just responding with the best version the server supports. To access these broken servers the client has to lie and claim that it only supports TLS1.0 as the best version.
Is Ubuntu 14.04 or wget 1.15 not compatible with TLS 1.0 websites? Do I need to install/download any library/software to enable this connection?
Источник
Windows wget unable to establish ssl connection
Sorry if this has been asked before; I’ve searched but I can’t see the problem discussed (well certainly not in a form I understand!).
I am brand new to Raspberry Pi and am not technical. It was a Christmas present for my 9 year old who is so keen, however we’re running into problems with our first project, which is the Fart Detector in the Resources section. We’ve built the board, but we can’t seem to download the sound which is in the first step, getting the following error:
wget unable to establish ssl connection
I tried the same on the normal home computer and see a play button so I assume there may be something wrong with the Pi settings.
Can anyone help in really plain terms?
Re: wget unable to establish ssl connection
You should see something like
Languages using left-hand whitespace for syntax are ridiculous
The use of crystal balls and mind reading is prohibited.
Re: wget unable to establish ssl connection
Many thanks for your help and happy New Year to you!
do you have any pointers please?
We’ll leave everything set up so can get back onto it quickly this time.
Re: wget unable to establish ssl connection
I don’t know what’s wrong.
Languages using left-hand whitespace for syntax are ridiculous
The use of crystal balls and mind reading is prohibited.
Re: wget unable to establish ssl connection
I am wondering if it is an issue with a poor wi-fi connection in the living room as the web pages seem to take a long time to load on the Pi. I did also wander if it could be our ‘safe search’ settings on our broadband connection but I tried switching these off and it made no difference.
Re: wget unable to establish ssl connection
I am having the same problem with wget (although in a different context). It seems to me that wget and github aren’t playing well together for some reason.
Using curl instead of wget does resolve it for me. This command, as provided by DougieLawson, did work:
Источник
Невозможно установить SSL-соединение при wget в Ubuntu 14.04 LTS
Я попытался загрузить изображение через wget, но получил сообщение об ошибке: не удалось установить SSL-соединение.
Мой тестовый пример:
Другая переменная заключается в том, что сайт www.website.com использует TLS 1.0. Я понятия не имею, как это влияет на wget. Но если я получаю изображение с веб-сайтов TLS 1.2, я не получаю никаких ошибок соединения ssl в обоих тестовых случаях.
Ubuntu 14.04 или wget 1.15 несовместимы с веб-сайтами TLS 1.0? Нужно ли мне устанавливать / загружать какую-либо библиотеку / программное обеспечение, чтобы включить это соединение?
4 ответа
. сейчас это происходит только с веб-сайтом, который я тестирую. Я не могу разместить это здесь, потому что это конфиденциально.
Обратите внимание, что это могут быть другие причины, но эта наиболее вероятна, и без доступа к сайту все в любом случае является лишь предположением.
Подробно предполагаемая проблема: Обычно клиенты используют наиболее совместимое рукопожатие для доступа к серверу. Это рукопожатие SSLv23, которое совместимо со старыми версиями SSL, но объявляет лучшую версию TLS, поддерживаемую клиентом, чтобы сервер мог выбрать лучшую версию. В этом случае wget объявит TLS1.2. Но есть несколько сломанных серверов, которые никогда не предполагали, что однажды будет что-то вроде TLS1.2, и которые отказываются от рукопожатия, если клиент объявляет о поддержке этой горячей новой версии (с 2008 года!), Вместо того, чтобы просто отвечать лучшей версией сервера. поддерживает. Чтобы получить доступ к этим сломанным серверам, клиент должен солгать и заявить, что он поддерживает только TLS1.0 как лучшую версию.
Ubuntu 14.04 или wget 1.15 несовместимы с веб-сайтами TLS 1.0? Нужно ли мне устанавливать / загружать какую-либо библиотеку / программное обеспечение, чтобы включить это соединение?
Проблема в сервере, а не в клиенте. Большинство браузеров обходят эти сломанные серверы, повторяя попытку с более ранней версией. Большинство других приложений не работают безвозвратно, если первая попытка подключения не удалась, то есть они не переходят на более раннюю версию сами по себе, и нужно принудительно применять другую версию с помощью некоторых настроек конкретного приложения.
В некоторых редких случаях ваше системное время может быть рассинхронизировано, что делает сертификаты недействительными.
Это обычная ситуация, если вы работаете в большой корпорации.
Вы должны использовать старую версию wget, у меня была такая же проблема. Я использовал wget 1.12. поэтому для решения этой проблемы есть два способа: Обновите wget или используйте curl
Источник
OpenSSL: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version #93
I received the following error when installing the hdf5 submodule:
To fix this issue, I manually downloaded the hdf5 tar.gz file, but I wanted to alert you to this potential problem. Thank you.
The text was updated successfully, but these errors were encountered:
Work for me on Windows: update git to latest version (2.16) and remove old version ( 1.9)
I have upgraded with latest version (2.16) but still face the same problem. Can you please help me to sort out the issue?
error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
That’s great, thanks for the reply ravisingla. Now I know that the config bit does work (for you). So something is still forcing my git to use tlsv1.
edit: For the record, and to help others maybe, I discovered that the reason my git was ignoring http.sslVersion=tlsv1.2 in config is that this feature was introduced in Git 2.6 and I am on 2.3.5 (the latest built git installer compatible with Mac 10.8 Mountain Lion. I now need to make and compile my own Git using newer source code)
I had a similar problem (OpenSSL: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version) when downing from GitHub using wget. Tried all above, none worked out.
Then I upgrade wget from 1.5 to 1.9, then wget is back to live. I guess the old wget is not compatible with some of the newest dependencies.
Источник
wget https://downloads.sourceforge.net/project/junit/junit/4.10/junit-4.10.jar
SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = c:systemtest_prereqswget-1.11.4-1-bin/etc/wgetrc
—2017-11-02 14:16:37— https://downloads.sourceforge.net/project/junit/junit/4
.10/junit-4.10.jar
Resolving downloads.sourceforge.net… 216.34.181.59
Connecting to downloads.sourceforge.net|216.34.181.59|:443… connected.
ERROR: cannot verify downloads.sourceforge.net’s certificate, issued by /C=US/O=GeoTrust Inc./CN=GeoTrust SSL CA - G3': Unable to locally verify the issuer's authority. To connect to downloads.sourceforge.net insecurely, use —no-check-certificate’
.
Unable to establish SSL connection.
wget https://ci.adoptopenjdk.net/job/jtreg/lastSuccessfulBuild/artifact/jtreg-4.2.0-tip.tar.gz
SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = c:systemtest_prereqswget-1.11.4-1-bin/etc/wgetrc
—2017-10-31 14:42:46— https://ci.adoptopenjdk.net/job/jtreg/lastSuccessfulBuild/artifact/jtreg-4.2.0-tip.tar.gz
Resolving ci.adoptopenjdk.net… 78.47.239.97
Connecting to ci.adoptopenjdk.net|78.47.239.97|:443… connected.
ERROR: cannot verify ci.adoptopenjdk.net’s certificate, issued by /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3': Unable to locally verify the issuer's authority. To connect to ci.adoptopenjdk.net insecurely, use —no-check-certificate’.
Unable to establish SSL connection.
c:gitopenjdk-testsTestConfiglib>tar xf jtreg-4.2.0-tip.tar.gz
‘tar’ is not recognized as an internal or external command,
operable program or batch file.
I know my version of wget is very old, but I can’t get a download to work with it,
# wget https://github.com/radare/radare2/archive/master.zip
--2018-11-05 00:07:51-- https://github.com/radare/radare2/archive/master.zip
Resolving github.com... 192.30.253.112, 192.30.253.113
Connecting to github.com|192.30.253.112|:443... connected.
OpenSSL: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
Unable to establish SSL connection.
# wget --secure-protocol SSLv3 https://github.com/radare/radare2/archive/master.zip
--2018-11-04 23:06:12-- https://github.com/radare/radare2/archive/master.zip
Resolving github.com... 192.30.253.112, 192.30.253.113
Connecting to github.com|192.30.253.112|:443... connected.
OpenSSL: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure
Unable to establish SSL connection.
# wget --secure-protocol SSLv2 https://github.com/radare/radare2/archive/master.zip
--2018-11-04 23:06:14-- https://github.com/radare/radare2/archive/master.zip
Resolving github.com... 192.30.253.113, 192.30.253.112
Connecting to github.com|192.30.253.113|:443... connected.
Unable to establish SSL connection.
# wget --secure-protocol TLSv1 https://github.com/radare/radare2/archive/master.zip
--2018-11-04 23:06:22-- https://github.com/radare/radare2/archive/master.zip
Resolving github.com... 192.30.253.112, 192.30.253.113
Connecting to github.com|192.30.253.112|:443... connected.
OpenSSL: error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
Unable to establish SSL connection.
I’ve tried adding --no-check-certificate but still no dice. Is there anyway to get grab an a .zip with an ancient version of wget on an https server?
In this case, it’s a public tarball. And, I’m working on an iso made to test vulnerabilities (Protostar).
Using Wget 1.12 and OpenSSL 0.9.8 from Debian Squeeze 6.0.3
I am trying to execute :
wget https://app.adroll.com/api/v1/export/all_campaigns_report?advertisable=T4ZPAGYESJEZZMCCBVEMHK&reports=AllCampaignsSummary,AllCampaignsChart,AllAds,AllCampaignsSites&format=csv¤cy=USD
I replaced wget 1.12 with 1.16 on my centos machine.
I have set check-certificate option to off in
vi /etc/wgetrc
I can infact use https usually with wget
wget https://google.com
It doesn’t give ssl error with google.com.
Infact I can access the link on browser just fine. Why does it seem to fail with wget then?
With this command, I get:
[root@warehouse ~]# wget 'https://app.adroll.com/api/v1/export/all_campaigns_report?advertisable=T4ZPAGYESJEZZMCCBVEMHK&reports=AllCampaignsSummary,AllCampaignsChart,AllAds,AllCampaignsSites&format=csv¤cy=USD'
[2] 1487
[3] 1488
[4] 1489
[3] Done reports=AllCampaignsSummary,AllCampaignsChart,AllAds,AllCampaignsSites
[root@warehouse ~]# --2016-10-06 18:27:48-- https://app.adroll.com/api/v1/export/all_campaigns_report?advertisable=T4ZPAGYESJEZZMCCBVEMHK
Resolving app.adroll.com (app.adroll.com)... 52.11.56.178, 52.89.249.63
Connecting to app.adroll.com (app.adroll.com)|52.11.56.178|:443... connected.
Unable to establish SSL connection.
Edit: Tried with single and double quotes as well.Made no difference:
[root@warehouse ~]# wget 'https://app.adroll.com/api/v1/export/all_campaigns_report?advertisable=T4ZPAGYESJEZZMCCBVEMHK&reports=AllCampaignsSummary,AllCampaignsChart,AllAds,AllCampaignsSites&format=csv¤cy=USD'
--2016-10-06 18:32:38-- https://app.adroll.com/api/v1/export/all_campaigns_report?advertisable=T4ZPAGYESJEZZMCCBVEMHK&reports=AllCampaignsSummary,AllCampaignsChart,AllAds,AllCampaignsSites&format=csv¤cy=USD
Resolving app.adroll.com (app.adroll.com)... 52.89.249.63, 52.11.56.178
Connecting to app.adroll.com (app.adroll.com)|52.89.249.63|:443... connected.
Unable to establish SSL connection.
Edit2: Tried with —no-check-certificate as well:
[root@warehouse ~]# wget --no-check-certificate "https://app.adroll.com/api/v1/export/all_campaigns_report?advertisable=T4ZPAGYESJEZZMCCBVEMHK&reports=AllCampaignsSummary,AllCampaignsChart,AllAds,AllCampaignsSites&format=csv¤cy=USD"
--2016-10-06 18:35:23-- https://app.adroll.com/api/v1/export/all_campaigns_report?advertisable=T4ZPAGYESJEZZMCCBVEMHK&reports=AllCampaignsSummary,AllCampaignsChart,AllAds,AllCampaignsSites&format=csv¤cy=USD
Resolving app.adroll.com (app.adroll.com)... 52.11.56.178, 52.89.249.63
Connecting to app.adroll.com (app.adroll.com)|52.11.56.178|:443... connected.
Unable to establish SSL connection.
Edit 3:
using curl -v "https://app.adroll.com/api/v1/export/all_campaigns_report?advertisable=T4ZPAGYESJEZZMCCBVEMHK&reports=AllCampaignsSummary,AllCampaignsChart,AllAds,AllCampaignsSites&format=csv¤cy=USD"
* About to connect() to app.adroll.com port 443 (#0)
* Trying 52.11.56.178... connected
* Connected to app.adroll.com (52.11.56.178) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* NSS error -5938
* Closing connection #0
* SSL connect error
curl: (35) SSL connect error