Error on a fresh ubuntu installation
snorberhuis opened this issue · comments
I tried to use the install scripts on a fresh vm running ubuntu server 14.04 and I tried using docker (guide in #3).
But both result in a page stating:
"Something happened and our Oompa Loompas are working on it.
Try reloading again soon."
I also tried to look for ways to read any logs that Taiga produces to see what the error is, but I cannot seem to find any. If you could point me in the right direction I could either fix it myself or give a better bug report.
I really want to try Taiga as it seems to fit my needs perfectly. Any help would be appreciated.
Did you follow my instructions? What does your console say? If you're not browsing from the same place you're hosting it you may encounter issues (I did - the api server was not exposed to the world). I ended up having to use socat to forward requests.
Seems something related to hostname and how you are access to the virtual machine.
In any case, I recommend use taiga-vagrant, because it configures everything that needed (including port redirections) for test and deploy it in small "production" environment.
Maybe helpful:
I had similar issues with getting Taiga up and running: I set up a KVM machine with Ubuntu 14.04 Server, created some user, cloned the deployment scripts and ran the setup-server.sh script with the default options. Ports 80, 8000 and 8001 were exposed.
In Firefox I was getting a login form. The default credentials were rejected though.
In Chromium I didn't get a login form, instead I got the same error message like snorberhuis. The developer console yielded OPTIONS http://localhost:8000/api/v1/projects net::ERR_CONNECTION_REFUSED.
In my case I was able to solve the problem by deleting the ~/.setup, ~/taiga-back and taiga-front directories and running setup-server.sh again, this time I used the LAN IP address instead of localhost. It works like a charm now.
I'm not sure though, whether all references to localhost are replaced with the LAN IP now, since there are still components in ~/.npm.
In any case the described approach should work with a fresh VM.
Congratulations to the team: Taiga looks quite promising already, this was quite some work for sure! :)
Hi! @jotbe
Thanks you very much for you feedback.
localhost should be used if you want test it on local and external ip address, if you are using it out of virtual machine.
I tried it again. During installation I filled in the ip that I found using docker inspect. I still get the same error. How can I look at the developer console to give you guys more detailed feedback?
If you want to work in docker, have a look at #3
The one I've posted has instructions more easily ported to running on a single server, the one bameda posted is closer to the 'docker way'.
I get the same issue as @jotbe when I use the vagrant install. I am able to browse via localhost:8000 but when others use my ip @ http://ipaddress:8000 they get the Taiga error page.
Hi @pdnellius
taiga consists in two pieces of code, one runs on server and other runs on your browser. On step new installation you should indicate that is the public ip should be used for taiga-front. By default (with taiga-scripts and taiga-vagrant is set tu localhost:8000. It means that any one access to it through other ip, the taiga-front (browser part of application) will try connect to localhost:8000.
For make it accessible to outside your machine you should fix the taiga-front api url (http://taigaio.github.io/taiga-doc/dist/setup-production.html#_final_steps)
The documentation of how to setup production environment can help you: http://taigaio.github.io/taiga-doc/dist/setup-production.html
I close this issue because it is not a bug. If you have more questions, please use the mailing list: http://groups.google.com/d/forum/taigaio
Why does that URL need to be configured at all? Can't it just be relative: /api/v1/...
You are completelly right. The current config, is designed for get it run frontend in different domain of backend. But for basic installation, is obvioulsy not necesary the comple host and scheme for the url.
Thank you for your suggestion. I will fix it in the next release of taiga-scripts, also with reprovisioning support.
Unable to login to taiga post successful installation admin 123123 is not working
@awasekhirni any info in your javascript console?
After Successful Taiga Installation admin 123123 is not working.
Error: Something happened and our Oompa Loompas are working on it.
@sairaj3 please write to https://groups.google.com/forum/#!forum/taigaio for setup support and give us more info: what SO?? taiga-back is runing??, logs files, browser console errors,...
Guys not sure if this is solved already.
I ran under this problem and spent 1 day time [1 time investment though].
First is it looks like DNS problem to access taiga hostname from network lan[external to taiga server host/host outside taiga].
Example.
If DNS you picked is registed in network DNS entries then no problem - clients know where to connect for dns hostname [you used on conf files].
If NOT - temporary DNS name used for Taiga server then each clients[outside taiga server - local lan] to be added with hosts entry to know where to connect with front-dist libraries[java script].
Resolution for Non LAN DNS Entry usage for Taiga server:
Add below host entry
192.168.17.39 taiga.tejas.com
Linux: in your /etc/hosts File
Windows: in your C:\Windows\System32\Drivers\etc\hosts or relative file based on OS version
Root cause Seems to Be the logs found in firebug.
[But these problem not occurs immediately takes time by the time you would have completely reinstalled your taiga! I let the browser in firebug mode for more time and captured below exception related to internal dns lookup fails from client browsers.]
Firebug Logs - Captured After say 30 minutes of idle client browser:
Firefox can't establish a connection to the server at ws://taiga.tejas.com/events.
app.js (line 2, col 18537)
WebSocket error: [object Event]
libs.js (line 11)
Firefox can't establish a connection to the server at ws://taiga.tejas.com/events.
app.js (line 2, col 18537)
The connection to ws://taiga.tejas.com/events was interrupted while the page was loading.
Duplicated from https://github.com/taigaio/taiga-front/issues/367