Im running an analytics server that connects to Instgram through the requests library. I'm using proxies and 1 out of 5 of the requests I'm making, I'm getting this error.
I've been looking around the internet and did not find anything that I could understand, any guidance would be much appreciated!
IGBOTDriver: Error in my make_request():
HTTPSConnectionPool(host='i.instagram.com', port=443): Max retries exceeded
with url: /api/v1/users/gameaimon/usernameinfo/
(Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'ssl3_get_record',
'wrong version number')],)",),))
I'm using Ubunto, Apache2 with python 2.7. The script is running on a celery worker in the background.
Related
HTTPSConnectionPool(host='dl.google.com', port=443): Max retries exceeded with url: /dl/cloudsdk/channels/rapid/components-2.json (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', '', 'certificate verify failed')])")))
I have tried both installation i.e. via .exe and .zip facing the same error in both the cases.
I am not sure what certificate it is looking for to validate. Is there something that I missed?
Snapshot of the error
I have a site , and the SSL Certificate works properly when I open it using Chrome.
But when I use requests to get the URL I get the following error
requests.exceptions.SSLError: HTTPSConnectionPool(host='somerandomsite.subdomain.com', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')],)",),))
Any way to have more verbose output on why it fails, or understand whats the issue here?
The certificate has been generated using Let's Encrypt through Google R3
I have configuration as documentation says
exporters:
jaeger:
endpoint: "ipv4:firstHost:14250,secondHost:14250"
balancer_name: "round_robin"
Collector produces error.
How I can configure collector to balance exporter for sending requests in different backends?
info exporterhelper/queued_retry.go:276 Exporting failed. Will retry the request after interval. {"component_kind": "exporter", "component_type": "jaeger", "component_name": "jaeger", "error": "failed to push trace data via Jaeger exporter: rpc error: code = Unavailable desc = last connection error: connection error: desc = "transport: Error while dialing dial tcp: address ipv4:firstHost:14250,secondHost:14250: too many colons in address"", "interval": "30.456378855s"}
It doesn't work in golang grpc client. I used openTelemetry load balancing Another option - use kubernetes to balance requests to backends.
I was doing a rutinary check of my web at GTMETRIX when I get this error message:
Analysis Error An error occurred fetching the page: HTTPS error: SSL
connect attempt failed error:14077410:SSL
routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
There may be a connectivity issue between your server and the GTmetrix
test server. Try testing from another test location or try again
later.
I was looking for answers but can't find any solution. This is the actual status of my SLL configuration:
** Configuring SSL ** testing htaccess rules...
htaccess rules test failed with error: cURL error 35:
error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert
handshake failure checking if .htaccess can or should be edited...
Any help would be appreciated.
My websocket connection fails to connect when connecting through Apache ws tunnel plugin intermittently. The connection always works when hitting the app servers directly.
I see the below errors.
Error during WebSocket handshake: Invalid status line
WebSocket connection to 'ws://host' failed: One or more reserved bits are on: reserved1 = 1, reserved2 = 0, reserved3 = 0
and sometimes
WebSocket connection to 'ws://host' failed: Unrecognized frame opcode: 12
and at times
Error during WebSocket handshake: Status line does not end with CRLF ui-toolkit-vendor.js:21965
Infrastructure
Apache HTTPD 2.4.9 with mod_proxy_wstunnel and mod_proxy_balancer modules
The ws tunnel module ported with 2.4.9 version has several bugs which have been later fixed in the 2.4.12 build. Please find the excerpt from the SVN log.
Revision 1587075 - (view) (download) (annotate) - [select for diffs]
Modified Sun Apr 13 18:41:05 2014 UTC (11 months, 3 weeks ago) by covener
File length: 20119 byte(s)
Diff to previous 1587057 (colored)
several related mod_proxy_wstunnel changes that are tough to pull apart:
make async websockets tunnel opt-in
add config for how long we block a thread in asynch mode
add config for a cap on the synchronous path
avoid sending error responses down the upgraded tunnel