-
Notifications
You must be signed in to change notification settings - Fork 298
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
405 Method not allowed connecting to a remote server #2238
Comments
Hey @clayms . Thanks for reporting this. microsoft/vscode-python#6309 was only closed as we didn't get solid repro information back on that to investigate. Question, could you please get the info from the "Console" section of Help->Toggle Developer Tools when you try to connect. That has our detail output and would be the first think that I would look at to help diagnose this. |
Thanks @IanMatthewHuff . Only Warnings and Errors pasted below.
|
@IanMatthewHuff Did you need any additional information? |
@clayms So the tricky bit here is that I don't really have an easy way to reproduce this myself. I don't have the same AWS setup available to me, and as you noted you were seeing it on your EMR cluster and not your other AWS cluster. My AWS knowledge is quite low, but I believe that it's going to be some of the EMR security rules from here: From the log, the error is coming from when we start up a new session. (If you are interested here is the location): For our connections to servers and operations on them we use the jupyterlab services. Given the source location and the error it looks like it's the call to the newUntitled function of the content manager here: So it looks like the service connection is trying to do a POST to this url: http://...:8889/lab/api/contents/?1582691793239 and the server is not allowing it. I'm not sure how that's configured though on your servers end. |
Same error here. I'm successful with Atom-Hydrogen but I've to use cert-tweaks to enable adding extra certificates to Atom's trust store I was able to solve my 405 error thank to this answer |
@jacquespeeters How did you create your self-signed certificate? I followed these instructions from IBM, then added the certificate to Chrome following the instructions you linked to. From the EMR master node: # create key and cert
openssl req -newkey rsa:2048 -nodes -keyout key.pem -x509 -days 365 -out certificate.pem
# combine key and cert
openssl pkcs12 -inkey key.pem -in certificate.pem -export -out certificate.p12 Downloading Same error. Should I create either the Thanks, |
Solved it. The newer versions of Jupyter start what appears to be something like the Terminal based No matter which Terminal shell I choose, the output is extremely chaotic after I launch Jupyter, in that the 'documents' that the terminal browser is viewing is intermixed with the output of the Jupyter server. Through all of that noise, I can use the arrow keys to somehow 'navigate' to a point where the following occurs somewhere in the terminal intermixed with the Jupyter output (usually highlighted, but depends on which Terminal program):
I type A and press enter Sometimes, and sometimes not, I will see the following in the Terminal for a short time:
Then I can press q and get out of whatever terminal browser thing Jupyter launched and just see the normal Jupyter server output. Copy the full url to the Jupyter server, paste it into VS Code Python extension Everything seems to be working after that. No certificates or keys needed. |
Issue Type: Bug
I am getting the following error when connecting to Jupyter running on a remote server.
However, the link given in the Terminal when launching Jupyter Labs, works and I can run python and pyspark code with no issue.
I use the Python VS Code extension to run PySpark jobs on a AWS cluster of EC2 instances running Cloudera CDH with no issue. I simply start the Jupyter server on the Master node and paste the link into the
mywork.code-workspace
file. For example:Now I am trying to do the same thing from the Master node of an EMR cluster, which is still just a cluster of EC2 instances. Again, the exact same Jupyter Labs server on the same port works without any issue from a browser, but I cannot get it to work in the Python extension for VS Code.
Related reported issues:
Extension version: 2020.2.64397
VS Code version: Code 1.42.1 (c47d83b293181d9be64f27ff093689e8e7aed054, 2020-02-11T14:45:59.656Z)
OS version: Windows_NT x64 10.0.17763
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: