-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Spyder 5.0.4 crashes with proxy error to kite.com #15876
Comments
Hi @gvizkelethy, This error is happening at the startup or did you ran something? Also, how are you upgrading Spyder? |
This happens when I start Spyder from a terminal window. It does not matter if I start in the foreground or the background. I upgraded Spyder with pip, I do not have the anaconda environment. |
I get a similar error with 5.0.4 where it fails to launch if I am not connected to the internet. Connected it works. |
I am connected to the internet but through a firewall. The proxy settings work for everything, even for pip except for Spyder. It looks like it is trying to connect to the wrong proxy. Is there a way to check what proxy it is trying to connect? And why does Spyder need an internet connection? Can I turn it off? |
@gvizkelethy, how did you set your proxy settings so that pip can use them? Are you using environment variables for that? |
Yes, I am using environment variables: |
Ok, thanks for the confirmation @gvizkelethy. We'll fix this problem and release 5.0.5 right away. |
According to the requests documentation, the variables set by @gvizkelethy should work as expected, as requests is already picking them. In this case, the error is related to the proxy communication and not with Spyder, we should introduce a Try/Except block to prevent these kind of errors. |
I can verify that this also occurs when self-signed certificates are used... 2021-06-21 12:52:35,915 [WARNING] [spyder.plugins.completion.plugin] -> Failed to load completion provider from entry point kite = spyder.plugins.completion.providers.kite.provider:KiteProvider
Traceback (most recent call last):
File "urllib3/connectionpool.pyc", line 699, in urlopen
File "urllib3/connectionpool.pyc", line 382, in _make_request
File "urllib3/connectionpool.pyc", line 1010, in _validate_conn
File "urllib3/connection.pyc", line 411, in connect
File "urllib3/util/ssl_.pyc", line 449, in ssl_wrap_socket
File "urllib3/util/ssl_.pyc", line 493, in _ssl_wrap_socket_impl
File "ssl.pyc", line 500, in wrap_socket
File "ssl.pyc", line 1040, in _create
File "ssl.pyc", line 1309, in do_handshake
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1129) The self-signed certificate issue is not technically a Spyder problem (we have these issues constantly at my company), but I agree with @andfoy that a try/except block should be used. |
Issue Report Checklist
conda update spyder
(orpip
, if not using Anaconda)jupyter qtconsole
(if console-related)spyder --reset
Problem Description
Spyder 5.0.4 crashes with proxy error to kite.com and "internal console not found.
What steps reproduce the problem?
What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)
Versions
Dependencies
The text was updated successfully, but these errors were encountered: