Joplin: Usage Error: The nearest package directory doesn't seem to be part of the project declared in /app/code

[krumel]

Hi everyone,
the current version of Joplin (2.3.2) suddenly throws a rather strange error and became unresponsive.

 $ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0] <scriptName> ...
Usage Error: The nearest package directory (/app/code/packages/server) doesn't seem to be part of the project declared in /app/code.
- Finally, if /app/code is fine and you intend packages/server to be treated as a completely separate project (not even a workspace), create an empty yarn.lock file in it.
 - If /app/code is intended to be a project, it might be that you forgot to list packages/server in its workspace configuration.
 - If /app/code isn't intended to be a project, remove any yarn.lock and/or package.json file there.
 => Healtheck error: Error: Timeout of 7000ms exceeded

Most interestingly it occured days after the 2.3.2 update and I couldn't identify any other factors that could have caused this.
Does anyone have an idea how to solve this?

[nebulon]

Have you by chance edited the config file in /app/data for that instance? Trying to reproduce it here, but it seems it work.

[krumel]

Nope, absolute standard install. I had to go back one update to make it work again for now.