Server locked error

Worked fine for months. Now everybackup is server locked error.

What should i do?

Welcome to the forum @Adramelramalech

I’m not finding that text in Duplicati (or its web server) source, in the forum, or in GitHub Issues.
Can you describe error appearance further, or preferably paste a screenshot of it into this topic.

For general info, what operating system is this, and what sort of destination is backup going to?

Above, plus say what you tried, if anything. For example, did you restart Duplicati or the system?

I apologize but that is all I have is server locked error message. It worked for months now it will not run at all. I restarted the service, edit the backup job. Nothing works.

The message is still happening, but you can’t describe it or screenshot it and paste to the forum?

What about this info?

Win10 is what duplicati is installed on
it is using webdav
the designation is my nextcloud
in nextcloud the designation drive is an mounted NAS share
I guess I may have to drive over there and take a pic.
Thanks.

??? Isn’t Duplicati on the screen near you, either in your web browser or some sort of command line?

If you’re using from Windows, see 7 ways you can take screenshots in Windows 10 and Windows 11

EDIT:

If in Duplicati GUI, you can start About → Show log → Live → Warning before backup. Click on errrors.
About → Show log → Stored is an alternative error location, most likely used when backup doesn’t run.

Nope. A few towns over.

Ouch. So you’re just reporting from memory and have no remote access? This may get awkward.

Sounded like you had a view of something (maybe there at the time?). Was it a GUI popup over the standard Duplicati screen? If so, was it blue and in the middle or red and near the bottom? Was it a Windows notification which sometimes says the same thing? Was it a web page with just that text?

Meaning you installed as a Windows service using Duplicati.WindowsService.exe after initial install?
You then used the Windows service tools to restart the service? You could also try a system reboot.

Server error


Server is loading

Nothing in logs.

Errors reported by Duplicati which refer to the “remote server” mean the destination server, here the Nextcloud server, which uses WebDAV, which is an extension of HTTP. 423 looks WebDAV-specific:

List of HTTP status codes on Wikipedia:

423 Locked (WebDAV; RFC 4918)
The resource that is being accessed is locked.

From RFC 4918:

   The 423 (Locked) status code means the source or destination resource
   of a method is locked.  This response SHOULD contain an appropriate
   precondition or postcondition code, such as 'lock-token-submitted' or
   'no-conflicting-lock'.

and because I’m not familiar with WebDAV, I won’t try to interpret that. From Duplicati end, you can (if you have accesss…) About → Show log → Live → Retry to see what was being tried when 423 was returned.

A backup will usually begin with list, then do a series of put for uploads, then list and get verifications. Alternatively you can try the Verify files choice which is probably just the list and probably three get.

There seem to be some Internet search results for Nextcloud 423 locked problems. You can look at some.

That really does not help me. I delete the job, make a new one and it works. And no one has a fix or any idea. I am too accept that? We can develop duplicati and nextcloud and webdav but a solution, an idea or anything we are to just ignore?

I must not understand this term locked. What does locked mean? I can still access the server, and everything works. It is a problem between duplicati and the server but the user can use it all day no problem. I dont get it

Jan 12, 2022 10:59 AM: Failed while executing “Backup” with id: 5
System.Net.WebException: The remote server returned an error: (423) Locked.
at Duplicati.Library.Main.BackendManager.Delete(String remotename, Int64 size, Boolean synchronous)
at Duplicati.Library.Main.Operation.FilelistProcessor.RemoteListAnalysis(BackendManager backend, Options options, LocalDatabase database, IBackendWriter log, IEnumerable1 protectedFiles) at Duplicati.Library.Main.Operation.FilelistProcessor.VerifyRemoteList(BackendManager backend, Options options, LocalDatabase database, IBackendWriter log, IEnumerable1 protectedFiles)
at Duplicati.Library.Main.Operation.BackupHandler.PreBackupVerify(BackendManager backend, String protectedfile)
at Duplicati.Library.Main.Operation.BackupHandler.d__20.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at CoCoL.ChannelExtensions.WaitForTaskOrThrow(Task task)
at Duplicati.Library.Main.Controller.<>c__DisplayClass14_0.b__0(BackupResults result)
at Duplicati.Library.Main.Controller.RunAction[T](T result, String[]& paths, IFilter& filter, Action`1 method)
at Duplicati.Library.Main.Controller.Backup(String[] inputsources, IFilter filter)
at Duplicati.Server.Runner.Run(IRunnerData data, Boolean fromQueue)

And by the way, three machines are now getting the same error.

I’m taking a guess here, but maybe it fails when Duplicati decides to delete files on the remote side. Are you disallowing deletions by chance?

And I am taking a guess here no one really cares at all.
I have no idea what I am supposed to do here. Literally. So Duplicati that once was I can no longer use so everything I made was all for nothing.
What am I missing here? Seriously? How are you all using duplicati?

Not sure why you are saying that, we are trying to help you. Duplicati is designed to work with myriad back end products, and it has no control over limitations placed intentionally on the back end (like prohibiting deletions), or unintentionally, or compatibility issues on the back end.

Did you prohibit deletions on the back end, either intentionally or unintentionally (incorrect permissions)?

I do not know what that means or how you like me to respond

The problem is I have no idea what to do. And once again I am in another stituation where tens of thousands of people can use duplicati and I am the only one that can not use it. Every one just passes the blame. It does not matter anything.Community. Here. I need assistance. I get none.

I am getting the same thing on next cloud, no support and the blame is being passed

I just need to walk away from this and find another solution. Only thing i can do and there is no other solution so it sucks.

Now i get this

Failed to connect: database is locked database is locked

How about this.

Does duplicati even work?