I've tried to establish a connection by both command line and in my C++ project.
In a "secure" version I received:
OpenSSL error: 336130315:SSL routines:SSL3_GET_RECORD:wrong version number
If I try with an insecure connection, I received:
connection to 'neo4j://localhost:7474' failed: Could not agree on a protocol version
but I successfully access to the db via browser on the same port number.
How could I repair?
An insecure connection is good for me.
Related
I have ocserv setup on a vm, but when trying to connect through openconnect app getting these errors,
it will be helpful if any solution, tried various ocserv config file modifications but non-sucessfull
Logs:
` Disconnected
STAT: attempt=O; first-NEVER; prev=NEVER
STAT: connect=o; first-NE-VER; prev=NEVER
STAT: cancel=o; first=NEVER; prev=NEVER
LIB: POST https://<IP/hostname>/
L1B: Attempting to connect to server <IP/hostname>
LIB: Connected to <IP :443/hostname>
LIB: SSL negotiation with <IP/hostname>
L1B: Server certificate verify failed: certificate does not match hostname CALLBACK: onValidatePeerCert
LIB: SSI- connection failure: The operation timed out
LIB: Failed to open HTTPS connection to <IP/hostname>
Error obtaining cookie
VPN terminated with errors`
Update::: after few changes this is the current error im getting,
setup description: Vm has debian 9 installed with ocserv installed, also certificates. trying to connect useing openconnect android app, device has mobile data enabled with low speed.
Log:
Disconnected
STAT: attempt=O; first-NEVER; prev=NEVER
STAT: connect=o; first-NE-VER; prev=NEVER
STAT: cancel=o; first=NEVER; prev=NEVER
LIB: POST https://<IP/hostname>/
L1B: Attempting to connect to server <IP/hostname>
LIB: Connected to <IP :443/hostname>
L1B: SSL_negotiation with <IP/hostname>
L1B: SSL_connection failure: The operation timed out
L1B: Failed to open HTTPS connection to <IP/hostname>
Error obtaining cookie
VPN terminated with errors
Is their any SSL issue? or do I need to give 3rd party SSL to ocserv, if so how to install 3rd party SSL to ocserv.
Thanks in advance
The error message states that the server's certificate did not match its hostname. As your client checks this, you need to use a certificate that matches the hostname that you use to access the server.
I am following these instructions to deploy a Django app on Google App Engine:
https://cloud.google.com/python/django/appengine
I have got as far as downloading the proxy .exe file (I am on a Windows machine) and connecting to it:
2019/01/08 16:14:08 Listening on 127.0.0.1:3306 for
[INSTANCE-NAME] 2019/01/08 16:14:08
Ready for new connections
When I try and create the Django migrations by running python manage.py createmigrations I see the connection received by the proxy file:
2019/01/08 16:15:06 New connection for
"[INSTANCE-NAME]"
However, after a couple of seconds pause I get this error:
2019/01/08 16:15:28 couldn't connect to
"[INSTANCE-NAME]": dial tcp
35.205.185.133:3307: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
I have tried disabling my local firewall in case this was causing any issues, but the result is the same. I've also checked the username, password and Cloud SQL instance name, they are all correct.
What could be causing this error?
I was trying to code a simple server client program in python and when i ran the server using python3 and tried to have the client connect to it using python2, it would throw an error:
TimeoutError: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
however, when i ran the same short program on the same computer using python2 and python3, it would connect. The 2 separate computers would only connect if they were using the same version of python. Is there a reason for this and a way around this?
#client
s=socket.socket()
s.connect(('ip, port))
#server
s=socket()
s.bind(('', port))
s.listen(4)
c, addr = s.accept()
Your Windows software firewall has python.exe marked as allowed but not python3.exe.
We are running "helloworld" example from https://grpc.io/docs/quickstart/cpp.html#update-a-grpc-service and we received the following ERROR:
14: Connect Failed
Greeter received: RPC failed.
The server and the client are listening on: 0.0.0.0:50051. The Server is running.
First we receive just a packet on the server and the client crashes, I checked it with tcpdump. We checked on different hosts as well as on the same host but it didn't work for either cases.
Should we change a different IP or different Port number?
I got the same issue on my PC(OS: ubuntu 16.04 LTS, protobuf 3.4.0)
so I search for the reason and I found this:
Reason
If on a linux machine, the environment has the usual "http_proxy" environment variable configured, gRPC will take that into account when trying to connect, however, will then proceed to ignore the companion no_proxy setting:
For example:
$ env
http_proxy=http://106.1.216.121:8080
no_proxy=localhost,127.0.0.1
$ ./greeter_client
D0306 16:00:11.419586349 1897 combiner.c:351] C:0x25a9290 finish old_state=3
D0306 16:00:11.420527744 1896 tcp_client_posix.c:179] CLIENT_CONNECT: ipv4:106.1.216.121:8080: on_writable: error="No Error"
D0306 16:00:11.420567382 1896 combiner.c:145] C:0x25a69a0 create
D0306 16:00:11.420581887 1896 tcp_client_posix.c:119] CLIENT_CONNECT: ipv4:106.1.216.121:8080: on_alarm: error="Cancelled"
I0306 16:00:11.420617663 1896 http_connect_handshaker.c:319] Connecting to server 127.0.0.1:50051 via HTTP proxy ipv4:106.1.216.121:8080
Basically, it's using the http_proxy url to connect even though localhost is in the no_proxy list. Since the default for no_proxy includes localhost on most linux machines; the end result is that any user with an http_proxy configured will never be able to connect to localhost. --- [1]
Other solution
You can enable grpc tracing with
export GRPC_TRACE=all && ./greeter_server and same thing for the client.
Verification
Terminal 1
Terminal 2
That should do the trick
ps. for more information about GRPC_TRACE - gRPC environment variables
Reference
gRPC doesn't respect the no_proxy environment variable
I'm trying to use remote debugging but get this error on pycharm:
Error running remoteTest:
failed to find free socket
My remote host is Ubuntu |(with username and password) and my localhost is windows, I followed the following tutorial:
https://blog.jetbrains.com/pycharm/2010/12/python-remote-debug-with-pycharm/
and I used a ssh tunnel on putty to connect to the server.
import pydevd
pydevd.settrace('localhost', port=21000, stdoutToServer=True, stderrToServer=True)