-
Notifications
You must be signed in to change notification settings - Fork 67
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
Problems using AWS IoT Device Client with Greengrass V2 #465
Comments
Hey @feborja , can you share your setup steps? Just by reading the issue description, I think you might not be setting up the device correctly. Can you share all details and steps to reproduce the issue? |
@HarshGandhi-AWS Of course, so as context this is a device that was created beforehand and contains another components, so it has already been deployed before, I had worked with the client with Greengrass V1 before following the steps in the readme from this repository, but I found that Greengass v2 added this as a component. So the only thing I did was revise the existing deployment, add the component, merge the configuration
I am not sure if this is the information you needed, please let me know |
Just want to make sure, (a) you are using the Greengrass v2 on your device and (b) is your device is not able to connect to secure tunnel in device mode? Is that the case? From the logs you shared it shows the secure tunnel component is running and did not crash. Are you seeing any issues connecting to the end device via secure tunnel?
|
a) Yes, I am using Greengrass V2
After that nothing else happens (when I try to connect it never does, it is loading forever), and if I generate new access tokens, the same thing happens again |
@HarshGandhi-AWS Tried with local proxy with docker, same type of error
|
If you are using the latest version of localproxy to connect to device client can you try passing in |
I get the same error, the localproxy shows:
and my device shows the same logs as before:
I also checked if I the device has port 443 open, which it does:
|
Just like another issue in 2021, I am also trying to enable secure tunnelling in a Device using Greengrass v2, right now I only added the component in the deployment and declared the OS as "raspberry", yet I get errors with the settings with the certificates (Permissions not set to desired value) as well as an error that seems like a placeholder is not edited for the client:
2024-07-12T17:44:05.165Z [WARN] {Config.cpp}: Path replace_with_root_ca_file_location to RootCA is invalid. Ignoring... Will attempt to use default trust store.. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}
The documentation for the component does not specify anything aditional step therefore I am not sure if I am doing something wrong, any help is appreciated.
OS: Raspbian GNU/Linux 11 (bullseye)
Tunnelling component version: 1.0.19
Nucleus Version: 2.12.6
The only configuration merged into the recipe is:
"OS_DIST_INFO": "raspberry"
The text was updated successfully, but these errors were encountered: