Replies: 1 comment 10 replies
-
Well, first things first... back up the environment file ( With those two backed up safely, you can recreate your Redash installation if things go really wrong. Unless there are further customisations that have been done to it, in which case you'll need to back those up too. It sounds like restarting things isn't working for you. Have you tried shutting down the containers completely ( If that doesn't work, then it sounds like there might really be some code level issue that needs investigating. From your description of it running from the Redash AMI, it might be an older Redash version too. Like, perhaps version 8 or similar? If that's the case (after making a backup (not joking!)) you should try upgrading Redash using the process here: https://redash.io/help/open-source/admin-guide/how-to-upgrade The version numbers there are outdated (and should get fixed), so I'd try upgrading to version 10.1.0. That uses the docker image labelled Hopefully something of the above will fix the problem. 🙏 |
Beta Was this translation helpful? Give feedback.
-
We have a running AWS EC2 instance created out of the Redash AMI that has been running for a year and a half with a few reboots. In the past couple of weeks we have been unable to perform queries or see and connect to data sources.
Upon examining the docker compose logs I have found plenty of InvalidToken exceptions thrown every time data sources are queried. I can paste the stack trace if needed. Quick search found that this is somehow related to the
REDASH_SECRET_KEY
environment variable, but it has been unchanged ever since the image was launched and as far I as understand it, it was autogenerated then.Is there a way to mitigate this issue without a data loss, we have a large number of queries and dashboard that would be very painful to recreate.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions