You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "joaocosta123 (via GitHub)" <gi...@apache.org> on 2023/06/26 08:02:21 UTC
[GitHub] [superset] joaocosta123 opened a new issue, #24512: Superset on 443 port
joaocosta123 opened a new issue, #24512:
URL: https://github.com/apache/superset/issues/24512
When I try to run superset on port 443 by the command "superset run --cert ".........." --key "......." -h 0.0.0.0 -p 443 --with-threads --reload --debugger"
This is the error....
Serving Flask app 'superset' (lazy loading)
Environment: production
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
Debug mode: off
Permission denied
How can i chanhe the port to 443 if i dont put "-p 443" on the comand it run's perfectly on port 5000.
On my custom superset_config.py is "WEBDRIVER_BASEURL = "http://0.0.0.0:443/"
On your default config,py is "
SUPERSET_WEBSERVER_PROTOCOL = "https"
SUPERSET_WEBSERVER_ADDRESS = "0.0.0.0"
SUPERSET_WEBSERVER_PORT =443
"
And still Permission denied......
How can i configure https on port 443?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] datta90 commented on issue #24512: Superset on 443 port
Posted by "datta90 (via GitHub)" <gi...@apache.org>.
datta90 commented on issue #24512:
URL: https://github.com/apache/superset/issues/24512#issuecomment-1632923906
you will need root or sudo priviledges to run an application on port 443 . or as per @sfirke you can use nginx
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] sfirke commented on issue #24512: Superset on 443 port
Posted by "sfirke (via GitHub)" <gi...@apache.org>.
sfirke commented on issue #24512:
URL: https://github.com/apache/superset/issues/24512#issuecomment-1625680176
Most people use an application gateway, load balancer, or reverse proxy to implement SSL / HTTPS and route traffic in via port 443. You could try asking this in the Superset Slack chat, but it seems like more of a general Docker question than a Superset bug or issue that needs the project's attention.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org