webodm/nodeodx can't connect, opendronemap/nodeodm works

Aeret

Hi everybody. For a large mapping (4000 images x 45MP) I wanted to run this via an extra node installed on a (temp) GCP instance. However when installing the nodeodx version the WebODM environment (v3.2.4) can't connect to the nodeodx node.

webodm/nodeodx
1) Installed docker
2) installed nodeodx (--> sudo docker run --rm -it -p 3000:3000 webodm/nodeodx -q 1 --token password)

via the CLI I get the message nodeodx is running on port 3000

3) adding the extra node into WebODM frontend.
4) Node is offline in WebODM

opendronemap/nodeodm
1) Installed docker
2) installed nodeodm (--> sudo docker run --rm -it -p 3000:3000 opendronemap/nodeodm:stable -q 1 --token password)

via the CLI I get the message the nodeodm is running on port 3000 (with a large area of text with all the options).

3) adding the extra node into WebODM frontend.
4) Node is online in WebODM

I guess last week I also had another mapping processed via nodeodx, via the same installation procedure and then it did work. As far as I can see I don't see any changes in the Github https://github.com/WebODM/NodeODX so I'm curious what causes this behaviour 🙂

7 Replies

pierotofy

Did you type the address of the node correctly? I can't think of any change that would have affected node connectivity

Aeret OP

Yes, copied the IP adress. Ok good to know nothing has changed from your side 🙂 I will give it a try later on.

Aeret OP

Regarding this topic:

I recently had a large map (A) that was around 4000 x 45 MP images in 31 hours. This job was processed with good results.
I'm currently running another similar job (B) of 4000 x 45MP images of the same area. This job (B) is being aligned onto mapping (A). It seems that the alignment proces takes quite some time (around 47 hours total already).

2026-06-03 05:06:03,903 INFO: Solving ICP registration.

As far as I can understand from the server logs this alignment is being done singlethreaded.

Since the images were taken with RTK I'm curious if there is a way to cancel the job, skip the alignment step, and continue from the last succesful step?

Aeret OP

The mapping was finished after 58 hours 😉 I will ask if I can show the results in the showcases part

🎉 1
pierotofy Best answer

Nice! Yeah the alignment code is a bit slow. I haven't spent much time optimizing it. From WebODM you can't remove the alignment step once you've chosen you want to use the alignment

👍 1
Aeret OP

I think I found out what happened.... (so stupid). When filling in the Token-value for the additional Node at .../admin/nodeodm/processingnode/3/change/.. I mistyped one character 😐 I can confirm that the webodm/nodeodx works as expected 🙂

😄 2

Need more help?

This discussion happened in the WebODM community Discord. Join and ask your own question.

Join View Original Thread

Related questions

This page mirrors a public discussion from the WebODM Discord. How to request a removal.