Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BadNoMatch during Startup #811

Closed
ChrisDahmen opened this issue Jul 31, 2024 · 4 comments
Closed

BadNoMatch during Startup #811

ChrisDahmen opened this issue Jul 31, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@ChrisDahmen
Copy link

Describe the bug
I cannot use the Client to connect to the Umati Dashboard, upon attempting to start an exception is shown after which the software immediately closes.

To Reproduce
Unknown since I cannot not replicate the error

Expected behavior
The Application to launch and establish a connection

Environment:

  • OS: Windows 10 running Mosquitto 2.0.18 as my test Broker, WSL with Docker for the client

  • Version Used: Docker Image ghcr.io/umati/dashboard-opcua-client Tag: renovate-docker-setup-buildx-action-3.x (latest for me) and v2.1.0

  • Used Enviroment: Local mosquitto server

  • OPC UA SDK of server: Träger's Opc.UaFx.Advanced Version 2.42.1

Log
logfile.txt

@ChrisDahmen ChrisDahmen added the bug Something isn't working label Jul 31, 2024
@ainglessi
Copy link
Contributor

Hello! The gateway is known to work (with occasional crashes) with a server based on Traeger SDK. Could you please try running the gateway with "Security": 1 in "OpcUa" section of configuration.json and default security settings in the server code with ACL enabled:

opcServer.Security.AnonymousAcl.IsEnabled = false;
var serverAcl = opcServer.Security.UserNameAcl;
serverAcl.AddEntry("xxx", "xxx");
serverAcl.IsEnabled = true;

@ChrisDahmen
Copy link
Author

Hi, I have tried the configuration as given by you, however it still results in the same error. If you need any further files, such as the configuration, to be able to better diagnose the issue please feel free to ask.

@Kantiran91
Copy link
Member

After a test with the old version v2.0.0-rc4 we noticed that some children are missing.

@ChrisDahmen
Copy link
Author

Issue is fixed, now that #816 was found I was able to diagnose the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants