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.

Sign up for GitHub

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

Jump to bottom

Explicitly set which IP debugger binds to #205

Closed
DonJayamanne opened this issue Nov 14, 2017 · 2 comments · Fixed by #417
Closed

Explicitly set which IP debugger binds to #205

DonJayamanne opened this issue Nov 14, 2017 · 2 comments · Fixed by #417
Assignees
@DonJayamanne
Labels
area-debugging feature-request Request for new features or functionality
Milestone
January 2018

Comments

@DonJayamanne
Copy link

From @ragerin on October 23, 2017 8:38

Environment data

VS Code version: 1.17.1
Python Extension version: 0.7.0
Python Version: 3.6.2
OS and version: Windows 8.1 Enterprise x64

Actual behavior

When attempting to launch the debug server, I receive the following error:
There was an error in starting the debug server. Error = {"code":"EACCES","errno":"EACCES","syscall":"listen","address":"::"}
I'm behind restrictive corporate Firewall, which I suspect limits the ability to launch the debug server.
I am generally unable to run any servers that binds to 0.0.0.0, but I am able to bind explicitly to 127.0.0.1 without any issue (tested with NodeJS).

Can I somehow configure which IP address (and port) the Python debugger attempts to bind to?

Copied from original issue: DonJayamanne/pythonVSCode#1335
@DonJayamanne
Copy link
Author

Unfortunately there's no option at this stage to configure this.
However you can work around this limitation by using the Attach debugger option.

https://github.com/DonJayamanne/pythonVSCode/wiki/Debugging:-Remote-Debuging

Basically, you're launching the application in debug mode and then attaching to it using a specific IP and port.

Please let me know if that solution works (it should).

@DonJayamanne
Copy link
Author

From @ragerin on October 26, 2017 8:18

Sadly, I get a ECONNREFUSED and experience the same issues as specified in #1039 - tested with ptvsd 3.0.0 and latest 3.2.1.

@brettcannon brettcannon added awaiting 2-PR area-debugging feature-request Request for new features or functionality and removed awaiting 2-PR labels Nov 14, 2017
@brettcannon brettcannon mentioned this issue Nov 14, 2017
Closed
@DonJayamanne DonJayamanne added this to the January 2018 milestone Dec 13, 2017
@DonJayamanne DonJayamanne self-assigned this Dec 13, 2017
@DonJayamanne DonJayamanne mentioned this issue Dec 14, 2017
Merged
DonJayamanne added a commit that referenced this issue Dec 15, 2017
@DonJayamanne
Use localhost instead of 0.0.0.0 for all local socket servers (#417)
68f6626 
Fixes #205 
Fixes #227
* Added ability for users to provide their own ports and host names for the local debug client when debugging
* Added ability for users to provide their own ports and host names for the local debug client when debugging unit tests
* Ensured the default host name for all socket servers is 'localhost'
* Remove some redundant code related to refactor or Jedi (language server that was never completed)
@brettcannon brettcannon mentioned this issue Jan 29, 2018
Closed
38 tasks
@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@DonJayamanne DonJayamanne

Labels
area-debugging feature-request Request for new features or functionality
Projects
None yet
Milestone
January 2018
Development

Successfully merging a pull request may close this issue.

Use localhost instead of 0.0.0.0 for all local socket servers DonJayamanne/pythonVSCode
2 participants
@brettcannon @DonJayamanne