Admin Registration Issue / Login Page right after installation

I’ve installed redash 9.0.0 successfully.
By this guide: https://redash.io/help/open-source/dev-guide/setup

after running * ./manage.py runserver --debugger --reload
have an access to http://localhost:5000
and after npm install run
to http://localhost:8080/.

Note: Why ignored the post???

but here is log-in page in both screens, not an installation-page(initial page - admin registration).

so which email/password is needed to be used to enter to the system?
maybe there are some scripts to run to create admin user?
by the way, on postgres/users table has no rows.

How strange! I haven’t seen this one before and I’m not sure I have much help with the information provided. In your case I would probably re-asses the whole setup:

Are you certain you’re looking in the right users table? A fresh installation should always show the setup screen. If a login page is shown instead the application must be looking at a database somewhere with a users table.

For good measure: how did you install Redash? Are you using Docker or something else?

It is an installation to local machine (Mac), without docker.
By this guide: https://redash.io/help/open-source/dev-guide/setup
Everything looks good, no red-messages/errors.
But there is not installation page…

Before that I have tried docker installation(redash 8.0.0), installation page was appeared.

python=3.6, pip install results:

Successfully installed Flask-1.1.1 Flask-Limiter-0.9.3 Flask-Login-0.4.1 Flask-Migrate-2.5.2 Flask-OAuthLib-0.9.5 Flask-RESTful-0.3.7 Flask-SQLAlchemy-2.4.1 Jinja2-2.10.3 Mako-1.1.4 MarkupSafe-1.1.1 PyAthena-2.1.1 PyJWT-1.7.1 PyYAML-5.1.2 RestrictedPython-5.0 SQLAlchemy-1.3.10 SQLAlchemy-Searchable-0.10.6 SQLAlchemy-Utils-0.34.2 alembic-1.5.3 aniso8601-8.0.0 argh-0.26.2 atomicwrites-1.4.0 attrs-20.3.0 bcrypt-3.2.0 blinker-1.4 boto3-1.10.50 botocore-1.13.50 cffi-1.14.4 chardet-3.0.4 click-6.7 coverage-4.5.4 croniter-1.0.5 cryptography-2.8 decorator-4.4.2 defusedxml-0.6.0 disposable-email-domains-0.0.64 dnspython-1.16.0 docutils-0.15.2 flask-mail-0.9.1 flask-talisman-0.7.0 freezegun-0.3.12 funcy-1.13 future-0.18.2 gevent-1.4.0 greenlet-1.0.0 gunicorn-19.9.0 httplib2-0.14.0 idna-2.8 importlib-metadata-3.4.0 importlib-resources-1.5.0 itsdangerous-1.1.0 jmespath-0.10.0 jsonschema-3.1.1 limits-1.5.1 maxminddb-2.0.3 maxminddb-geolite2-2018.703 mock-3.0.5 more-itertools-8.6.0 natsort-7.1.1 oauthlib-2.1.0 packaging-20.9 paramiko-2.7.2 parsedatetime-2.4 passlib-1.7.1 pathtools-0.1.2 pluggy-0.13.1 psutil-5.8.0 psycopg2-2.8.3 ptvsd-4.3.2 py-1.10.0 pyOpenSSL-19.0.0 pycparser-2.20 pycrypto-2.6.1 pymongo-3.9.0 pynacl-1.4.0 pyparsing-2.3.0 pypd-1.1.0 pyrsistent-0.17.3 pysaml2-4.8.0 pystache-0.5.4 pytest-5.2.1 pytest-cov-2.8.1 python-dateutil-2.8.0 python-editor-1.0.4 pytz-2020.5 redis-3.3.11 requests-2.21.0 requests-oauthlib-1.1.0 rq-1.1.0 rq-scheduler-0.9.1 s3transfer-0.2.1 semver-2.8.1 sentry-sdk-0.14.4 simplejson-3.16.0 six-1.15.0 sqlparse-0.3.0 sshtunnel-0.1.5 statsd-3.3.0 supervisor-4.1.0 supervisor-checks-0.8.1 tenacity-6.3.1 typing-extensions-3.7.4.3 ua-parser-0.8.0 urllib3-1.24.3 user-agents-2.0 validators-0.18.2 watchdog-0.9.0 wcwidth-0.2.5 werkzeug-0.16.1 wtforms-2.2.1 xlsxwriter-1.2.2 zipp-3.4.0

I found the reason. We have two variables: current_org and settings.MULTI_ORG
settings.MULTI_ORG = False
current_org = Default(1), so not None.

Code inside “setup.py” for /setup handler:

if current_org != None or settings.MULTI_ORG:
    return redirect("/")

It looks like, it is a bug. How fix that?
How current_org can have value right after Redash installation?
Or if it is ok, then it needs to change code on setup at least.

I doubt you need to change any code as this exact set of steps works fine for most other users. It would be interesting to emit a print() or logging statement to see which org Redash thinks has been configured, however.

It is done already. I dropped the database, and created again.
Problem here was, somehow organization row was inserted to database until initial-setup.

Now another question is actual for me. How to change front-end (React) on fly and to see changes on localhost:8080?
For now localhost:5000 and localhost:8080 look like the same. So my changes on /client folder (React files) do not affect app.

Proxy is created → http://localhost:5000/ (8080 is listening to 5000?)
I’m changing /redash/templates/login.html content for testing purpose, but nothing changes on 8080 port…

Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
[HPM] Proxy created: [
‘/login’,
‘/logout’,
‘/invite’,
‘/setup’,
‘/status.json’,
‘/api’,
‘/oauth’
] → http://localhost:5000/
[HPM] Proxy created: [Function: context] → http://localhost:5000/
:information_source: 「wds」: Project is running at http://localhost:8080/
:information_source: 「wds」: webpack output is served from /static/
:information_source: 「wds」: 404s will fallback to /static/index.html
Successfully compiled 145 files with Babel.