Max Retries Exceeded and SSL Errors - geopy

I'm looking for some assistance in resolving this error.
geopy.exc.GeocoderUnavailable: HTTPSConnectionPool(host='nominatim.openstreetmap.org', port=443): Max retries exceeded with url: /search?q=ADDRESS&format=json&limit=1 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1108)')))
I've already tried installing certifi. I've tried adding time out restrictions. I tried to install ssl, but I'm receiving an error for that indicating that there is no matching distribution found for ssl. I've tried to connect to the Nominatim geocoder using two computers with the same error. Any thoughts on how to resolve? I've only tried to query 5-6 times, so I would guess that would be within limits of reasonable tries. Any thoughts appreciated.

Related

Increase in the number of connections gives 504 gateway timeout error in Nginx

I have a mail server running nginx. Whenever the number of connections increase, nginx fails and give Upstream connection error in the error.log. On the browser, it gives 504 Timeout error. How can I resolve this?
I have checked the resources that are being used by my server. They are in the optimal state. Still, I am facing this issue.

Jmeter- Nginx-Non HTTP response code: org.apache.http.conn.HttpHostConnectException/Non HTTP response message: Connection timed out: connect

Im executing a load testing using Jmeter. Sometimes I get the error "Non HTTP response code: org.apache.http.conn.HttpHostConnectException/Non HTTP response message: Connect to example.com failed: Connection timed out: connect" even for 100 users. But sometimes it passes 5000 users without any errors. Im unable to find out where exactly is the issue, if its on Nginx webserver or at the network end.
In the nginx configuration, I have added keepalive, keepalive_requests, keepalive_timeout in the upstream module part. Kindly help me with a solution on how to fix this issue and any suggestions to optimize the server configuration.

How to handle "Failed to establish a new connection" error in python requests

I wrote a python script with requests to send requests a list of domains, I use
try
requests.get('http://example.com')
except requests.exceptions.RequestException as e:
pass
to handle exceptions such as timeout, or too many redirections, as described in Correct way to try/except using Python requests module?.
However, there is an issues that some sites support only http scheme, while others support only https. In other words, if I send request to http://example.com, it does not redirect to https://example.com. Because of this, requests gives "failed to establish a new connection" error, complain that http://example.cm does not exist and terminates the program.
I wonder if there is a way to let me bypass such error, and continue to send request to the next host.

improbable-eng/grpc-web Response closed without headers

I have a server in go using gRPC and on the react client I'm using grpc web with grpcwebproxy and I've been trying to connect my client to the server but constantly get error Code 2, with the message: Response closed without headers. Has anybody else encountered this issue? I'm currently using improbable-eng implementation of grpc-web.
You probably need to configure grpcwebproxy for CORS, see this docs.
grpcwebproxy: might have read/write timeout and close your longPolling connection by timeout. Relevant for all client-server streaming calls.
server_http_max_read_timeout – HTTP server config, max read duration (default 10s).
server_http_max_write_timeout – HTTP server config, max write duration (default 10s).

client closed connection in nginx error log

I am using openresty with redis for a project.
I am getting these messages in nginx error.log.
2016/07/13 23:08:05 [info] 28306#0: *110027 client closed connection while waiting for request, client: 27.97.70.20, server: 0.0.0.0:80
Total number of connects opened and count of this message is almost same. I see that lots of people see this message on different context, and see varying responses on different places.
How should I proceed? Is this issue serious?

Resources