WebODM update Error

Hello People!

I have been using WebODM since once build 18 and I tried updating the software. It got updated on 2 machines out of 3 successfully.

3rd one got some error and I cancelled the installation. It was not opening after that… So reinstalled the software through windows native installer build 18 and it was working successfully… but if I try to update the latest version , I face issues while expanding tasks, The screen goes blank.

I’ve seen other issues as well, but nothing for Windows or without uninstalling the previous versions. I have lots of data around 250 GB on WebODM server.

  1. Can you please tell me the fix of this bug?
  2. If only uninstalling previous versions and reinstalling → updating is the only solution… then how can I take back up… Should I just backup the projects folder and then paste it after updating?

same issue - Problems after webodm update - WebODM - OpenDroneMap Community

These appear to be the Docker version, and a build you’ve customized at that. This may be a cause for the conflict when updating.

Can you please confirm these are WebODM for Windows native or the Docker version?

1 Like

WebODM for Windows Natie installer. We bought it.
It is 1.9.2 build 28 . Now I’m updating to latest one.

Maybe it was bug,

But I think it is possible to backup your project file and uninstall the broken one, reinstall build 18 which works good for you. Finally restoring the backup files. I’m sorry can not explain detailed way to do that, since I don’t have any experience with paid native windows,

Yeah, I do think so… that uninstalling and reinstalling will work for sure.
But the problem is taking backup. I want a proved procedure of how to take backup and put it in the new one without much difficulties.

Also, does 1.9.2 build 28 is not good with processing images with GCP’s, cuz I also faced this issue. Although, they are working well in the latest version and kinda more accurate then pix4d as well.

What you’re showing in your screenshots is not the WebODM for Windows native that we ship.

You copy the data folder under the WebODM for Windows native install directory (usually C:\WebODM)


You copy the AppData folder for your Windows User account:


Uninstall/reinstall or upgrade as normal, and when the program is not running, paste these back into the same locations, opting to overwrite all files.

1 Like

Yes, we bought Windows Native installer but we modified some things to make it visible on server. The screenshot you see is the Web instance of the same. We just changed the IP in main.js file to a different one and DESKTOP MODE = FALSE.
SINGLE USER = FALSE in local settings.py file.
Also, sharable links as Public.

But I think that doesn’t matter while updating… Right?

WebODM seems to be working fine for other users.

Your modified version is what seems to be currently breaking.

So perhaps it is a problem with the modifications?

1 Like

For the backup… I have to take backup of 2 different folder … right?
And paste it back in the same paths?

1 Like

Yes. Those two folders I noted, back exactly to where they each came from.

I will note that this is not really a supported method, and that we in general recommend people use the all.zip export method for critical task backups.


Yeah , It can be the possible case.
Should I undo the changes and then Update?
Will that work?

Great Help. If updating won’t work. I’ll obiously do that

1 Like

But I have almost 50 tasks contained in 10 different projects… Is it really a feasible method to download all task’s all.zip file and then upload them again at every method.

1 Like

I guess you’re balancing risk vs time at that scale… Using the all.zip export is our supported/tested means.

What I told you is how I personally do it for testing locally, but I’m also not fussed if I have to clean install since none of what I work with is critical data. It has worked fine for me thus far, but caveat emptor, as ever.

1 Like

For sure… that more of feels like sarcastic… but I;ll surely try your idea.

1 Like

Sorry, not meant to be sarcastic at all.

Simply a warning that I’ve done it locally numerous times and on a few customer computers for support/testing, but not at any scale that I’d consider it well-tested or generally something I want folks using as a first option.

So, please beware/careful if you use that method.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.