Cannot access processing node after update about nodeodm HOT 8 CLOSED

Hey @xmutantson ✋

If you run from a shell:

docker run -p 3000:3000 -v /mnt/sdb1:/var/www/data opendronemap/node-opendronemap

Are you able to access http://localhost:3000 ? If so, then the node is working fine. Note that you should use the IP address of your network card to reference the node in WebODM, don't set the hostname to localhost, use the IP address instead.

from nodeodm.

Here's the output. Not sure what to make of it.

kameron@SilverPancake:/WebODM$ docker run -p 3000:3000 -v /mnt/sdb1:/var/www/da ta opendronemap/node-opendronemap
docker: Error response from daemon: driver failed programming external connectiv ity on endpoint youthful_carson (09b9222a6afb134801e3ad2d64b76c4d1ca7130144f68b8 b583a402030a13cbc): Bind for 0.0.0.0:3000 failed: port is already allocated.
ERRO[0000] error getting events from daemon: net/http: request canceled
kameron@SilverPancake:/WebODM$

from nodeodm.

So I think I now understand what you were asking me to do. I went to the address in chrome. This is what I have.

from nodeodm.

I tried it again, and now with new results. I am on a local network with the server and now get this error. @pierotofy

from nodeodm.

@xmutantson I wish I knew what the problem was, but I don't know what's causing it. It seems to be specific to the environment in which you are running WebODM, so it's likely a possible configuration/network issue, not necessarily a problem with WebODM itself?

from nodeodm.

[code]
Ping statistics for 192.168.8.112:
Packets: Sent = 55, Received = 55, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
[/code]
How is this a network issue? My network seems stable to me. That ping report was generated after deleting webodm on both machiens and reinstalling. Is it significant that the API versions are different for the built in processing node versus the server's API version?

from nodeodm.

The NodeODM API's latest version is 1.3.1. WebODM doesn't care too much about what version you are using, as the API as not changed much since its first release. If in doubt, make sure you are running the latest version of both software, but I don't think that's the root of the problem.

from nodeodm.

Closing as this does not seem a bug in NodeODM.

from nodeodm.