This is a frequently asked question. In most cases it’s the wrong upgrading procedure that caused the problem. Maybe this post could help you, let me know:
Unfortunately, I ran all the database upgrade scripts during the update, and the error still occurred …
The logs on the server itself don’t say anything about it either, except for one thing: dtable config path /opt/seatable/conf/dtable-db.conf doesn't exist: stat /opt/seatable/conf/dtable-db.conf: no such file or directory.
Will this file be created automatically? Unfortunately, it was probably not created for the Docker Pull itself.
The other question is, of course, whether that has anything to do with the bug
The problem has actually been there a little longer, but today I only had time to look for the cause myself.
But today I also updated to 2.2, which unfortunately didn’t change the problem
But the error message seems unrelated to the page loading problem.
What do you mean by …
Are all bases affected? A few? In one and the same base, can you open some tables, other not? Is it always the same error message? Can you discern a pattern?