If you had followed this forum for long, you would wonder why the question, "Why does my use of SQLite over a networked filesystem fail in manner (*)?", is not in [the FAQ](https://sqlite.org/faq.html). If it was there, it would briefly explain that locks and concurrent access protections act inconsistently over the network with many/most implementations, and might link to an article worth perusal by anybody still considering use of SQLite over a network filesystem, titled [How To Corrupt An SQLite Database File](https://sqlite.org/howtocorrupt.html), particularly section 2.1. "Filesystems with broken or missing lock implementations". I recommend that reading to you. I think the question posed here, "Why does this use fail now?" could be better recast as "Why did it seem to work for so long?" After that reading, I suspect you will agree. If you really want to use SQLite over the network, you can find published programs (with source) which run locally on the same machine with some SQLite database(s) residing on reliable attached storage hardware and offer networked-accessible access. The SQLite designers have included your use case in [Appropriate Uses For SQLite](https://sqlite.org/whentouse.html). (See "Server-side database".) IMO, while it is interesting to watch yet another attempt to chase down a gremlin plaguing a SQLite-over-networked-filesystem application, it is not going to result in a reliable solution unless whatever transient circumstances led to transient success before can be made less transient. (It's like watching somebody after they say "Watch me build this big pyramid of eggs!)