jackybek

There are additional parameters that needs to be initialised before the connection to mqtt can be successful. You can look for my reply to an earlier question which is similar...

i used .pem extensions and it worked. Never tried .der extensions. Perhaps you can generate the ca certs and server certs using pem extensions.

I think the trustlist is not yet implemented in open62541. Yes, I use OpenSSL to generate my own SSL certs (.pem) and keys. This same cert and key is also...

Open62541 version 1.4.8 OS : Debian bullseye

When creating a PR, it says : PR creation failed. Validation failed: must be a collaborator

Thanks for your suggestion. I will take a look at all the api in include/open62541, as well as the generated headers. Regarding the use of 3rd party opcua client such...

Open62541 version : 1.2.2 OS: raspbian i read from the release notes of 1.2.2 that support for websocket is available in this version. Besides adding the 1 line of code...

I traced the source and realised that UA_parseEndpointUrl() did not cater to wss:// type of endpoint. Hence although the websocket layer is initialised successfully using UA_ServerConfig_addNetworkLayerWS(), the subsequent calls to...

I tried the following changes and now the websocket client from [bami-tech ](https://bami-tech.com/index.html)is able to connect successfully. However, there is still a catch: **UAExpert and open62541 client still not able...

I made the following changes to UA_parseEndpointUrl() to handle new connection string for: 1. mqtt connections : opc.mqtt:// 2. ws connections : ws:// and wss:// It is tested on v1.3-rc1-128-g1bd54abc...