1 Answer
- Newest
- Most votes
- Most comments
1
Hello, The problem that you are having is that you changed the greengrassDataPlanePort, while that is necessary in your case, it isn't not the only change you need to make. You must also change the MQTT port which is used. Please see our documentation here for how to configure MQTT to use port 443. https://docs.aws.amazon.com/greengrass/v2/developerguide/configure-greengrass-core-v2.html#configure-alpn-network-proxy
Relevant content
- asked a month ago
- asked 2 months ago
- Accepted Answerasked a year ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
Thank you so much Michael. One more question if you do not mind. Is there anyway to change it locally without connecting to online?
In the same way you set the dataplane port, you may create a configuration file which contains the necessary configuration underneath the aws.greengrass.Nucleus key.
You can also have a look at our manual installation instructions which have a bit more information about creating a local config file and using that. https://docs.aws.amazon.com/greengrass/v2/developerguide/manual-installation.html#:~:text=in%20an%20HSM.-,Install%20the%20AWS%20IoT%20Greengrass%20Core%20software%20with%20private%20key%20and%20certificate%20files,-Install%20the%20AWS
It is working now after i changed both mqtt and greengrassDataPlanePort to 443. Thank you so much Michael.