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

Unable to access the target device on the browser through a secure tunnel #601

Closed
zhangzz0413 opened this issue Jul 12, 2023 · 7 comments
Closed
Assignees
Labels
bug This issue is a bug. closing-soon This issue will automatically close in 5 days unless further comments are made. p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 2 days.

Comments

@zhangzz0413
Copy link

Describe the bug

Unable to access the target device from the browser through sample tunnel-notification, click the connect button and keep rotating.

Expected Behavior

Correctly connect to the target device through browser.

Current Behavior

I click the connect button and keep rotating, cannot connect the target device.

Reproduction Steps

My steps as follows:

  1. Create a thing (name: secure_tunnel_demo) and download rootca, certification and private key;
  2. run the tunnel-notification sample:
    $ ./tunnel-notification --endpoint avat5bq0m42tf-ats.iot.us-east-1.amazonaws.com --cert cert.crt --key private.key --thing_name secure_tunnel_demo
  3. Click on the thing name and click to create a secure tunnel, and used quickly set it.
    I can see that the destination connection status is connected, and then click the connection button.;
  4. It is always rotating in circles and cannot be connected;

Possible Solution

No response

Additional Information/Context

No response

SDK version used

1.24.3

Environment details (OS name and version, etc.)

Ubuntu 18.04

@zhangzz0413 zhangzz0413 added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jul 12, 2023
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@zhangzz0413 zhangzz0413 reopened this Jul 31, 2023
@zhangzz0413
Copy link
Author

How should I use the securetunnel feature? Does this sample feel unusable?

@jmklix
Copy link
Member

jmklix commented Jul 31, 2023

You can find out more info about how/why to use a secure tunnel here. Are you running into any problems with the sample? You closed the above issue without any comments.
Are you still running into the same issue that you opened this ticket for?

@jmklix jmklix added response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 2 days. p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. labels Jul 31, 2023
@jmklix jmklix self-assigned this Jul 31, 2023
@zhangzz0413
Copy link
Author

You can find out more info about how/why to use a secure tunnel here. Are you running into any problems with the sample? You closed the above issue without any comments. Are you still running into the same issue that you opened this ticket for?

Hi, jmklix

Thank you for your reply.
I am currently unable to run through the secure tunnel function using the sample in the C++SDK. Can you take a look at the steps I mentioned above to run the sample? Am I missing any steps?

@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 2 days. label Aug 1, 2023
@jmklix jmklix added the investigating This issue is being investigated and/or work is in progress to resolve the issue. label Aug 2, 2023
@jmklix
Copy link
Member

jmklix commented Aug 8, 2023

Are you getting any console output after you create the secure tunnel? Can you also enable logging? I'm able to run the sample and successfully connect.

@jmklix jmklix added response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 2 days. and removed investigating This issue is being investigated and/or work is in progress to resolve the issue. labels Aug 8, 2023
@github-actions
Copy link

Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 5 days unless further comments are made. label Aug 10, 2023
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. closing-soon This issue will automatically close in 5 days unless further comments are made. p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 2 days.
Projects
None yet
Development

No branches or pull requests

2 participants