Hi all,

I've been using a Scaleway storage to backup my instance on a 3-day basis but I've been getting various timeout errors since the last 5 days (each day):

Message: write EPIPE HTTP Code: NetworkingError.

Message: Your socket connection to the server was not read from or written to within the timeout period. HTTP Code: RequestTimeout.

Message: Socket timed out without establishing a connection HTTP Code: TimeoutError.

Message: write EPIPE HTTP Code: NetworkingError.

The errors only happen after an hour or so in the backup process and files are added to my Scaleway instance. The error always pops up somewhere deep inside a gibberish directory (I think it's encrypted?) but never the same one so it seems. It's always my NextCloud instance and the directory always seems to match in some way, something like:

snapshot/app_xxxx/....1NRyroOTEk..../....YDrvyp7W5N..../..a../..b../..c../..d..
snapshot/app_xxxx/....1NRyroOTEk..../....YDrvyp7W5N..../..k../..l../..m../..n..

The only thing I can think of is that I messed up my NextCloud instance a bit because I removed a file directly in the terminal, which apparently causes the instance to get confused with its database. As recommended on other NextCloud posts that I found, I ran a command to reindex my database. Something like this:

sudo -u www-data php occ files:scan --all

I ran it within the Cloudron terminal of my NextCloud instance.

Any ideas on how to debug this problem? Is it related to the described hickup? Or is it related to Cloudron/Scaleway?

Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Cloudron Forum

timmeh