Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Aws IoT / S7-1500 / Mqtt - Certificate Error 80E4

Created by: hugueds at: 5/17/2019 9:13 PM (12 Replies)

Rating (3)

Thanks 4

Result pages:: |; 1 | 2; |

13 Entries

Entries per page: 10 | all

5/17/2019 9:13 PM	Rate (0)
hugueds Regular Member Joined: 4/28/2015 Last visit: 6/30/2022 Posts: 3 Rating: (0)	Hello everyone, I've seen that some users had the same problem, but I didn't find any response if it worked or not, so I decided to create another topic. I'm tryng to use the Mqtt block called LMqtt_Publisher available on https://support.industry.siemens.com/cs/us/en/view/109748872 I'm pretty sure that I'm filling the DB with the correct TCP Params (port, broker, HW_ID) But no matter what I change in certificate manager I keep receiving the Error 80E4 (certificate error) I tried to generate the .p12 file using the xxxx-private.pem.key + xxxx-.pem.crt provided by Aws, exporting to the certificate manager and not worked Observations: - Using Mqtt.fx for windows with the same certificates the communication is OK - What are the correct numbers to put on DB tcpConnParams (from which certificate tab?) 1 "validateSubjectAlternateNameOfServer", 2 "idTlsServerCertificate", 3 "idTlsOwnCertificate" Attachment LMqtt_Publishier_Error.PNG (594 Downloads)
	Last edited by: Jen_Moderator at: 05/20/2019 11:41:27 Optimized link.
Suggestion To thank Quote Answer

5/17/2019 11:33 PM	Rate (0)
0_Einstein Diamond Member Joined: 7/7/2010 Last visit: 11/18/2024 Posts: 15403 Rating: (2446)	Check the *version* of the open communications instructions in the instruction pane. Sometimes I have to really expand the instruction pane to fill about half my screen to see the version column and select the latest version for everything.
	science guy
Suggestion To thank Quote Answer

5/18/2019 4:28 PM	Rate (0)
hugueds Regular Member Joined: 4/28/2015 Last visit: 6/30/2022 Posts: 3 Rating: (0)	Everything was in the latest version

Suggestion To thank Quote Answer

6/20/2019 1:39 AM	Rate (2)
mmckay Bronze Member Joined: 9/21/2006 Last visit: 5/25/2023 Posts: 247 Rating: (65)	I was having a similar problem: getting Certificate Error 80E2 instead of the 80E4 you are seeing. I finally got it working (at least as far as seeing a PLC message arrive in AWS IOT). Things I did: downloaded "thing" certificates from AWS IOT: the Amazon root CA, the ...pem.crt file, and the .key files. Used OpenSSL to put the pem.crt and the private key file into a .P12 file. Imported the root CA and the P12 file into the "trusted and root certificate" store of the TIA Portal project Configured the PLC CPU to use the Amazon root CA as "Certificate of partner devices" Configured the PLC CPU to use the thing certificate (P12) as the "Device certificates" Put the certificate reference numbers into the idTlsServerCertificate (= partner device certificate) and idTlsOwnCertificate (= device certificate) I am using the LMqttqdn variant, so I configured the DNS server for the PLC to be 8.8.8.8 (google) Downloaded everything, did STOP --> RUN, then rising edge on enable of LMqtt_Publisher It took me most of an afternoon fiddling with it until I got it right (or perfected my mouth position), but it is working now. Whether it will stay working is a question for tomorrow.

Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users mschaberle MohamadBasha Stplco

8/21/2019 10:18 AM	Rate (0)
Ỵuki222232311 Advanced Member Joined: 5/14/2018 Last visit: 2/21/2022 Posts: 5 Rating: (0)	Hi mmckey . Can you send me your code. Regards!
	Last edited by: Ỵuki222232311 at: 08/21/2019 10:19:02
Suggestion To thank Quote Answer

9/25/2019 6:49 PM	Rate (1)
mmckay Bronze Member Joined: 9/21/2006 Last visit: 5/25/2023 Posts: 247 Rating: (65)	https://tsuoad.box.com/s/1lp9nw2fx7daexk3yc29faoz9z4sqtyx Uses the older MQTT blocks, but otherwise working for AWS.

Suggestion To thank Quote Answer

5/12/2020 11:03 AM	Rate (0)
rQx Bronze Member Joined: 12/9/2010 Last visit: 9/18/2024 Posts: 162 Rating: (4)	Hi, I'm having trouble getting the rootCA file, how do you get that one from AWS? When I tried to download it, it just gave me a website with numbers /Tim

Suggestion To thank Quote Answer

5/12/2020 11:05 AM	Rate (0)
Kirschiaub08 Gold Member Joined: 4/25/2017 Last visit: 10/11/2024 Posts: 430 Rating: (66)	Hi, Try this way, described in the picture. Attachment AWS_Root.png (460 Downloads)
	Best Regards, Kirschiaub08 Please rate my answers if it was helpful 😊
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users rQx

5/12/2020 12:18 PM	Rate (0)
rQx Bronze Member Joined: 12/9/2010 Last visit: 9/18/2024 Posts: 162 Rating: (4)	To easy... Thanks!

Suggestion To thank Quote Answer

5/13/2020 7:43 AM	Rate (0)
rQx Bronze Member Joined: 12/9/2010 Last visit: 9/18/2024 Posts: 162 Rating: (4)	mmckay https://tsuoad.box.com/s/1lp9nw2fx7daexk3yc29faoz9z4sqtyx Uses the older MQTT blocks, but otherwise working for AWS. Hi, I downloaded your project but it is in V15.1, so I can't open it with V16. Can you maybe update the version?

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on