Not Able to login Superset key decryption error #43227
Replies: 15 comments 20 replies
|
Hey @PARKER-X, don't worry — this is a very common situation and it's fixable! I can see you've been dealing with this across a couple of discussions. Let me give you a clear plan. What's happening: The Step-by-step fix: 1. Figure out which key is actually being loaded Open a terminal in your Superset folder and check: echo %SUPERSET_SECRET_KEY%If that prints anything, it's overriding your Superset logs which config file it loads on startup — look for 2. Pick ONE key and stick with it Your metadata database was encrypted with one specific key. You need to use that same key every time. Never swap keys between restarts without re-encrypting. 3. Re-create your database connections Once you have the correct key loaded and Superset starts without errors, go to Settings → Database Connections and delete and re-add any broken connections. The stored passwords were encrypted with the wrong key and can't be recovered without the original — but you can just re-enter them [1]. 4. If you need to switch to a new key Superset has a CLI command for key rotation: superset re-encrypt-secretsThis re-encrypts stored credentials with the new key. Run it while the old key is still active, then swap to the new key [1]. 5. Clear your browser session After fixing the key, clear cookies/local storage for The most important thing: identify the original key your metadata DB was encrypted with and restore it. If that was your own key before you cloned your friend's project, go back to that value in your Let me know what you see in step 1 and we can narrow it down further! To reply, just mention @dosu. Docs are dead. Just use Dosu.
|
|
this command echo %SUPERSET_SECRET_KEY% returns %SUPERSET_SECRET_KEY% |
|
this command echo %SUPERSET_SECRET_KEY% returns %SUPERSET_SECRET_KEY% |
|
Good news on two things:
Step-by-Step: Get back to working with your original keyStep 1 — Find your original
|
|
how can i find the database uri path?superset_db? @dosu |
@dosu (venv) PS C:\Users\Administrator\Desktop\SamarthX_New\superset> superset db upgradeA Default SECRET_KEY was detected, please use superset_config.py to override it.
|
|
@dosu help |
|
Hey @PARKER-X! Still here to help. Where are you stuck? Are you:
Just share what you're seeing (an error message, a log output, or describe what happened) and I'll help you get unstuck! To reply, just mention @dosu. Docs are dead. Just use Dosu.
|
|
@dosu i am able to login but not able to delete database file "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy_utils\types\encrypted\encrypted_type.py", line 407, in process_result_value During handling of the above exception, another exception occurred: Traceback (most recent call last): |
|
Good progress — you can log in now! The remaining problem is clear from your traceback: the database connection record stored in your metadata DB was encrypted with a different Since the UI can't touch it, you need to delete the record directly in the underlying SQLite database: 1. Install DB Browser for SQLite — download from https://sqlitebrowser.org/ (free). 2. Open your 3. Delete the broken record:
4. Restart Superset. The decryption error will be gone because the broken record no longer exists. 5. Re-add the database connection via Settings → Database Connections → + Database. It will be encrypted with your current
Let me know if you hit any issues finding the file or with the DB Browser steps! To reply, just mention @dosu. Docs are dead. Just use Dosu.
|
|
I am using my old one key no my friend key use my old chats and remember my problem |
|
I am using my old one key no my friend key use my old chats and remember my problem |
|
Great — you have a backup, so let's get you restored step by step. The core issue: Your backup DB ( Step 1 — Fix your The URI you have is not in the correct SQLite format. In your SQLALCHEMY_DATABASE_URI = 'sqlite:///C:/Users/Administrator/.superset/superset-old-backup.db'Alternatively, copy the backup to the standard location: Then you can omit Step 2 — Set your original In SECRET_KEY = 'your-original-key-exactly-as-it-was'This must be the same key that was active when your backup was created. Superset uses this key to encrypt/decrypt database connection passwords and other sensitive fields. If it doesn't match, you'll get decryption errors. Step 3 — Run db upgrade superset db upgradeThis applies any missing schema migrations without wiping your data. Step 4 — Start Superset superset run -p 8088 --with-threads --reload --debuggerStep 5 — Clear browser cookies/session Clear cookies for If you still get a decryption error after these steps, it likely means the backup was created while your friend's key was active (not your original key). In that case, let me know — we can use a tool like DB Browser for SQLite to directly clear the encrypted fields from the database so Superset can start, and then you re-enter your connection passwords manually. Can you confirm that you still have your original To reply, just mention @dosu. Docs are dead. Just use Dosu.
|
But there is no datbase shown?
with closing(engine.raw_connection()) as conn:
^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\engine\base.py", line 3404, in raw_connection
return self._wrap_pool_connect(self.pool.connect, _connection)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\engine\base.py", line 3374, in _wrap_pool_connect
Connection._handle_dbapi_exception_noconnection(
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\engine\base.py", line 2208, in _handle_dbapi_exception_noconnection
util.raise_(
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\util\compat.py", line 211, in raise_
raise exception
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\engine\base.py", line 3371, in _wrap_pool_connect
return fn()
^^^^
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\pool\base.py", line 327, in connect
return _ConnectionFairy._checkout(self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\pool\base.py", line 894, in _checkout
fairy = _ConnectionRecord.checkout(pool)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\pool\base.py", line 493, in checkout
rec = pool._do_get()
^^^^^^^^^^^^^^
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\pool\impl.py", line 256, in _do_get
return self._create_connection()
^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\pool\base.py", line 273, in _create_connection
return _ConnectionRecord(self)
^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\pool\base.py", line 388, in __init__
self.__connect()
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\pool\base.py", line 690, in __connect
with util.safe_reraise():
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\util\langhelpers.py", line 70, in __exit__
compat.raise_(
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\util\compat.py", line 211, in raise_
raise exception
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\pool\base.py", line 686, in __connect
self.dbapi_connection = connection = pool._invoke_creator(self)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\engine\create.py", line 574, in connect
return dialect.connect(*cargs, **cparams)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\sqlalchemy\engine\default.py", line 598, in connect
return self.dbapi.connect(*cargs, **cparams)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Administrator\Desktop\SamarthX_New\superset\venv\Lib\site-packages\psycopg2\__init__.py", line 135, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "172.16.0.119", port 5432 failed: fe_sendauth: no password supplied
(Background on this error at: https://sqlalche.me/e/14/e3q8) The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
Good news — the decryption error is gone! You now have a different, simpler problem: Superset is trying to connect to your PostgreSQL database at The key error is: followed by: This means the database connection form was submitted without a password, or the password field was left blank. What to do:
The If you don't know the PostgreSQL password, you'll need to check with whoever set up the PostgreSQL server at Try re-entering the connection with the password typed explicitly and let me know what happens! To reply, just mention @dosu. Docs are dead. Just use Dosu.
|
|
line 130, in run |
|
You're seeing two separate errors here — let me address each: 1. "Please re-enter the password" / CONNECTION_ACCESS_DENIED_ERROR Even though your password is correct, this error can occur for a few reasons:
Try filling in all the fields and clicking Connect directly rather than using the "Test Connection" button, as the test connection flow can sometimes behave differently with password handling. 2. "A database with the same name already exists" This means there's already a database connection record in Superset with the same display name (the "Database Name" field in the form — this is the label you give it in Superset, not the actual PostgreSQL database name). You likely have a leftover record from a previous attempt. To fix this, you have two options:
Once the duplicate name issue is resolved and the connection credentials are correct, the database connection should succeed. Which approach would you like to try? To reply, just mention @dosu. Docs are dead. Just use Dosu.
|
|
@dosu how can i delete org_db and employee_db from sqlite database viewer and can we acess old charts and graphs |
|
@PARKER-X Here's how you can remove Deleting the database entries
Alternatively (recommended), you can remove them directly from the Superset UI: go to Settings → Database Connections, find Accessing old charts and dashboards Your existing charts and dashboards are stored separately from the database connection entries, so deleting a database connection does not automatically delete the charts that used it. If you re-add the database connections later with the exact same display names (
To reply, just mention @dosu. Docs are dead. Just use Dosu.
|
|
, line 72, in run The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
You have three separate issues here — let me address each clearly: Issue 1: "The port is closed" (port 5432) This means your machine cannot reach the PostgreSQL server at Check: Can you ping ping 172.16.0.119If it doesn't respond, you're not on the right network. This is a network/PostgreSQL server issue, not a Superset issue. Issue 2: "A database with the same name already exists" You said you deleted it from DB Browser, but the error persists. This could mean DB Browser was still open when Superset was running and re-locked the file before your delete was saved, or Superset is pointing to a different Fix:
Issue 3: "sqlite3.OperationalError: database is locked" SQLite doesn't handle multiple concurrent writers well. This error means DB Browser was open at the same time as Superset, locking the file. Never have both open simultaneously. Always stop Superset before using DB Browser, and close DB Browser before starting Superset. In summary — do this in order:
Let me know which step you're stuck on! To reply, just mention @dosu. Share context across your team and agents. Try Dosu.
|
|
@dosu what r u doing man same error |
|
The error To fix the "missing parameters" error:
To fix the "database name already exists" error (since you deleted from DB Browser):
Can you confirm what rows you still see in the To reply, just mention @dosu. Docs are dead. Just use Dosu.
|
|
can i create new secret key and new metabase from scratch @dosu and connect with my data |
|
Yes, absolutely — starting fresh is the cleanest approach. You'll lose any old charts/dashboards stored in the corrupted metadata DB, but your actual data in PostgreSQL is untouched and you can rebuild from there. Here's how: 1. Generate a new SECRET_KEY python -c "import secrets; print(secrets.token_hex(42))"Copy the output. 2. Update SECRET_KEY = 'paste-your-new-key-here'
# Remove or comment out any SQLALCHEMY_DATABASE_URI line
# so Superset creates a fresh default superset.db3. Delete the old metadata DB Delete (or rename) the old SQLite file — by default it lives at 4. Initialize the new metadata database superset db upgrade
superset fab create-admin
superset initSet your new admin username and password when prompted. 5. Start Superset superset run -p 8088 --with-threads --reload --debugger6. Add your PostgreSQL database Go to Settings → Database Connections → + Database, choose PostgreSQL, and enter your host, port, database name, and credentials. Make sure the PostgreSQL server is reachable from your machine before connecting. That's it — clean slate, no more decryption errors, and your source data is safe since Superset only reads from your database. You'll just need to recreate your charts and dashboards. To reply, just mention @dosu. Share context across your team and agents. Try Dosu.
|
|
how can i add database in my folder? |
|
what is the best way to do colobrated work in apache superset file structure for this so 4 ppl can work together @dosu |
|
The core issue is that each person running their own separate Superset instance (with different Practical options (simplest → most robust):
This gives you one What to keep in git:
Never put To add a database: Once your shared instance is running, go to Settings → Database Connections → + Database in the Superset UI. Any database connection you add there will be available to all users on that instance (subject to permissions). You don't add databases to the file/folder structure directly — they're registered through the web interface and stored in the metadata database. For your immediate situation: pick one machine to be the "server," do a fresh To reply, just mention @dosu. Share context across your team and agents. Try Dosu.
|
|
how can we do this One person hosts locally and shares the URL — Run Superset on one machine (e.g. http://192.168.x.x:8088) and the other 3 access it over the same network. Create accounts for each person with superset fab create-user.? how can someone host and other use full roadmap |
|
how can we do this One person hosts locally and shares the URL — Run Superset on one machine (e.g. http://192.168.x.x:8088/) and the other 3 access it over the same network. Create accounts for each person with superset fab create-user.? how can someone host and other use full roadmap @dosu |
|
Here's a full roadmap — Person A (the host) does all the setup, the other 3 just open a browser. Person A (Host) — Setup Steps 1. Find your local IP address Open Command Prompt and run: ipconfigLook for your IPv4 Address under your active network adapter — it'll look like 2. Start Superset bound to all network interfaces Instead of the default (which only listens on superset run -p 8088 --host 0.0.0.0 --with-threadsThe 3. Allow port 8088 through Windows Firewall In PowerShell (as Administrator): New-NetFirewallRule -DisplayName "Superset" -Direction Inbound -Protocol TCP -LocalPort 8088 -Action Allow4. Create accounts for your teammates Run this once per person: superset fab create-user --role Alpha --username teammate1 --firstname Name --lastname Name --email email@example.com --password theirpasswordUse role Persons B, C, D (Teammates) — Nothing to install Just open a browser and go to: (Replace with Person A's actual IP address.) Log in with the credentials Person A created. That's it — full access to shared charts, dashboards, and SQL Lab. Important notes:
This is the simplest way to get a small team collaborating without any cloud or server setup. To reply, just mention @dosu. Share context across your team and agents. Try Dosu.
|
Uh oh!
There was an error while loading. Please reload this page.
I am using superset for my project later i git clone my friend project and use there superset key but i think after superset db upgrade and init from his key i am not able to login on superset using my and his key now i am not able to access key decryption error how can i resolve it i am using my old key now but not able to login and access sqllab or connecting database i just got decryption error plz help me to solve!!
@rusackas @dosu Help me to setup superset for both my friend project and mine i recently joined my 1st full time role and ur company using it working with superset from last 1 month now this error happens i am bit depressed if i am not able to resolve this help me this is my first job!!
Thank you!!
All reactions