General backup error from one custom app

[jbrichez]

Hi everyone,
I have some custom app installed on my Cloudron.
I scheduled global backup everyday.
Since 4 days now I have a backup error:

Error uploading snapshot/app_032a1955-1996-42d5-8396-478d39a39b7d.tar.gz.enc. Message: Non-whitespace before first tag. Line: 0 Column: 1 Char: { HTTP Code: XMLParserError

I localized the app from where the error come from. But i don't understand the point.
Can anyone help me ?
Thanks you

[nebulon]

So other apps backup fine?

[jbrichez]

@nebulon Yes no problem with other app.
But because of this one failed, global backup failed too.

[nebulon]

Hm usually this XMLParserError indicates an issue with the backup storage provider. Which one are you using?

[jbrichez]

@nebulon I'm using contabo object storage.

[jdaviescoates]

@jbrichez possibly not relevant at all but I just searched for that "Non-whitespace" message and saw e.g. this:

https://stackoverflow.com/questions/34783452/cannot-parse-xml-error-non-whitespace-before-first-tag-line-0-column-1-cha

[jbrichez]

@jdaviescoates Hmm sounds like to be. I'm not a specialist of Cloudron so maybe a dev could says if one of those involved packages is used

[girish]

@jbrichez the xml error message is a fairly generic message. The AWS S3 protocol is based on XML. What's happened here is that when Cloudron is trying to backup using the S3 protocol, something is going wrong.

Usually, this error is not library code related. It's either related to the S3 provider (contabo) OR because of a bug in Cloudron backup logic. About the latter, there is a known issue that if files keep changing a lot (let's say you have log files as part of your backups, or temporary sessions files that keep coming and going), then the backup code is unable to handle this properly. Is this the case with your custom app?

[jbrichez]

There is logs files yes.

UPDATE: same problem with invoiceNinja.
So problem not only linked to my custom app

[jbrichez]

Ok my bad... The bucket wasn't existing anymore.
But still the error should be another one

[nebulon]

Yes that is annoying, do you happen to know that your particular provider responds if the bucket does not exist at all. Given the error you were pasting, it seems it is something not part of the normal S3 protocol.

[jbrichez]

@nebulon I don't really know the S3 system they used