-
After some recent updates this weekend our Redash installation is now unresponsive. Attempting to restore, or clone a working backup to a new instance, throws this error.
An error occurred during the restore operation: Addons Error: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/dc95a87a-2048-4187-b2a7-7310de48e50a/postgresqldump to http://172.18.30.2:3000/databases/dbdc95a87a20484187b2a77310de48e50a/restore?access_token=REDACTED&username=REDACTED: status 408 complete false
Any help anyone could offer would be greatly appreciated.
-
After some recent updates this weekend our Redash installation is now unresponsive. Attempting to restore, or clone a working backup to a new instance, throws this error.
An error occurred during the restore operation: Addons Error: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/dc95a87a-2048-4187-b2a7-7310de48e50a/postgresqldump to http://172.18.30.2:3000/databases/dbdc95a87a20484187b2a77310de48e50a/restore?access_token=REDACTED&username=REDACTED: status 408 complete false
Any help anyone could offer would be greatly appreciated.
-
@cdolson are you on 7.4.0 ? We got a couple of reports on error when restoring to Postgres (pretty much the same error you posted). So , just cheking if these are all related.
-
@cdolson are you able to contact us at support@cloudron.io ?
-
G girish moved this topic from Redash on
-
This was a bug in 7.4.0 and is now fixed in 7.4.1.
We updated node to v18 (from v16). There was a subtle but impact change hidden... In node 16, the requestTimeout was 0. This meant unlimited time. In node 18, the requestTImeout is now 5 mins. This meant that large restores were failing if the upload didn't finish within 5 mins.
-
G girish marked this topic as a question on
-
G girish has marked this topic as solved on
-
G girish referenced this topic on