Does this help: https://github.com/apache/superset/issues/25359?
On Sun, Oct 1, 2023 at 9:50 PM Tseng Anthony <[email protected]> wrote: > Dear Team, > > Could you help on this issue？ > > ## How to reproduce > > 1. Install the latest superset as below: > # pip install apache-superset Pillow > # export SUPERSET_SECRET_KEY=`openssl rand -base64 42` > # export FLASK_APP=superset > # superset fab create-admin --username admin --firstname Superset > --lastname Admin --email [email protected] --password admin > # superset db upgrade > # superset superset init > # superset run -h 172.17.0.7 -p 8080 --with-threads --reload --debugger > the output as below: > ====================================================================== > logging was configured successfully > 2023-09-30 20:55:12,234:INFO:superset.utils.logging_configurator:logging > was configured successfully > 2023-09-30 20:55:12,328:INFO:root:Configured event logger of type <class > 'superset.utils.log.DBEventLogger'> > /usr/local/lib/python3.11/site-packages/flask_limiter/extension.py:336: > UserWarning: Using the in-memory storage for tracking rate limits as no > storage was explicitly specified. This is not recommended for production > use. See: > https://flask-limiter.readthedocs.io#configuring-a-storage-backend for > documentation about configuring the storage backend. > warnings.warn( > * Serving Flask app 'superset' > * Debug mode: off > 2023-09-30 20:55:13,280:INFO:werkzeug:WARNING: This is a development > server. Do not use it in a production deployment. Use a production WSGI > server instead. > * Running on http://172.17.0.7:8080 > 2023-09-30 20:55:13,280:INFO:werkzeug:Press CTRL+C to quit > 2023-09-30 20:55:13,281:INFO:werkzeug: * Restarting with stat > logging was configured successfully > 2023-09-30 20:55:14,680:INFO:superset.utils.logging_configurator:logging > was configured successfully > 2023-09-30 20:55:14,786:INFO:root:Configured event logger of type <class > 'superset.utils.log.DBEventLogger'> > /usr/local/lib/python3.11/site-packages/flask_limiter/extension.py:336: > UserWarning: Using the in-memory storage for tracking rate limits as no > storage was explicitly specified. This is not recommended for production > use. See: > https://flask-limiter.readthedocs.io#configuring-a-storage-backend for > documentation about configuring the storage backend. > warnings.warn( > 2023-09-30 20:55:15,777:WARNING:werkzeug: * Debugger is active! > 2023-09-30 20:55:15,778:INFO:werkzeug: * Debugger PIN: 787-983-920 > logging was configured successfully > 2023-09-30 20:55:12,234:INFO:superset.utils.logging_configurator:logging > was configured successfully > 2023-09-30 20:55:12,328:INFO:root:Configured event logger of type <class > 'superset.utils.log.DBEventLogger'> > /usr/local/lib/python3.11/site-packages/flask_limiter/extension.py:336: > UserWarning: Using the in-memory storage for tracking rate limits as no > storage was explicitly specified. This is not recommended for production > use. See: > https://flask-limiter.readthedocs.io#configuring-a-storage-backend for > documentation about configuring the storage backend. > warnings.warn( > * Serving Flask app 'superset' > * Debug mode: off > 2023-09-30 20:55:13,280:INFO:werkzeug:WARNING: This is a development > server. Do not use it in a production deployment. Use a production WSGI > server instead. > * Running on http://172.17.0.7:8080 > 2023-09-30 20:55:13,280:INFO:werkzeug:Press CTRL+C to quit > 2023-09-30 20:55:13,281:INFO:werkzeug: * Restarting with stat > logging was configured successfully > 2023-09-30 20:55:14,680:INFO:superset.utils.logging_configurator:logging > was configured successfully > 2023-09-30 20:55:14,786:INFO:root:Configured event logger of type <class > 'superset.utils.log.DBEventLogger'> > /usr/local/lib/python3.11/site-packages/flask_limiter/extension.py:336: > UserWarning: Using the in-memory storage for tracking rate limits as no > storage was explicitly specified. This is not recommended for production > use. See: > https://flask-limiter.readthedocs.io#configuring-a-storage-backend for > documentation about configuring the storage backend. > warnings.warn( > 2023-09-30 20:55:15,777:WARNING:werkzeug: * Debugger is active! > 2023-09-30 20:55:15,778:INFO:werkzeug: * Debugger PIN: 787-983-920 > ====================================================================== > 2. Open browser and input http://172.17.0.7:8080 will see the superset > portal but while try to login with admin/admin, > will not login and the errorr message as bleow: > ====================================================================== > 2023-09-30 20:55:30,020:INFO:werkzeug:172.17.0.1 - - [30/Sep/2023 > 20:55:30] "GET /login/ HTTP/1.1" 200 - > 2023-09-30 20:55:31,436:INFO:flask_wtf.csrf:The CSRF session token is > missing. > Refresh CSRF token error > Traceback (most recent call last): > File "/usr/local/lib/python3.11/site-packages/flask_wtf/csrf.py", line > 261, in protect > validate_csrf(self._get_csrf_token()) > File "/usr/local/lib/python3.11/site-packages/flask_wtf/csrf.py", line > 103, in validate_csrf > raise ValidationError("The CSRF session token is missing.") > wtforms.validators.ValidationError: The CSRF session token is missing. > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/local/lib/python3.11/site-packages/flask/app.py", line 1821, > in full_dispatch_request > rv = self.preprocess_request() > ^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/local/lib/python3.11/site-packages/flask/app.py", line 2313, > in preprocess_request > rv = self.ensure_sync(before_func)() > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/local/lib/python3.11/site-packages/flask_wtf/csrf.py", line > 229, in csrf_protect > self.protect() > File "/usr/local/lib/python3.11/site-packages/flask_wtf/csrf.py", line > 264, in protect > self._error_response(e.args[0]) > File "/usr/local/lib/python3.11/site-packages/flask_wtf/csrf.py", line > 307, in _error_response > raise CSRFError(reason) > flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF session token is > missing. > 2023-09-30 20:55:31,436:WARNING:superset.views.base:Refresh CSRF token > error > Traceback (most recent call last): > File "/usr/local/lib/python3.11/site-packages/flask_wtf/csrf.py", line > 261, in protect > validate_csrf(self._get_csrf_token()) > File "/usr/local/lib/python3.11/site-packages/flask_wtf/csrf.py", line > 103, in validate_csrf > raise ValidationError("The CSRF session token is missing.") > wtforms.validators.ValidationError: The CSRF session token is missing. > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/local/lib/python3.11/site-packages/flask/app.py", line 1821, > in full_dispatch_request > rv = self.preprocess_request() > ^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/local/lib/python3.11/site-packages/flask/app.py", line 2313, > in preprocess_request > rv = self.ensure_sync(before_func)() > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/local/lib/python3.11/site-packages/flask_wtf/csrf.py", line > 229, in csrf_protect > self.protect() > File "/usr/local/lib/python3.11/site-packages/flask_wtf/csrf.py", line > 264, in protect > self._error_response(e.args[0]) > File "/usr/local/lib/python3.11/site-packages/flask_wtf/csrf.py", line > 307, in _error_response > raise CSRFError(reason) > flask_wtf.csrf.CSRFError: 400 Bad Request: The CSRF session token is > missing. > 2023-09-30 20:55:31,438:INFO:werkzeug:172.17.0.1 - - [30/Sep/2023 > 20:55:31] "POST /login/ HTTP/1.1" 302 - > 2023-09-30 20:55:31,480:INFO:werkzeug:172.17.0.1 - - [30/Sep/2023 > 20:55:31] "GET /login/ HTTP/1.1" 200 - > ^C[root@superset ~]# > ====================================================================== > > ## Environment > > - browser type and version: > Firefox 102.15.1esr(64-bit) > - superset version: `superset version` > [root@superset ~]# superset version > logging was configured successfully > 2023-09-30 21:08:25,369:INFO:superset.utils.logging_configurator:logging > was configured successfully > 2023-09-30 21:08:25,477:INFO:root:Configured event logger of type <class > 'superset.utils.log.DBEventLogger'> > /usr/local/lib/python3.11/site-packages/flask_limiter/extension.py:336: > UserWarning: Using the in-memory storage for tracking rate limits as no > storage was explicitly specified. This is not recommended for production > use. See: > https://flask-limiter.readthedocs.io#configuring-a-storage-backend for > documentation about configuring the storage backend. > warnings.warn( > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Superset 3.0.0 > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > [root@superset ~]# > [root@superset ~]# python -V > Python 3.11.2 > [root@superset ~]# pip -V > pip 23.2.1 from /usr/local/lib/python3.11/site-packages/pip (python 3.11) > > > > -- Regards Multazim Deshmukh https://www.linkedin.com/in/multazim-deshmukh-a5b68429/
