Make sure that at least one processing node is reachable and that you have granted the current user sufficient permissions to view the processing node (by going to Administration – Processing Nodes – Select Node – Object Permissions – Add User/Group and check CAN VIEW PROCESSING NODE). If you are bringing a node back online, it will take about 30 seconds for WebODM to recognize it.
If you haven’t already fixed this, I ran into the same thing recently. User permissions was not the issue in my case, despite the hint. I stopped everything, ran “./webodm.sh update” and then started again with “./webodm.sh start”. It worked fine from there. (You may also need to delete the existing processing node from the list under “Processing Nodes”. Then restart. I recall doing that also, but I’m not sure it was part of the fix.)
Update will take a very long time if you have a lot of data because it will need to convert all your existing data into the current formats. So be very patient.
Start WebODM. Navigate to Processing Nodes and click on your processing node. Most likely going to be “node-odm-1”
Run “docker network inspect odm_default” on PowerShell to get the your IP address. Most likely going to be under “odm_node-odm_1”. Something like that. Copy the numbers before the backslash.
Back in WebODM, click to edit the processing node, and then change the Hostname of the node from “webodm_node-odm_1” to the address you just copied.
Save, give it a few seconds, and all shall be well.