Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Demo OPCUA server configuration issue: Discovery failure and discovered endpoints are missing FQDN
September 13, 2019
2:49, EEST
Avatar
fred
New Member
Members
Forum Posts: 1
Member Since:
September 13, 2019
sp_UserOfflineSmall Offline

Don’t know if this is the best (or valid) place to report this, but figured y’all would want to know…

Demo servers listed on Wikipedia ( https://github.com/node-opcua/node-opcua/wiki/publicly-available-OPC-UA-Servers-and-Clients ). Trying to connect to them:

* opc.tcp://uademo.prosysopc.com:53530/OPCUA/ –> Fails to connect

Unexpected OpcExtConfig Failure for endpoint opc.tcp://uademo.prosysopc.com:53530/OPCUA: io.vantiq.extsrc.opcua.uaOperations.OpcExtConfigException::io.vantiq.extsrc.opcua.uaOperationsOpcuaESClient.discoveryError: Could not discover OPC Endpoints:java.util.concurrent.ExecutionException::UaException: status=Bad_TcpEndpointUrlInvalid, message=Bad_TcpEndpointUrlInvalid (code=0x80830000, description=”The Server does not recognize the QueryString specified.”)

* opc.tcp://uademo.prosysopc.com:53530 –> Discovery returns endpoints of the form opc.tcp://UADEMO:53530/…

These fail to connect since I don’t have a node named UADEMO at this site. Returned endpoints should have fully qualified domain name (FQDN).

io.vantiq.extsrc.opcua.uaOperations.OpcUaESClient – Endpoints discovered via discoveryEndpoint: opc.tcp://uademo.prosysopc.com:53530
Discovered endpoint: opc.tcp://UADEMO:53530 [None, None]). <– This should be opc.tcp://UADEMO.prosysopc.com:53530

Thanks

September 13, 2019
13:01, EEST
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 402
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline

Hi,

I guess. Technically it is sort of an issue with OPC UA in general, but this is technically caused by our UA SDK for Java and currently the application running at the demo is the Simulation Server application.

However that being said, it should now work. Note that the certificate was recreated as part of a workaround (generally the connections in this case are with NONE security mode, but as we always send it to be backwards compatible with UA 1.01 so clients might do validation for it still).

Additionally while it is sort of fixed, a client application generally should still be able to deal with the problem. Technically speaking, the specification mentions in 1.04 Part 12 Discovery Annex A “Firewalls and Discovery”:

Note that Servers may not be aware of all HostNames which can be used to access the
Server (i.e. a NAT firewall) so Clients need to handle the case where the URL used to access
the Server is differen t from the HostNames in the Certificate. This is discussed in more detail
in Part 4.

And additionally in Part 4 section 5.5.2.1 at the end for the Description of OpenSecureChannel service:

Clients should be prepared to replace the HostName returned in the EndpointDescription with the
HostName or the IP addresses they used to call GetEndpoints.

For these reason sometimes the endpointUrl might needed to be ignored or do the replacing and just continue trying to open a session by via the original connection url, but passing one of the discovered EndpointUrls within the CreateSessionRequest. For this reason this hasn’t been that big of a problem.

P.S. The server might be offline for a second time (+ a second cert change) later today as we’ll do some version upgrades. The address space might slightly change as well.

September 24, 2019
14:17, EEST
Avatar
Viral
New Member
Members
Forum Posts: 1
Member Since:
September 24, 2019
sp_UserOfflineSmall Offline

Hi,

I have installed Prosys OPC UA simulation server after running it for the first time I was able to view Connection Address (both UA TCP & HTTPS)
But after when I restarted the OPC UA Simulation Server I am not able to view any Connection Address it is showing no endpoint configured for this TCP connection, while both the endpoint configuration settings are enabled.
Please need help on this.

Thanks,
Viral.

September 26, 2019
14:02, EEST
Avatar
aku
New Member
Members
Forum Posts: 1
Member Since:
June 3, 2019
sp_UserOfflineSmall Offline

Viral said
Hi,

I have installed Prosys OPC UA simulation server after running it for the first time I was able to view Connection Address (both UA TCP & HTTPS)
But after when I restarted the OPC UA Simulation Server I am not able to view any Connection Address it is showing no endpoint configured for this TCP connection, while both the endpoint configuration settings are enabled.
Please need help on this.

Thanks,
Viral.  

Hello,

Creating a separate thread is advised for separate issues.

Could you provide screenshots of “Status” and “Endpoints” tabs to our support address: uajava-support@prosysopc.com

Aku

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 78

Currently Online:
10 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 91

pramanj: 86

ibrahim: 68

kapsl: 57

gjevremovic: 49

TimK: 41

Fransua33: 39

fred: 36

Rainer Versteeg: 32

peterrob45: 25

Member Stats:

Guest Posters: 0

Members: 880

Moderators: 12

Admins: 1

Forum Stats:

Groups: 3

Forums: 14

Topics: 892

Posts: 3744

Newest Members:

Fervic1991, ivfa, tplbev1272761848, vinwin, ancyss, dj, Thomas, Viral, nedumarans, Dhruvil Dhanani

Moderators: Jouni Aro: 833, Otso Palonen: 32, Tuomas Hiltunen: 5, janimakela: 0, Pyry: 1, Terho: 0, Petri: 0, Bjarne Boström: 402, Heikki Tahvanainen: 402, Jukka Asikainen: 1, Teppo Uimonen: 16, Markus Johansson: 1

Administrators: admin: 0