Something happened and our Oompa Loompas are working on it.

3,336 views
Skip to first unread message

bmr...@gmail.com

unread,
Oct 7, 2014, 3:42:45 PM10/7/14
to tai...@googlegroups.com
after using taigo-scripts on a digital ocean instance I go to 
and it shows the login screen for  a second then goes to an error page 
that says

Something happened and our Oompa Loompas are working on it.
Try reloading again soon.

Take me home


I tried again 5 minutes later and got the same.
How long do these Oompa Loompas take?




marcel...@gmail.com

unread,
Oct 7, 2014, 5:07:17 PM10/7/14
to tai...@googlegroups.com, bmr...@gmail.com
I have the same problem, when looking at the developer console I can see the following

Initialize navigation urls libs.js?v=1412714854130:9
Initializing configuration Object {host: "localhost:8000", scheme: "http", debug: true, defaultLanguage: "en", languageOptions: Object…} libs.js?v=1412714854130:9
Initialize api urls libs.js?v=1412714854130:9
Initialize resources libs.js?v=1412714854130:9
Initialize application libs.js?v=1412714854130:9
XHR finished loading: GET "http://10.0.0.26/partials/projects.html". libs.js?v=1412714854130:9
XHR finished loading: GET "http://10.0.0.26/partials/login.html". libs.js?v=1412714854130:9
OPTIONS http://localhost:8000/api/v1/projects net::ERR_CONNECTION_REFUSED libs.js?v=1412714854130:9
FAIL app.js?v=1412714854130:2
XHR finished loading: GET "http://10.0.0.26/partials/error.html". libs.js?v=1412714854130:9
Uncaught TypeError: Cannot read property 'opacity' of null jquery.js:2
Uncaught ReferenceError: jQuery is not defined colorpicker.js:397
Uncaught ReferenceError: jQuery is not defined jquery.tipsy.js:216
Uncaught ReferenceError: jQuery is not defined selectize.js:9
Uncaught ReferenceError: $ is not defined init.js:4
OPTIONS http://localhost:8000/api/v1/projects net::ERR_CONNECTION_REFUSED 

 And if I look at the network tab it tries to load http://localhost:8000/api/v1/projects but that fails. When I try to go to that page directly it works but gives an empty array.

I installed it on a fresh install of Ubuntu 14.04.1 on which I installed ssh and git-core before downloading and running the setup-server.sh script

marcel...@gmail.com

unread,
Oct 7, 2014, 5:11:25 PM10/7/14
to tai...@googlegroups.com, bmr...@gmail.com, marcel...@gmail.com
After further looking into it, it looks like it tries to load the api on the localhost, but the I am trying to connect to it from a different computer in the network so localhost isn't the correct location.
If I use the correct server location and than api/v1/projects it works but of course not on localhost.

Andrey Antukh

unread,
Oct 7, 2014, 5:21:01 PM10/7/14
to marcel...@gmail.com, tai...@googlegroups.com, bob mross
Hi!

Yes, this can happens if on intial configuration questions you are leave them with default values. The default values makes service work on localhost, and you are trying access to the service from outside.
Try modify the taiga-front/app/config/main.coffee and put here the correct values for `host` attribute. In your case  10.0.0.26 seems the correct value. After modifying it, run `gulp deploy` in taiga-front directory for apply the changes.

Greetings.
Andrey

2014-10-07 23:11 GMT+02:00 <marcel...@gmail.com>:
After further looking into it, it looks like it tries to load the api on the localhost, but the I am trying to connect to it from a different computer in the network so localhost isn't the correct location.
If I use the correct server location and than api/v1/projects it works but of course not on localhost.

--
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+u...@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/2900ceef-47e6-48b6-8967-3605375bdda6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--

bmr...@gmail.com

unread,
Oct 7, 2014, 6:31:29 PM10/7/14
to tai...@googlegroups.com, bmr...@gmail.com
in ~/taiga-front/app/config/main.coffee file I changed 
host: "localhost:8000"
to 

I then ran gulp deploy from the ~/taigo-front   directory and the problem still persisist
dev console shows

Initialize navigation urls libs.js?v=1412718863881:9
Initializing configuration Object {host: "localhost:8000", scheme: "http", debug: true, defaultLanguage: "en", languageOptions: Object…} libs.js?v=1412718863881:9
Initialize api urls libs.js?v=1412718863881:9
Initialize resources libs.js?v=1412718863881:9
Initialize application libs.js?v=1412718863881:9
OPTIONS http://localhost:8000/api/v1/projects net::ERR_CONNECTION_REFUSED libs.js?v=1412718863881:9
FAIL app.js?v=1412718863881:2
OPTIONS http://localhost:8000/api/v1/projects net::ERR_CONNECTION_REFUSED libs.js?v=1412718863881:9

I even rebooted and still the same

Do I have to do anything beyond gulp deploy to get the changes in place?

bmr...@gmail.com

unread,
Oct 7, 2014, 6:38:30 PM10/7/14
to tai...@googlegroups.com, bmr...@gmail.com
I edited the ~/taiga-front/dist/js/app.js directly and changed all "localhost" to ip address then rebooted.
I can log in as admin but cant change the password, clicking on the blue user preference button does nothing




On Tuesday, October 7, 2014 1:42:45 PM UTC-6, bmr...@gmail.com wrote:

Andrey Antukh

unread,
Oct 7, 2014, 6:39:31 PM10/7/14
to bob mross, tai...@googlegroups.com
Very very strange, gulp deploy should reflect these changes.

--
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+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

bmr...@gmail.com

unread,
Oct 7, 2014, 6:43:59 PM10/7/14
to tai...@googlegroups.com, bmr...@gmail.com
it did output lines of doing stuff, but app.js did not get changed.

my current problem is that I cant change the admin password, 
hovering over the blue user preference button does not change the cursor and clicking does nothing.
how do I change the password from a shell console?


On Tuesday, October 7, 2014 1:42:45 PM UTC-6, bmr...@gmail.com wrote:

bmr...@gmail.com

unread,
Oct 7, 2014, 6:46:33 PM10/7/14
to tai...@googlegroups.com, bmr...@gmail.com
I am going to open a new topic on the admin password problem


On Tuesday, October 7, 2014 1:42:45 PM UTC-6, bmr...@gmail.com wrote:

Andrey Antukh

unread,
Oct 7, 2014, 6:47:17 PM10/7/14
to bob mross, tai...@googlegroups.com
2014-10-08 0:43 GMT+02:00 <bmr...@gmail.com>:
it did output lines of doing stuff, but app.js did not get changed.

my current problem is that I cant change the admin password, 
hovering over the blue user preference button does not change the cursor and clicking does nothing.
how do I change the password from a shell console?

You can change pasword so:

cd taiga-back
workon taiga
python manage.py changepassword admin


Changing so the compiled file is not really recommended.
Sorry for not helping much with this issue, each environment is different and taiga-scripts it is still in alpha. It is tested in isolated environment and is not prepared for maintain update the instance with latest changes.
We are currently working on full documentation of how to correctly deploy taiga on production, and it will be available soon.


Thanks again for your patience.

Greetings.
Andrey


On Tuesday, October 7, 2014 1:42:45 PM UTC-6, bmr...@gmail.com wrote:
after using taigo-scripts on a digital ocean instance I go to 
and it shows the login screen for  a second then goes to an error page 
that says

Something happened and our Oompa Loompas are working on it.
Try reloading again soon.

Take me home


I tried again 5 minutes later and got the same.
How long do these Oompa Loompas take?




--
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+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

bailey...@gmail.com

unread,
Oct 8, 2014, 10:45:00 PM10/8/14
to tai...@googlegroups.com, bmr...@gmail.com
So I changed the app run on my domain name and edited app.js from localhost to my domain name. The login screen loads, but when I enter the admin creds I get a connection timeout. I know that it's authenticating becuase when I go to reload it immediately goes from the login to projects page, or trys to anyways. Any help would be appreciated. I'm not seeing anything in the logs that indicates a connection timeout.

Andrey Antukh

unread,
Oct 9, 2014, 2:25:21 PM10/9/14
to tai...@googlegroups.com
Sorry but without more information I don't know that is happens. 
Are you sure that in developer tools console of chrome/chromium/firefox nothing is happens?

Modifying app.js is very bad approach.

This is a work in progress, step by step installation process documentation, that maybe can help you find the source of your problem: http://taigaio.github.io/taiga-doc/dist/setup-production.html

Greetings.
Andrey



--
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+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Andrey Antukh

unread,
Oct 9, 2014, 2:34:31 PM10/9/14
to tai...@googlegroups.com
One note about the documentation: the documentation is build thinking in the next taiga release, and some things are not directly compatible(A great example is a taiga-front configuration that is changed to more readable format (json))

Bailey Ammons

unread,
Oct 11, 2014, 4:27:15 PM10/11/14
to tai...@googlegroups.com
So it turns out that the problem was on my end. However, when I run the server-setup script and set the default url, to my domain app.js retains localhost in its api/v1 and events. So the deployed app.js file still needs to be manually edited.
Message has been deleted

sch...@btaftp.com

unread,
Dec 18, 2014, 10:48:29 PM12/18/14
to tai...@googlegroups.com, marcel...@gmail.com, bmr...@gmail.com
Has this config file changed?  I've tried deploying taiga several ways on a fresh Ubuntu 14 image - docker, manual install, install scripts, and have never gotten the front end and back to communicate.  I don't see a config directory under taiga-front/app:

taiga@exectech-4:~/taiga-front/app$ ll
total 52
drwxrwxrwx 12 taiga taiga 4096 Dec 18 18:18 ./
drwxrwxrwx 10 taiga taiga 4096 Dec 18 18:19 ../
drwxrwxrwx  3 taiga taiga 4096 Dec 18 18:16 coffee/
drwxrwxrwx  2 taiga taiga 4096 Dec 18 18:16 fonts/
drwxrwxrwx  3 taiga taiga 4096 Dec 18 18:16 images/
-rwxrwxrwx  1 taiga taiga 1626 Dec 18 18:16 index.jade*
drwxrwxrwx  2 taiga taiga 4096 Dec 18 18:16 js/
drwxrwxrwx  3 taiga taiga 4096 Dec 18 18:16 locales/
drwxrwxrwx  3 taiga taiga 4096 Dec 18 18:16 partials/
drwxrwxrwx  4 taiga taiga 4096 Dec 18 18:16 plugins/
drwxrwxrwx 10 taiga taiga 4096 Dec 18 18:16 styles/
drwxrwxrwx  2 taiga taiga 4096 Dec 18 18:16 svg/
drwxrwxrwx 30 taiga taiga 4096 Dec 18 18:18 vendor/

I was getting a gunicorn error error that 0.0.0.0:1 was in use, trying in one second, in the gunicorn.stderr.log (I think that was the port).  I deleted the log file so I could be sure that error was still there and restarted, but no new log file was written. I touched to create a new one, and then chown it back to root, and even chmod 777 everything in ~ to make sure permissions weren't the problem, but I don't see anything written to those log files - just the oompa loompa error.  (The VM is on a blade in another room, not my machine).

Dev tools:

 OPTIONS http://localhost:8000/api/v1/projects net::ERR_EMPTY_RESPONSE
app.js?v=1412607293885:2 FAIL
libs.js?v=1412607293885:9 XHR finished loading: GET "http://171.71.112.201/partials/projects.html".
libs.js?v=1412607293885:9 XHR finished loading: GET "http://171.71.112.201/partials/error.html".

Looks like it's not pointed properly at the backend; when I did manual installs I changed the config files mentioned but still had problems, hence my wondering if this main.coffee needs to be changed somewhere.  Ideally would want it setup to automatically serve off whatever the VMs IP is.

Thanks,

Shayne Hodge

Alejandro Alonso

unread,
Dec 22, 2014, 4:27:50 AM12/22/14
to sch...@btaftp.com, tai...@googlegroups.com, marcel...@gmail.com, bmr...@gmail.com
Hello Shayne,

Your config file should be one level upper -> ~/taiga-front/main.json . You could write this file basing on ~/taiga-front/main.example.json 

Regards,


--

  
Alejandro Alonso Fernández  
CIO & Co-founder

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