Curl error 35 #6516
-
Trying to reinstall 2.3.90 and in the so setup.log getting the error messages. [WARNING] (10/10) Could not reach https://repo.saltstack.com/py3/ubuntu/18.04/amd64/archive/3003/SALTSTACK-GPG-KEY.pub, curl error code: 35 [WARNING] (01/10) Could not reach https://packages.wazuh.com/key/GPG-KEY-WAZUH, curl error code: 35 And the preflight fails. This is not an Airgap installation. Doing a network install From what I've read, curl error 35 is a SSL connection issue. There is not a proxy Running curl curl -v https://packages.wazuh.com
Any Ideas |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Hi, Looks like a geo location + cloudfront issue or maybe DNS.
Can you try with different DNS server ? Cheers, |
Beta Was this translation helpful? Give feedback.
-
Looks like something in-between the SO server and the destination is closing the connection. Can you confirm that there are no firewalls or content filtering etc that might be blocking the request? |
Beta Was this translation helpful? Give feedback.
-
Turning off content filer as I write this
Thanks
… On Dec 13, 2021, at 9:05 AM, Josh Brower ***@***.***> wrote:
Looks like something in-between the SO server and the destination is closing the connection.
Can you confirm that there are no firewalls or content filtering etc that might be blocking the request?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#6516 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASRTB36KZQJ23KE4V5SV4RTUQYDT7ANCNFSM5JZXWVDQ>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
Looks like something in-between the SO server and the destination is closing the connection.
Can you confirm that there are no firewalls or content filtering etc that might be blocking the request?