Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Superset Dashboard Loading Slow when Enable HTTPS #8938

SyamprasadNakka opened this issue Jan 8, 2020 · 3 comments

Superset Dashboard Loading Slow when Enable HTTPS #8938

SyamprasadNakka opened this issue Jan 8, 2020 · 3 comments


Copy link

@SyamprasadNakka SyamprasadNakka commented Jan 8, 2020

Hello Team,

We have enabled HTTPS by running superset with GUNICORN server and observed the dashboard page is loading slow. It's taking around 10-15 Sec delay and loading the page. We didn't face this slowness issue when running the server with HTTP.

###Command used to run:
gunicorn -w 10 --certfile /home/superset/ssl/companyname.crt --keyfile /home/superset/ssl/companyname.key -b --limit-request-line 0 --limit-request-field_size 0 superset:app

Expected results

Dashboard page should load without any delay

Actual results

Dashboard page is loading with 10-15 sec delay when enable https


If applicable, add screenshots to help explain your problem.

How to reproduce the bug

  1. Run superset with gunicorn server by using HTTPS
  2. Click on any Dashboard from dashboard menu
  3. Observe the page loading time
  4. See the time lag.


  • superset version: unofficial-superset==0.33.10402
  • python version: python 3.7


Make sure these boxes are checked before submitting your issue - thank you!

  • [*] I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • [*] I have reproduced the issue with at least the latest released version of superset.
  • [*] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.


This comment has been minimized.

Copy link

@issue-label-bot issue-label-bot bot commented Jan 8, 2020

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.81. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the #bug label Jan 8, 2020

This comment has been minimized.

Copy link

@willbarrett willbarrett commented Jan 8, 2020

You will experience better performance by setting up NGinx on the machine and terminating SSL at the web server rather than the Python process. I would recommend setting up gunicorn to only listen on the local loopback and having NGinx proxy requests via localhost. I hope this helps!


This comment has been minimized.

Copy link

@SyamprasadNakka SyamprasadNakka commented Jan 9, 2020

Hello Willbarret,
Thanks for the update.

We have enabled CAS - SSO (#968) and enabled the SSL through gunicorn server to work with HTTPS.

Currently we are not using nginx to terminate the SSL from gunicorn. Are there any steps needs to perform to work with both HTTPS and SSO along with nginx/apache httpd server?

Can you please provide any inputs.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.