Was following these instructions, updated the configs, and tried to re-start docker. When re-accessing the app from the browser, I get the following message.
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
On the server logs, I see
scheduler_1 | OperationalError: (psycopg2.OperationalError) FATAL: password authentication failed for user “postgres”
I managed to reproduce this. The issue is the following: when the Postgres container is run for the first time it creates its configuration and after that point you can no longer change the postgres user password.
When the instance boots we update the COOKIE SECRET and Postgres password to new values, so that not all the instances share the same ones. But for Postgres this has no effect.
To fix this, update your /opt/redash/env files to includes the following values:
As an alternative, you can login to Postgres with the above password and update the password of the postgres user to use the new one that was generated by your instance. This is actually more secure.
We will create new AMIs now to avoid this issue for future users.
Hello
I have the very same issue -(
run ./setup.sh
error
File “/usr/local/lib/python2.7/dist-packages/psycopg2/init.py”, line 130, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) FATAL: password authentication failed for user “postgres”
If I apply the technique described by Arik, I will get the following question during the setup process:
“rm: remove write-protected regular file ‘/opt/redash/env’?”
which will rewrite the credentials we just wrote in env.