admin login not workin after following developement install instructions

85 views
Skip to first unread message

alexande...@googlemail.com

unread,
Jul 22, 2017, 5:16:45 AM7/22/17
to taigaio
Hi all,

i installed taiga.io on my local debian wheezy, usual pc with 16Gb Memory (no virtual machine) following install for debian-wheezy and comparing to production-mode-installation
not yet activating https login - i thought it would be good to check if everything works before takin the next step.
So far, installation seemed to works fine (no errors during the python manage.py xxx calls).

The only difference is that I'm not using
systemctl start circus
but (as root)
/usr/local/bin/circusd /home/taiga/conf/circus.ini


When I browse to 127.0.0.1 or localhost, I see taiga, but when trying to login as admin with 123123 i get an error ( username/email or password are incorrect.)
When I try to register as new user and hit the sign in button, nothing happens.

See my config files below.

Firefox's developer console gives shows the following error:
downloadable font: kern: Too large subtable, table discarded (font-family: "OpenSans-Regular" style:normal weight:normal stretch:normal src index:0) source: http://127.0.0.1/v-1495549531419/fonts/OpenSans-Regular.ttf  theme-taiga.css:4:13093
Initialize navigation urls  libs.js:11:28183
Initialize api urls  libs.js:11:28183
Using the default logging exception handler.  libs.js:11:28183
Initialize resources  libs.js:11:28183
Initialize application  libs.js:11:28183
Analytics: no acount id provided. Disabling.  libs.js:11:28183
Error: A network error occurred.
Oe/<@http://127.0.0.1/v-1495549531419/js/libs.js:11:20645
g@http://127.0.0.1/v-1495549531419/js/libs.js:11:18645
d/c@http://127.0.0.1/v-1495549531419/js/libs.js:11:16931
a@http://127.0.0.1/v-1495549531419/js/libs.js:12:3271
s/<@http://127.0.0.1/v-1495549531419/js/libs.js:12:3443
xn/this.$get</p.prototype.$eval@http://127.0.0.1/v-1495549531419/js/libs.js:12:10956
xn/this.$get</p.prototype.$digest@http://127.0.0.1/v-1495549531419/js/libs.js:12:9460
xn/this.$get</p.prototype.$apply@http://127.0.0.1/v-1495549531419/js/libs.js:12:11241
k/u<@http://127.0.0.1/v-1495549531419/js/libs.js:12:7437
o@http://127.0.0.1/v-1495549531419/js/libs.js:10:21869
ue/c.defer/n<@http://127.0.0.1/v-1495549531419/js/libs.js:10:23328
 libs.js:11:28183
downloadable font: kern: Too large subtable, table discarded (font-family: "OpenSans-Light" style:normal weight:normal stretch:normal src index:0) source: http://127.0.0.1/v-1495549531419/fonts/OpenSans-Light.ttf  theme-taiga.css:4:12999
downloadable font: kern: Too large subtable, table discarded (font-family: "OpenSans-Semibold" style:normal weight:normal stretch:normal src index:0) source: http://127.0.0.1/v-1495549531419/fonts/OpenSans-Semibold.ttf


Browsing the postgres database, I see 62 tables,
in users_user I have (at row 5):
"5";"pbkdf2_sha256$10000$oRIbCKOL1U3w$/gaYMnOlc/GnN4mn3UUXvXpk2Hx0vvht6Uqhu46aikI=";"2013-04-04 09:36:09.88+02";TRUE;"admin";"ad...@admin.com";TRUE;"Administrator";"''";"''";"''";"2013-04-01 15:48:21.711+02";"''";"''";FALSE;"''";"";"";FALSE;"''";;;;

so it seems the admin user should be ok.

Any hints how to further debug this?
thx
Alexander

--------------------------
 ~/taiga-back/settings/local.py
========================
from .common import *

MEDIA_URL = "localhost/media/" 
STATIC_URL = "localhost/static/" 
ADMIN_MEDIA_PREFIX = "localhost/static/admin/" 
SITES["front"]["scheme"] = "http" 
SITES["front"]["domain"] = ".local"

SECRET_KEY = "theveryultratopsecretkey"

DEBUG = True 
TEMPLATE_DEBUG = False 
PUBLIC_REGISTER_ENABLED = True

DEFAULT_FROM_EMAIL = "no-r...@example.com
SERVER_EMAIL = DEFAULT_FROM_EMAIL

# Uncomment and populate with proper connection parameters 
# for enable email sending. EMAIL_HOST_USER should end by @domain.tld 
#EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend" 
#EMAIL_USE_TLS = False 
#EMAIL_HOST = "localhost" 
#EMAIL_HOST_USER = "" 
#EMAIL_HOST_PASSWORD = "" 
#EMAIL_PORT = 25

# Uncomment and populate with proper connection parameters 
# for enable github login/singin. 
#GITHUB_API_CLIENT_ID = "yourgithubclientid" 
#GITHUB_API_CLIENT_SEC



~/taiga-front-dist/dist/conf.json
========================
{
    "api": "localhost:8000/api/v1/",
    "eventsUrl": null,
    "eventsMaxMissedHeartbeats": 5,
    "eventsHeartbeatIntervalTime": 60000,
    "eventsReconnectTryInterval": 10000,
    "debug": true,
    "debugInfo": false,
    "defaultLanguage": "en",
    "themes": ["taiga"],
    "defaultTheme": "taiga",
    "publicRegisterEnabled": true,
    "feedbackEnabled": true,
    "privacyPolicyUrl": null,
    "termsOfServiceUrl": null,
    "maxUploadFileSize": null,
    "contribPlugins": [],
    "tribeHost": null,
    "importers": [],
    "gravatar": true
}




~/conf/circus.ini
========================


[circus] 
check_delay = 5 
endpoint = tcp://127.0.0.1:5555 
pubsub_endpoint = tcp://127.0.0.1:5556 
statsd = true

[watcher:taiga] 
working_dir = /home/taiga/taiga-back 
cmd = gunicorn 
args = -w 3 -t 60 --pythonpath=. -b 127.0.0.1:8001 taiga.wsgi 
uid = taiga 
numprocesses = 1 
autostart = true 
send_hup = true 
stdout_stream.class = FileStream 
stdout_stream.filename = /home/taiga/logs/gunicorn.stdout.log 
stdout_stream.max_bytes = 10485760 
stdout_stream.backup_count = 4 
stderr_stream.class = FileStream 
stderr_stream.filename = /home/taiga/logs/gunicorn.stderr.log 
stderr_stream.max_bytes = 10485760 
stderr_stream.backup_count = 4

[env:taiga] 
PATH = /home/taiga/.virtualenvs/taiga/bin:$PATH 
TERM=rxvt-256color 
SHELL=/bin/bash 
USER=taiga 
LANG=en_US.UTF-8 
HOME=/home/taiga 
PYTHONPATH=/home/taiga/.virtualenvs/taiga/lib/python3.4/site-packages



/etc/nginx/sites-available/taiga
========================

server { 
    listen 80 default_server;
    server_name _;

    large_client_header_buffers 4 32k;
    client_max_body_size 50M;
    charset utf-8;

    access_log /home/taiga/logs/nginx.access.log;
    error_log /home/taiga/logs/nginx.error.log;

    # Frontend
    location / {
        root /home/taiga/taiga-front-dist/dist/;
        try_files $uri $uri/ /index.html;
    }

    # Backend
    location /api {
        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme $scheme;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://127.0.0.1:8001/api;
        proxy_redirect off;
    }

    # Django admin access (/admin/)
    location /admin {
        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme $scheme;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://127.0.0.1:8001$request_uri;
        proxy_redirect off;
    }

    # Static files
    location /static {
        alias /home/taiga/taiga-back/static;
    }

    # Media files
    location /media {
        alias /home/taiga/taiga-back/media;
    }
}






David Barragán

unread,
Jul 23, 2017, 3:18:35 PM7/23/17
to alexande...@googlemail.com, taigaio
Review the response of the calls yo the api in the browser console. It seems that you are using a bad api (taiga-back) url in the configuration (conf.json) of you client (taiga-front). Change "localhost:8000/api/v1/" to "localhost/api/v1/".


Regards

--
Please help us keep the Taiga.io Community open and inclusive, follow our Code of Conduct:
https://github.com/taigaio/code-of-conduct/blob/master/CODE_OF_CONDUCT.md
---
You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+unsubscribe@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/895d48d6-c9a1-49db-9c71-a0c5e70f961c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

---

 
David Barragán Merino  
Engineer

www.kaleidos.net/FFF8E7
Reply all
Reply to author
Forward
0 new messages