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

MQTT Secure Error 80E4

Created by: Noenoe at: 5/8/2019 6:13 AM (17 Replies)

Rating (1)

Thanks 2

Result pages:: |; 1 | 2; |

18 Entries

Entries per page: 10 | all

5/7/2019 6:13 AM	Rate (0)
Noenoe Posts: 11 Rating: (0)	Hi all, I'm used to connect PLC with mosquitto broker on VPS cloud via 8883 port (secure). But this time, LMqtt FB always throw 80E4 error (No valid CA certificate). I have checked: CPU's time of day is at current time, CA certificate is connected successfully by MQTT.fx), certificate ID in global and local certificate management is correct. What is root cause of this error? Note: My PLC firmware is 2.6 but I download from TIA v15 with firmware 2.5 (because many reason, I don't want reinstall with TIA 15.1 at this time) . I concern that whether it can be a problem of this situation. Additional, my broker only support TLS v1.1 and v1.2, so which TLS version is used in MQTT connection of PLC s7-1500? Is it a problem? Thanks in advance. Best regard, Noenoe
Noenoe Posts: 11 Rating: (0)	Last edited by: Noenoe at: 05/08/2019 06:31:12
Suggestion To thank Quote Answer

5/7/2019 3:43 PM	Rate (1)
Towome Platinum Expert Joined: 7/9/2015 Last visit: 11/12/2024 Posts: 4026 Rating: (602)	Hi, I am not really sure if this information is what you are looking for but in TIA Information System you find information that TCON_IP_V4_SEC is used for requirement X.509-V3-Certificate of TLS Client. Regards, Towome
	If my post was useful, please rate me - if not, please tell me - thank you!
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Noenoe

5/9/2019 5:12 AM	Rate (0)
Noenoe Posts: 11 Rating: (0)	I don't think problem come from broker because I can connect to it by other apps with tls 1.1 and 1.2, When I try to connect with tls 1.0 (by mqttfx or C# app), broker show error "unsupport protocol". But when I connect from PLC, broker just show error: "New connection from <IP> on port 8883. Socket error on client <Unknown?, disconnecting".
Noenoe Posts: 11 Rating: (0)	Last edited by: Noenoe at: 05/09/2019 08:39:48
Suggestion To thank Quote Answer

5/9/2019 8:18 AM	Rate (0)
Noenoe Posts: 11 Rating: (0)	After many checks, I realized that: - Mismatch firmware is not a problem because I can connect to Azure Iot Hub via port 8883. - Proxy is also not a problem because It throw 80E4 error regardless I connect by company network or home network. - Installing new Broker support all TLS versions but error still happen. - Broker CA is x509 v3, and of course, Time of Day, CPU's Time, certificate ID are correct. 80E4 error still happen and I can't find any abnormal. Attached file is some my PLC configurations. Please, Could someone let me know what should i do now to correct it? Thanks a lot. Attachment MQTT_Configure_80E4 error.pdf (624 Downloads)
Noenoe Posts: 11 Rating: (0)	Last edited by: Noenoe at: 05/09/2019 08:47:36 Last edited by: Noenoe at: 05/09/2019 16:27:24
Suggestion To thank Quote Answer

5/10/2019 4:31 AM	Rate (0)
Noenoe Posts: 11 Rating: (0)	Help me please!!!
Noenoe Posts: 11 Rating: (0)
Suggestion To thank Quote Answer

5/10/2019 11:33 AM	Rate (0)
Noenoe Posts: 11 Rating: (0)	After using WireShark to trace TCP package during handshake with PLC, I found that GTM Unix Time send from PLC wrong although I configured Timezone and CPU's time for my PLC (attached file above). So, Why dose PLC send wrong timestamp to server? Attachment handshake.JPG (590 Downloads)
Noenoe Posts: 11 Rating: (0)
Suggestion To thank Quote Answer

1/8/2020 3:17 PM	Rate (0)
Aaron.N Member Joined: 3/22/2019 Last visit: 3/12/2024 Posts: 1 Rating: (0)	Hi Noenoe, Did you track this problem down? I am experiencing the same issues. I have a valid certificate, set the time, checked the domain name etc... Same error 80E4

Suggestion To thank Quote Answer

2/17/2020 11:48 AM	Rate (0)
Gibbo Regular Member Joined: 10/28/2009 Last visit: 5/29/2023 Posts: 5 Rating: (0)	Same problem me too... Any suggestion ?

Suggestion To thank Quote Answer

4/13/2020 8:59 PM	Rate (0)
WoifeSch Member Joined: 7/2/2016 Last visit: 7/5/2024 Posts: 4 Rating: (0)	Same problem considering the timestamp but I am not sure if this is the only issue since in the header in wireshark shows tls version 1.0 while the handshake has version 1.2... For me it is always error 80C4. But I have seen error 80E4 too. I was incredible surprised that there is even a mqtt client in the siemens world. If it is able to use tls as well it would be to good to be true. I would not expect to have a solution from siemens soon. Try searching for a different solution. Use non encrypted communication or use a proxy which translates the non encrypted communication to an encrypted one.

Suggestion To thank Quote Answer

4/14/2020 7:59 AM	Rate (0)
Kirschiaub08 Gold Member Joined: 4/25/2017 Last visit: 10/11/2024 Posts: 430 Rating: (66)	Are you using the latest version? Th application got updated on April 24.
	Best Regards, Kirschiaub08 Please rate my answers if it was helpful 😊
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on