-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
Default credential not working #10149
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
Its similar issue as |
Is there a reason this was closed? I'm still having this issue. |
@scook12 I could manage to fix this issue. If you run it in windows you will get an error. To fix it first run following |
Got it, thanks @SwapnilKhante! |
I do not agree this issue should be closed. The documents for Docker clearly state the user/password should be admin/admin. |
@simondmorias I agree. It does not work the way it is mentioned in official documentation. |
Hi all +1 should not be closed, the documentation doesn't mention this step Thanks @SwapnilKhante!! |
I still fail to get superset up on windows. I ran But I get the error ERROR: No container found for superset_1 edit: I did not realize that I need to run up first. If I do that no Error appears upon executing in a second terminal |
how exacly did you call it on windows? |
To init the user and roles
|
when trying to init the roles as @ToryZhou suggested I'm presented with the following error:
|
I am confirming @jessecbrown message, so to say the Docker image is currently useless. |
Same issue
|
I was having the same problem. I end up using their image: https://hub.docker.com/r/preset/superset/ with a custom extension as they point at the bottom of the page and it worked. |
I also have this issue. Followed the steps at https://superset.apache.org/installation.html#start-with-docker, the default login of admin/admin does not work (Get: "Invalid login. Please try again"). All 4 containers appear to be running after running docker-compose up. Environment: dos2unix docker-init.sh docker-compose exec superset bash /app/docker-init.sh |
Is everyone here on Windows? I mean, is this a docker-on-windows-specific issue? |
No same issue on Linux mint |
Ubuntu. |
Yep, I just ran a clean
I'll get a fix for this today :) |
I'm having this issue on macOS too. And this is after running dos2unix. |
This is fixed in master. Please make sure you are up to date and have cleared all of your images, containers and volumes. |
I just experienced this issue on windows after following the default instructions at https://superset.incubator.apache.org/installation.html by cloning the repo and running In my case, introspection of the superset_init image showed I explicitly replaced windows line endings in |
I just experienced this issue on ubuntu 18.04 starting from scratch. It looks like there's some kind of pyarrow dependency conflict in superset-init |
Hi all, I successfully installed superset two weeks ago on ubuntu 18.04. I'm now running into this admin user/pw issue on subsequent installs from the docker-compose method, on multiple local machines - Windows 10 and ubuntu 16.04 and 18.04 all running python 3.6 or 3.7. I get this error during the build: You can get to the login step but then the same error occurs. I've tried this on 4 different local machines today, two with the same specs as I have with the build that worked two weeks ago. Also, it appears the reference |
I just pushed a fix for this into master. Please pull the latest and try one more time. |
This is still a thing, updated to the latest version, same error message Invalid log in. Please try again. I was able to make it work on Windows:
Hope this helps someone. |
I have similar problem with the helm chart in K8s. One way to create user/or change password, is to log into the container and create admin user:
Of course this approach is not optimal as you have to do it manually and most importatntly after your container is recreated, the user is also lost if you are running the container in a stateless manner. The right way is to fix it in helm chart initialization. |
Hi, looks like the issue is fixed in master branch. Please git checkout master (don't checkout latest as per official document) and re-build again. You should be able to login as admin/admin. Thanks |
It's 2022 and:
|
It's half past 2022 and:
|
Hey guys, I just tried these steps:
What steps / output are you seeing? |
@craig-rueda thanks for the swift reply. sharing the steps I am trying on my machine.
|
Ah, steps are different :). Pls try the ones I outlined. We don't ship any default creds with the base image. The docker-compose stack includes an "init" container that does a bunch of setup (including the creation of the |
Hello @craig-rueda , I think a recent merge created multiple heads for alembic, a head merge might be needed. Below is output from the init container after following your steps above. Should I open a new issue for this?
|
Workaround: Run steps described in docker-init.sh ADMIN_PASSWORD="admin"
superset db upgrade
superset fab create-admin \
--username admin \
--firstname Superset \
--lastname Admin \
--email admin@superset.com \
--password $ADMIN_PASSWORD
superset init
superset load_examples --force |
What VPS configuration will be sufficient to run Superset? |
I was able to bypass the invalid credentials error by running |
I encountered the issue during the initial setup. After deleting the containers, images, and volumes, everything started working as expected. Btw I'm using linux/amd64. |
What a useless app...all that effort to install and the default creds dont work. I tried a all the methods here but still no go. Also giving up and will maybe come back when it actually works. |
This is my fault but WARNING! In case you are newish to docker or just not used to these kinds of commands these commands will nuke all your containers and images, not just superset. Just erased all containers running on my server, not fun. |
Also facing similar issue my instance was working but now I used the same image to build a separate instance and I can't log in @betodealmeida , Kindly help same issue as above on superset 3.1.1 and 3.1.0 |
This issue should be reopened, I've just run into the same issue with the latest Docker installed on Mac M2. |
@Carmageddon how did you install? |
I am still facing the issue - after creating flask fab user the browser goes in 'Internal server error' !!!! |
Seems like a different issue, any logs server side? Since this is issue is closed and this seems different, you may want to open a fresh new issue and fill the input form (logs, version, environment details...) |
I am running Superset in Kubernetes and when I am trying to enter the default login details it says 'Invalid login try again' so I tried above suggestion - #10149 (comment) and got the 'Internal server error 500' !! |
A clear and concise description of what the bug is.
Expected results
Successful login
what you expected to happen.
Actual results
Trying admin username and admin as password. Getting
Invalid login. Please try again.
what actually happens.
Screenshots
If applicable, add screenshots to help explain your problem.
How to reproduce the bug
Environment
(please complete the following information):
Running docker setup
The text was updated successfully, but these errors were encountered: