Connect problem with HTTP and HTTPS endpoint channel

[Arumugam]

Hello,

I am unable to connect my server using the http or https secure channel.

When I try to query the endpoint descriptions for my server. I will get below endpoints
1. http://localhost:8526/ModbusRTUFDICommunicationServer
2. http://localhost:8526/ModbusRTUFDICommu ... erver/None
3. http://localhost:8526/ModbusRTUFDICommu ... c256sha256

1. When I try to connect using the "http://localhost:8526/ModbusRTUFDICommunicationServer" endpoint, I am getting the below error message
"MaxCallDepth at ServiceDiagnostics. 0 < 1".

2. When I try to connect using the "http://localhost:8526/ModbusRTUFDICommu ... c256sha256" endpoint, I am getting the below error exception
"The message could not be processed. This is most likely because the action 'http://opcfoundation.org/UA/2008/02/Ser ... okeService' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding."

3. When I try to connect using the "https://localhost:888/ModbusRTUFDICommunicationServer" endpoint, It is not connecting instead it will show Operation Timeout error message"

I am not able to identify where I did a mistake. Could you guys suggest me the what was the problem here?

Note: My client is developed using same UnifiedAutomation.Client.

Best Regards,
Arumugam

[Support Team]

Hello,

the HTTP and HTTPS endpoints are disabled in all our OPC UA SDKs for a reason. They are unsupported and marked as experimental for good cause. It is not recommended to switch those endpoints on nor to use them. The http/SOAP/XML with WS* secure conversation is already deprecated by the OPC Foundation. The hybrid https/UaBinary still exists, but can only be used in very controled environment due to resource constraints in parallel operations.

The only recomended (and supported) transport is UA-TCP with Binary encoding. It is the mandatory, default in all our products and it was compliance tested.

However the issue you are reporting can not be reproduced by us. Please be more precise on the version and the exact SDK you are using on both sides?

Best Regards
Support Team

[s.meadow]

Hello Support Team,

could you tell me please where do you got that information and name the source?

Thanks.

Best Regards