Issues embedding dashboard in public website #31442
-
Bug descriptioni'm using superset via
I tried add to superset_config.py:
So i get error:
Screenshots/recordingsNo response Superset versionmaster / latest-dev Python version3.9 Node version16 BrowserChrome Additional contextNo response Checklist
|
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 3 replies
-
|
Hey @RealTun, I'm here to assist you with the issue you're facing in embedding the Superset dashboard. I can help you with bug fixes, answering questions, and even guide you on how to become a contributor. Let's tackle this together! I found some similar discussions that might help you resolve the issue with embedding a Superset dashboard in a public website:
To resolve the 'X-Frame-Options' error, you should modify the TALISMAN_ENABLED = True
TALISMAN_CONFIG = {
"content_security_policy": {
"frame-ancestors": ["*.my-domain.com", "*.another-domain.com"],
}
}After making these changes, restart Superset to apply the new configuration [1]. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Beta Was this translation helpful? Give feedback.
-
|
@dosu i added: but i still get same error |
Beta Was this translation helpful? Give feedback.
-
|
Ensure that the If the issue persists, you might want to explicitly set the HTTP_HEADERS = {
'X-Frame-Options': 'ALLOWALL'
}Make sure that To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Beta Was this translation helpful? Give feedback.
-
|
@dosu i added it, sill get same error |
Beta Was this translation helpful? Give feedback.
-
|
Ensure that there are no other configurations or middleware that might be overriding your settings. Here are a few steps to troubleshoot further:
If these steps don't resolve the issue, consider checking any web server or proxy configurations that might be affecting the headers. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Beta Was this translation helpful? Give feedback.
-
|
You probably shouldn't be using docker compose for production servers. @sfirke might be able to help with some of this. Meanwhile, I'll convert this to a Discussion since it's not a bug. |
Beta Was this translation helpful? Give feedback.
-
|
Here are some steps for this: https://superset.apache.org/docs/configuration/networking-settings/#embedding-a-public-direct-link-to-a-dashboard Start there and if that doesn't do it, maybe we can expand those docs? |
Beta Was this translation helpful? Give feedback.
-
|
Is there any way or documentation showing how to deploy superset under a prefixed URL (https://myhost.com/my-superset) avoiding redirect issues? I would like to use embedding dashboard as well but under Azure APIM. |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys, I have this issue as well, and I did all the changes on Talismand and the header. I have version 5.0.0. Did someone find the solution to this issue? |
Beta Was this translation helpful? Give feedback.
You need grant permission access to database that u wanting other people can see for public.
Watch this video from 4m20s: https://youtu.be/FH_2csQ7D9c?si=7XETUEv1_QKgsdu-&t=269