-
Notifications
You must be signed in to change notification settings - Fork 27
Getting a 502 bad gateway error #37
Comments
I see from docker-compose ps that the main cabot_app_1 has exited 1 -- so I guess I need to look into that first... |
Turns out I needed to comment out all the FIX_ME variables in cabot_env for the app_1 container to start properly! Makes sense ;) |
@surfacescan Just got into the same problem, thanks for the tip |
Maybe it is worth mentioning in the README so that others won't get into this problem |
@erez-rabih did you remove all the FIXME ? what if I don't want hipchat integration? |
@patovala I meant mentioning that you must change all the fix me comments on the file for the app to work. |
This one has bitten me too. I made a minor PR (#41) that just tells you to edit |
Hi guys, I'm installing this for the first time and I am having the above issue with the 502. I have changed the API information in the cabot_env file which I have added below:
I am only really looking to log into Cabot at the moment. Is there anything else I need to do in order to get this to work? I have also checked
This is a Linux VM with an IP of 192.168.1.14, so going to 192.168.1.14:8080 throws the 502. Do I have to restart or reinit a script at all? |
@dsgnr show your |
When accessing the http://server.address:8080/
Not sure if it is in the nginx.conf file?
The text was updated successfully, but these errors were encountered: