Unable to login to new server?
See original GitHub issueRemoved the ~/.superset
directory multiple times, tried configuring postgres and redis also.
Expected results
Should be able to login.
Actual results
No errors in console or network tab, server log just says:
[2019-06-02 13:50:29 +0000] [20401] [INFO] Starting gunicorn 19.8.0
[2019-06-02 13:50:29 +0000] [20401] [INFO] Listening at: http://0.0.0.0:8080 (20401)
[2019-06-02 13:50:29 +0000] [20401] [INFO] Using worker: sync
[2019-06-02 13:50:29 +0000] [20406] [INFO] Booting worker with pid: 20406
Warning in console though:
Source map error: request failed with status 404
Resource URL: https://omitted/static/appbuilder/css/bootstrap.min.css
Source Map URL: bootstrap.min.css.map
Navigated to https://omitted/login/
Using //@ to indicate sourceMappingURL pragmas is deprecated. Use //# instead
jquery-latest.js:2:21
Source map error: request failed with status 404
Resource URL: https://omitted/static/appbuilder/js/jquery-latest.js
Source Map URL: jquery-1.10.2.min.map
Source map error: request failed with status 404
Resource URL: https://omitted/static/appbuilder/css/bootstrap.min.css
Source Map URL: bootstrap.min.css.map
Screenshots
If applicable, add screenshots to help explain your problem.
How to reproduce the bug
- Follow this guide https://superset.incubator.apache.org/installation.html#superset-installation-and-initialization
- Setup postgres
- Setup redis
- Setup config
Environment
(please complete the following information):
- superset version:
$ superset --version Flask 1.0.2 Python 3.6.7 (default, Oct 22 2018, 11:32:17) [GCC 8.2.0]
257c100c5966c431abf19f6e813842aef8e588b5 - node.js version:
v10.16.0
- npm version:
6.9.0
Checklist
Make sure these boxes are checked 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
/etc/nginx/sites-enabled/omitted from code example
server {
server_name omitted from code example;
listen 80;
return 301 https://$server_name$request_uri;
}
server {
server_name omitted from code example;
listen 443;
ssl on;
ssl_certificate /etc/letsencrypt/live/omitted from code example/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/omitted from code example/privkey.pem;
fastcgi_param HTTPS on;
fastcgi_param HTTP_SCHEME https;
location / {
proxy_buffers 16 4k;
proxy_buffer_size 2k;
proxy_pass http://0.0.0.0:8080;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_http_version 1.1;
proxy_connect_timeout 600;
proxy_read_timeout 600;
send_timeout 600;
}
}
superset_config.py
import os
from werkzeug.contrib.cache import RedisCache
MAPBOX_API_KEY = os.getenv('MAPBOX_API_KEY', '')
CACHE_CONFIG = {
'CACHE_TYPE': 'redis',
'CACHE_DEFAULT_TIMEOUT': 300,
'CACHE_KEY_PREFIX': 'superset_',
'CACHE_REDIS_HOST': 'redis',
'CACHE_REDIS_PORT': 6379,
'CACHE_REDIS_DB': 1,
'CACHE_REDIS_URL': 'redis://localhost:6379/1'}
SQLALCHEMY_DATABASE_URI = \
'postgresql+psycopg2://omitted from code example:omitted from code example@localhost:5433/superset_db'
SQLALCHEMY_TRACK_MODIFICATIONS = True
SECRET_KEY = 'omitted from code example'
class CeleryConfig(object):
BROKER_URL = 'redis://localhost:6379/0'
CELERY_IMPORTS = ('superset.sql_lab', )
CELERY_RESULT_BACKEND = 'redis://localhost:6379/0'
CELERY_ANNOTATIONS = {'tasks.add': {'rate_limit': '10/s'}}
CELERY_CONFIG = CeleryConfig
RESULTS_BACKEND = RedisCache(
host='redis',
port=6379,
key_prefix='superset_results'
)
/etc/circus/conf.d/circus.ini
[circus]
check_delay = 5
endpoint = tcp://127.0.0.1:5555
pubsub_endpoint = tcp://127.0.0.1:5556
statsd = true
[watcher:supserset]
working_dir = /home/ubuntu/repos/incubator-superset
cmd = gunicorn
args = superset:app
uid = ubuntu
numprocesses = 1
autostart = true
send_hup = true
stdout_stream.class = FileStream
stdout_stream.filename = /home/ubuntu/repos/logs/supserset.stdout.log
stdout_stream.max_bytes = 10485760
stdout_stream.backup_count = 4
stderr_stream.class = FileStream
stderr_stream.filename = /home/ubuntu/repos/logs/supserset.stderr.log
stderr_stream.max_bytes = 10485760
stderr_stream.backup_count = 4
virtualenv = /opt/venvs/superset
virtualenv_py_ver = 3.6
copy_env = true
[env:supserset]
TERM=rxvt-256color
SHELL=/bin/bash
USER=ubuntu
LANG=en_US.UTF-8
HOME=/home/ubuntu/repos
PORT=8080
SERVER=gunicorn
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
reasons for not able login to a server - TechNet - Microsoft
1.Connectivity issue with DC due to dns misconfig. · 2.Account lockout or in disable state. · 3.DC unreaachable due physical connectivity issue.
Read more >[SOLVED] Unable to login to server locally or RDP
All of a sudden, our Windows Server 2008 will not allow me to login using the admin account (it is the only account...
Read more >Cannot Connect to Server: How to Connect to Company Server
1. Restart Your Computer · 2. Follow the Error Messages · 3. Identify Where the Shared Drive is Hosted · 4. Permissions ·...
Read more >Resolving “Unable to login to database server” on Workstations.
The following Unable to login to database server message usually occurs when something is blocking Microsoft SQL Server connections between your workstation ......
Read more >Unable to login at server: suddenly happening to an existing ...
Unfortunately, the ISP advised us to delete our TB accounts and create a new one to overcome whatever the problem was. Sadly 2...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sounds like we need versioned docs…
This is a different problem, can you please close it. For this new question, search if it’s already answered and if not open a new one.