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

No associated proxy found in cache. Terminating connection #1

Closed
Uri-Katsir opened this issue Sep 19, 2017 · 2 comments
Closed

No associated proxy found in cache. Terminating connection #1

Uri-Katsir opened this issue Sep 19, 2017 · 2 comments
Assignees
Labels

Comments

@Uri-Katsir
Copy link

Hello,

Configured the debugger but when running in Chrome, I see the following error.

image

@azurelogic azurelogic self-assigned this Sep 19, 2017
@azurelogic
Copy link
Contributor

Hi @Uri-Katsir,

It looks like you are trying to connect without having run a correctly configured Lambda function first. Just like any other debugger attachment, the target process needs to be running first in order to connect.

Things to check:

  • Did you install the npm package and put require('aws-lambda-debugger') at the end of the file containing the handler you wish to debug?
  • Did you add the required environment variables?
  • Did you execute the Lambda function before attempting to attach the debugger? (note: You will see a log message when the Lambda proxy connects to the broker)

Relevant documentation: "Use it!"

Let me know if this helps resolve your issue. Also, if that helps, feel free to give some feedback on how we can improve the docs if needed.

Thanks!

@Uri-Katsir
Copy link
Author

Hi @azurelogic,
Thanks for your reply, it is working as described.
The reasons it was not working for me were:

  1. I left the "DEBUGGER_ACTIVE" variable empty.
  2. I did not execute the Lambda function before attempting to attach the debugger.

Thank you

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