Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
An unknown error occurred. Please contact your Superset administrator
See original GitHub issueHello, I have installed superset using SupersetOffcDoc And successfully ran superset using command gunicorn superset:app but when i try to import a dashboard getting An unknown error occurred. Please contact your Superset administrator. My logged in user is ADMIN and also i found no errors in logs
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (2 by maintainers)
Top Results From Across the Web
An unknown error occurred. Please contact your Superset ...
Hello, I have installed superset using SupersetOffcDoc And successfully ran superset using command gunicorn superset:app but when i try to ...
Read more >An unknown error occurred. Please contact your Superset ...
liya2664 closed issue #8322: An unknown error occurred. Please contact your Superset administrator URL: ...
Read more >Unable to load dashboards list due to JSON decode error in ...
I tried to take a look at the dashboards table in my DB but could not find any irregularity. I tried to load...
Read more >Issue Code Reference - Apache Superset
Your query failed because of an error that occurred on the database. ... Please contact an administrator if you need to run DML...
Read more >airbnb/superset - Gitter
I tried to do import but failed with error: "An unknown error occurred. Please contact your superset administrator". JASON FOCHO.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had the same issue. Renaming the database to the old one, did the job.
If you are unsure of what was the old database. You can find it at the end of the export file itself with the
database_namekey.Please check the database name, it should be same to import dashboard or can rename to existing database name in json (database_name) before importing json