Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RTCClient 0.7 Fails to Connect to RTC server v6.0.6.1 #142

Open
shott92 opened this issue Jun 17, 2021 · 7 comments
Open

RTCClient 0.7 Fails to Connect to RTC server v6.0.6.1 #142

shott92 opened this issue Jun 17, 2021 · 7 comments
Labels

Comments

@shott92
Copy link

shott92 commented Jun 17, 2021

I am having issues connecting to our RTC Server v6.0.6.1 via the RTCClient v0.7.0, URL ends in ccm. (or on homepage jts)

I have tried changing the URL to end with both jazz and ccm, (both with the "Ends_with_Jazz" flag set to FALSE.)

Further I have tried to enable forwarding as per issue #93 by setting _allow_redirects=True on line 84 of client.py

Error message when using port 9443:
RTCClient_FailsToConnect.txt

@dixudx
Copy link
Owner

dixudx commented Jun 17, 2021

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

This basically means that no response (either positive or negative) was received from the remote host when the TCP connection attempt took place.

One reason this may happen is because a firewall is blocking the response from the server. Another reason is that the host name is incorrect.

This could also mean there is a (temporary) problem with the server (or some router along the way). You can try a traceroute to determine whether or not this is true.

@shott92
Copy link
Author

shott92 commented Jun 17, 2021

tracert completes successfully in 13 hops, using the hostname to connect to the server.
I assume this leaves firewall/proxy as a possible issue? I'm not sure I'd be able to manage firewall or proxy settings, but is there a way to confirm if this is the cause?

@dixudx
Copy link
Owner

dixudx commented Jun 17, 2021

Try to curl your server, such as curl https://xyz.com:9443/ccm and see what happened.

@shott92
Copy link
Author

shott92 commented Jun 17, 2021

I attempted to curl the server but fail on both ports 9443 and 443, same result as 443 when no port was specified.

~curl-7.77.0-win64-mingw\bin\curl.exe https://www.xzy.com:9443
curl: (28) Failed to connect to www.pd-dv.jlrint.com port 9443: Timed out

~curl-7.77.0-win64-mingw\bin\curl.exe https://www.xzy.com:443
curl: (60) SSL certificate problem: self signed certificate in certificate chain

More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above.

I've exported the relevant certificate for the URL/Server - is there a way to include the certificate in the requests from the RTCClient please?

Edit: I rather crudely modified base.py, so that all "Verify=False", and "Verify=verify", was replaced with "verify="path_to_cert.pem"
This didn't affect the result

@dixudx
Copy link
Owner

dixudx commented Jun 18, 2021

Actually verify=False has already been set, so there is no need to include a CA for checking.

Please check the port and server url. And also please check if you're using a VPN.

@shott92
Copy link
Author

shott92 commented Jun 18, 2021

yes, I am using a VPN

@dixudx
Copy link
Owner

dixudx commented Jun 18, 2021

yes, I am using a VPN

Then you need to specify proxies in your codes, such as,

proxies = {
  'http': 'http://10.10.1.10:3128',
  'https': 'http://10.10.1.10:1080',
}
myclient = RTCClient(url, username, password, ends_with_jazz=True, proxies=proxies)

We use requests as the http lib, refer to requests proxies for more details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants