I’m running the latest version of SeaTable, and using such a SQL query very often. Sadly, every query to [url]/dtable-db/api/v1/query/[base_id] returns bad gateway 502 for me. SeaTables logs in “dtable-db.error.log” shows this error:
2022/10/23 03:31:55 [error] 35#35: *123 upstream prematurely closed connection while reading response header from upstream, client: 172.25.0.1, server: [correct url], request: "POST /dtable-db/api/v1/query/[correct base id]/ HTTP/1.1", upstream: "http://127.0.0.1:7777/api/v1/query/[correct base id]/", host: "[correct host]"
Such a query worked until 3am this morning, and I wasn’t able to fix it and get them running ever since. Our internal tools rely on this method, any help from all of you would be appreciated. In addition to this, other api querys are working, I can normally create, delete or update rows and links etc.
Thank you for reading this