[Urgent] Unable to load superset stuck in welcome page post login

[Maannniii]

Superset docker-compose deployment not proceeding after login. Returns 404 for /static/assets/images/loading.gif

How to reproduce the bug

1. Clone superset repo.
2. cd superset and use docker-compose up -d to bring up containers.
3. Open developer tools and log in to Superset with admin creds.
4. Post login it redirects to http://localhost:8088/superset/welcome/ and is stuck there

Expected results

Should Proceed to further screens.

Actual results

Page is stuck at http://localhost:8088/superset/welcome/ and in developer tools, under Network we can see http://localhost:8088/static/assets/images/loading.gif returning 404.

Screenshots

Environment

• browser type and version: Chrome - Version 94.0.4606.61 (Official Build) (64-bit)
• superset version: Observed in docker images on both apache/superset:latest-dev (sha256:a430759eb60d3dc1ddf905eb5b3afdeccdd17c8ece7370c71901ed1b68f5fbbb) and apache/superset:latest (sha256:f7afd84becc688f239228b2460910e316c1e140baf943115c3eca1be00ef6ccc)
• python version: 3.8.12 (python verso=ion found in apache/superset:latest-dev image)
• node.js version: node:16 (sha256:ed7bbdf4d76e3083f22827edc444b061b6562cb08341be973bfde0a972b65272)(docker image)
• any feature flags active: not sure. nothing has been changed in code/config post cloning.

Checklist

Make sure to follow these steps 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

I have cloned the repo and used docker-compose to bring up the system. I can also see that containers superset_worker_beat, superset_worker to be unhealthy.

Superset app logs

127.0.0.1 - - [12/Oct/2021 18:00:24] "GET /health HTTP/1.1" 200 -
2021-10-12 18:00:24,588:INFO:werkzeug:127.0.0.1 - - [12/Oct/2021 18:00:24] "GET /health HTTP/1.1" 200 -
172.25.0.1 - - [12/Oct/2021 18:00:25] "GET / HTTP/1.1" 302 -
2021-10-12 18:00:25,596:INFO:werkzeug:172.25.0.1 - - [12/Oct/2021 18:00:25] "GET / HTTP/1.1" 302 -
2021-10-12 18:00:25,791:DEBUG:superset.stats_logger:[stats_logger] (incr) welcome
172.25.0.1 - - [12/Oct/2021 18:00:25] "GET /superset/welcome/ HTTP/1.1" 200 -
2021-10-12 18:00:25,818:INFO:werkzeug:172.25.0.1 - - [12/Oct/2021 18:00:25] "GET /superset/welcome/ HTTP/1.1" 200 -
2021-10-12 18:00:25,894:WARNING:superset.views.base:404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
172.25.0.1 - - [12/Oct/2021 18:00:25] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
2021-10-12 18:00:25,895:INFO:werkzeug:172.25.0.1 - - [12/Oct/2021 18:00:25] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -

[junlincc]

@Maannniii latest master, developer environment only, correct?

[Maannniii]

yes @junlincc the docker-compose was run from latest master branch with commit id c2e1ab6

Issue still persists. Checked again with latest code changes with commit id 959fd76. Checked on 01:13 AM UTC Wednesday, 13 October 2021

[manodupont]

Samething here ...
Running in dev, instead of non-dev, and this is always up.

[jomach]

+1 here

[sukupandachu]

+1 here too, installed yesterday and bumped into the same issue
Ubuntu server 20.04, Docker

Found this other thread with a solution that worked for me: #8818
docker-compose -f docker-compose-non-dev.yml up , suggested by @aseem-poloniex

[jomach]

I had the same issue. Wait for 10 or 15 minutes then npm has installed all packages. This is imho a bug

[maartenbreddels]

Docker didn't work for me, I checked out the docker/docker-frontend.sh script, and ran those commands manually. i.e.:

# get nodejs from conda-forge in my case
conda install -c conda-forge nodejs
cd superset-frontend
npm install -f --no-optional --global webpack webpack-cli
npm install -f --no-optional
npm run dev

My guess is some of the init scripts should have run this, but because nodejs is not installed it skipped it. I guess the installation docs can be improved on this.

[jasonoberme]

I had the same issue. Wait for 10 or 15 minutes then npm has installed all packages. This is imho a bug

Agree with this feedback. +1 for me.

[jasonoberme]

Docker didn't work for me, I checked out the docker/docker-frontend.sh script, and ran those commands manually. i.e.:

# get nodejs from conda-forge in my case
conda install -c conda-forge nodejs
cd superset-frontend
npm install -f --no-optional --global webpack webpack-cli
npm install -f --no-optional
npm run dev

My guess is some of the init scripts should have run this, but because nodejs is not installed it skipped it. I guess the installation docs can be improved on this.

To run these I had to first run:
export NODE_OPTIONS=--openssl-legacy-provider

[cdutr]

I am getting the same error here. After waiting around 20 min it finished installing and got an error with webpack installation, on superset_node:

superset_node | webpack 5.52.1 compiled with 48 errors and 9 warnings in 138433 ms

This is the kind of problem that discourages a lot of people who are having their first contact with the project following the tutorial. I would like to fix it, is anyone already working on it? Any suggestion on the best approach?

Comment: I didn't have this issue when running docker-compose-non-dev.yml.

[nikhil-kuyya-talentas]

can you share the logs of superset_node.

[nikhil-kuyya-talentas]

if you see something fail in the installation of packages like folder already or cannot install.
Try more removing node_modules working in superset_frontend.
I would suggest if we can skip getting node_modules coming to host volume of superset_frontend in deep folder places.
via docker volumes place.
Also if you see something related to CYPRESS INSTALL ISSUE
add this to environment : CYPRESS_CACHE_FOLDER='/app/.cache/Cypress'

[pa-mike]

Docker didn't work for me, I checked out the docker/docker-frontend.sh script, and ran those commands manually. i.e.:

# get nodejs from conda-forge in my case
conda install -c conda-forge nodejs
cd superset-frontend
npm install -f --no-optional --global webpack webpack-cli
npm install -f --no-optional
npm run dev

My guess is some of the init scripts should have run this, but because nodejs is not installed it skipped it. I guess the installation docs can be improved on this.

I had this same issue, running those node items solved my lockup on docker-compose. Looks like non-dev works fine, but the dev docker-compose has this challenge.

This is the kind of problem that discourages a lot of people who are having their first contact with the project following the tutorial. I would like to fix it, is anyone already working on it? Any suggestion on the best approach?

Agree this issue is a bit discouraging, requires getting your hands dirty.

[bhowmik23]

I think the problem was solve by following this steps:

1. Remove Node stage codes from Dockerfile
2. Remove node_modules from superset-frontend dir if exist
3. Run cd superset-frontend in cmd
4. Run npm install&&npm run dev
5. Run docker-compose up
   Hopefully it will be work

[muhsinfazal]

This worked for me docker-compose -f docker-compose-non-dev.yml up

[Paulo456]

if u have macos you can't use method above
the problem is in the image of the js node. To fix it, you need to fix version nodejs . to do that u need to fix file docker/docker-frontend.sh like this:
.....
apt install -y chromium
# add new strings
apt install -y npm
npm install npm -g
npm install -g n
n 16.18.1

n will install node js with version 16.18.1 . by the way npm also need some packages to start correctly

[SyakeerRahman]

This worked for me docker-compose -f docker-compose-non-dev.yml up. Thank you @sukupandachu

[krakzk]

How can we get this in dev, running docker-compose up?

[sfirke]

I'm closing this old issue as it pertains to a resolved issue from 2021-22 and even if a new version of this problem occurs in the future, it would have a different cause. Folks who experience something similar should please search for a newer issue and, if none exists, either post in the Superset Slack chat or create a new issue if you believe it's a new bug.

[avnav0]

I'm closing this old issue as it pertains to a resolved issue from 2021-22 and even if a new version of this problem occurs in the future, it would have a different cause. Folks who experience something similar should please search for a newer issue and, if none exists, either post in the Superset Slack chat or create a new issue if you believe it's a new bug.

i'm having this same exact issue...:
#24579 (comment)

[sfirke]

That doesn't seem like the same issue as this old one, your error code there is The CSRF session token is missing and there's no mention of CSRF in any of the posts on this issue. But I'm glad you found that issue, that one does seem like the right place to discuss the problem you're having.

[liisaxin]

changing the node verison to v16.9.1 can help u .
if the node's version is v19 or higher , it does not compile all file completely at superset-frontend.
u can install nvm package to change the node version to v16 .

[vaguptaqw]

i am facing the same issue as reported. i tried docker-compose -f docker-compose-non-dev.yml up it worked, but now while logging in using admin id, it does not go through. anyone help on this please.

[Captain404]

Same issue here...after battling to get the default creds issue resolved.

[lclerigues]

Docker didn't work for me, I checked out the docker/docker-frontend.sh script, and ran those commands manually. i.e.:

# get nodejs from conda-forge in my case
conda install -c conda-forge nodejs
cd superset-frontend
npm install -f --no-optional --global webpack webpack-cli
npm install -f --no-optional
npm run dev

My guess is some of the init scripts should have run this, but because nodejs is not installed it skipped it. I guess the installation docs can be improved on this.

did this, found 24 vulnerabilities

including malware?

did anyone else find this? should I worry?

[elburro1887]

Same issue here, just pulled the superset repo and ran docker as instructed in the docs:

git clone --depth=1 https://github.com/apache/superset.git
docker compose up

Went tohttp://localhost:8088/ -> logged in with admin:admin and got the following page:

Docker Logs say:

....
superset_app          | 2024-08-30 14:26:16,339:DEBUG:superset.stats_logger:[stats_logger] (incr) welcome
superset_app          | 2024-08-30 14:26:16,370:INFO:werkzeug:192.168.65.1 - - [30/Aug/2024 14:26:16] "GET /superset/welcome/ HTTP/1.1" 200 -
superset_app          | 2024-08-30 14:26:16,689:WARNING:superset.views.error_handling:HTTPException
superset_app          | Traceback (most recent call last):
superset_app          |   File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1484, in full_dispatch_request
superset_app          |     rv = self.dispatch_request()
superset_app          |   File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1469, in dispatch_request
superset_app          |     return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
superset_app          |   File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 502, in <lambda>
superset_app          |     view_func=lambda **kw: self_ref().send_static_file(**kw),  # type: ignore # noqa: B950
superset_app          |   File "/usr/local/lib/python3.10/site-packages/flask/scaffold.py", line 317, in send_static_file
superset_app          |     return send_from_directory(
superset_app          |   File "/usr/local/lib/python3.10/site-packages/flask/helpers.py", line 557, in send_from_directory
superset_app          |     return werkzeug.utils.send_from_directory(  # type: ignore[return-value]
superset_app          |   File "/usr/local/lib/python3.10/site-packages/werkzeug/utils.py", line 575, in send_from_directory
superset_app          |     raise NotFound()
superset_app          | werkzeug.exceptions.NotFound: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.

....

So im pretty sure this issue needs to be re-opened...

[ereztaiar]

I don't know if my solution is correct but what work for me is adding

apt install zstd

to docker_frontend.sh file before npm run dev
looks like simple-zstd requires it in the image
https://www.npmjs.com/package/simple-zstd

[rusackas]

I think #30279 intends to take care of any remaining zstd issues.