Hi all, I work with McKinsey and we use UMH to con...
# umh-supportq
qjunior12
04/01/2024, 6:11 PMHi all, I work with McKinsey and we use UMH to connect our compressor line to Proxmox and NodeRed. We have digital manufacturing workshops to display i4.0 solutions. Currently I am having a problem connecting to NodeRed. I assumed it was a broken Ethernet cable that was prevent internet access to the line, but it seems as there are two problems. The Ethernet cables that provided connections to NodeRed are no longer providing that connection, and the IPv4 connection does not allow us to view the NodeRed interface. I was wondering if I could get some external assistance with this issue since we have workshops coming up this week.
j
Jermuk
04/02/2024, 9:45 AMCreating a thread to prevent spamming everything 🙂
Jermuk
04/02/2024, 9:46 AMUnfortunately, we don't have the passwords anymore. Maybe you can try Hector?
Jermuk
04/02/2024, 9:46 AM> The Ethernet cables that provided connections to NodeRed are no longer providing that connection
What do you mean by that? I remember we labeled every cable. Are you saying someone removed those cables?
Jermuk
04/02/2024, 9:47 AMI think the best way to get started is to log into proxmox and see if there are any VM issues
Jermuk
04/02/2024, 9:50 AMOnce you are in Proxmox, you should verify that the two other VMs are still running:
1. OPNsense
2. flatcar or k3os (this is where the UMH is running on)
q
qjunior12
04/02/2024, 5:51 PMWe are not able to login into Proxmox
qjunior12
04/02/2024, 5:51 PMCan you guide us, how we can log into it
j
Jermuk
04/02/2024, 6:11 PMAre you able to get to the login screen?
Jermuk
04/02/2024, 6:11 PMif yes, enter the credentials. if not, then it will get really complicated
q
qjunior12
04/02/2024, 7:03 PMWe cannot see the login screen. Is there a way we can hop on a call to discuss?
qjunior12
04/02/2024, 9:29 PMWe have continued our troubleshooting process today. We still were not able to access Proxmox, and we will need assistance from UMH. We were able to access Node Red, and needed assistance getting the nodes to go from “connecting to connected”. Lastly, we cannot access Mqtt explorer and need help to view the data transferred on our line.
qjunior12
04/02/2024, 9:30 PMHere are some details provided from Node Red: “Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.”
j
Jermuk
04/03/2024, 7:26 AMMy hypothesis is that Proxmox and OPNSense are still running, but something inside the flatcar VM went wrong. You could also SSH into it, and re-install it (ensure you disable the historian because you don't need it, and setup the databridge to point ot your master server)
Jermuk
04/03/2024, 7:26 AMensure that you do backups before of Node-RED, but theoretically you should already have them all. even including the ignition configs
m
Mateusz
04/03/2024, 5:14 PMHi, as you are able to connect to NodeRed and it does not receive MQTT messages, it sounds like the central MQTT Broker that is running on your server is not responding. Are you able to check if the UMH instance (running on the dedicated Virtual Machine) there is running and potentially restart it? This would be the quickest fix
2 Views