Alternative node for OPC UA Compact Server

General
1

Hi,

I was using ' OPC UA Compact Server' in one of my Project, this project was handover two year ago.

Recently i was trying update OS of the image and stared updating my node-red application to it's latest nodes and flows, and looks like the 'OPC UA Compact Server' is no longer upgradable due o security concerns.

image
image509Ă—619 25.1 KB

also, tried to install node-red-contrib-opcua-server-refresh 0.1.6 and it wasn't successful due to the security issues and it's been discontinued

2025-06-10T15:02:45.777Z Install : node-red-contrib-opcua-server-refresh 0.1.6

2025-06-10T15:02:47.560Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict node-red-contrib-opcua-server-refresh@0.1.6
2025-06-10T15:03:17.999Z [err] npm
2025-06-10T15:03:18.000Z [err]  WARN deprecated vm2@3.9.19: The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm.
2025-06-10T15:03:34.419Z [err] npm
2025-06-10T15:03:34.420Z [err]  ERR! code 1

Is there any other node / flows which i could use instead of 'OPC UA Compact Server' develop and test ?

Your inputs highly appreciated.

Regards,
Mani

2

The discontinued notification is about a dependency (vm2) not the node-red-contrib-opcua-server-refresh node which was updated 2 months ago (it is not depreciated)

I have contacted @Hisma to see if it is something he would kindly look into.

3

You could try the newer node-red-opcua-x (node) - Node-RED it appears to have a node named opcua-server - though i have not tested it.

4

Hi @Steve-Mcl ,

Thanks for your quick response.

I did try to update the actual node'node-red-contrib-opcua-server' but got this below error messages.

I believe it's no longer supported due to security concern , the last update was nearly 3 yrs back.
that's a reason tried for the node-red-contrib-opcua-server-refresh got into the same issue.

2025-06-10T15:35:48.897Z Install : node-red-contrib-opcua-server 1.1.1

2025-06-10T15:35:50.641Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict node-red-contrib-opcua-server@1.1.1
2025-06-10T15:36:25.261Z [err] npm
2025-06-10T15:36:25.262Z [err]  WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
2025-06-10T15:36:25.833Z [err] npm
2025-06-10T15:36:25.834Z [err]  WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
2025-06-10T15:36:26.152Z [err] npm
2025-06-10T15:36:26.153Z [err]  WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
2025-06-10T15:36:28.140Z [err] npm
2025-06-10T15:36:28.141Z [err]  WARN deprecated vm2@3.9.19: The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm.
2025-06-10T15:36:42.435Z [err] npm
2025-06-10T15:36:42.436Z [err]  ERR! code 1
2025-06-10T15:36:42.436Z [err] npm ERR! path /var/lib/revpi-nodered/.node-red/node_modules/node-red-contrib-opcua-server
2025-06-10T15:36:42.451Z [err] npm
2025-06-10T15:36:42.453Z [err]  ERR! command failed

I have used quite a lot of logic structed code inside the 'address space' of this outdated opc ua compact server.

Thanks for the hit to use ' node-red-opcua-x' i will explored this option,

Also if possible any sample code to use 'OPCua-server' node with more variables would be highly appreciated.

image
image491Ă—718 27.6 KB

@Hisma : Can you please guide me to update the application with the latest opc ua server ?

Regards,
Mani

5

Hey guys,

Thanks for the update. I did a dependency update a couple months ago, as @Steve-Mcl mentioned. I do recall getting warnings that vm2 was going to be deprecated and figured we'd eventually arrive here. But since this was a fork, I didn't want to completely refactor the code, and vm2 unfortunately handles some of the core node functionality, and the module it suggests to update is not backwards compatible with vm2. That said, let me revisit it and see if I can update it. I'll check this weekend.

2 Likes
6

Hi @Hisma ,

Thanks for taking a look over the upcoming weekend.
I’m looking forward to the update once it’s ready.

Best Regards,
Mani

7

Hi mister, good to speak again, its been a while - I hope you are well.

I wonder if you would also switch on issues for node-red-contrib-opcua-server-refresh so good folk can raise issues for your repo?

FYI

Issues are disabled by default in forked repositories. However, you can enable them by following these steps:

  1. Navigate to the Settings page of your forked repository.
  2. Click on the General tab on the left-hand side.
  3. Scroll down to the Features subsection.
  4. Check the box for Issues to enable them.
1 Like