Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bot is not connected #15

Closed
elliotslab opened this issue Jun 9, 2015 · 4 comments
Closed

bot is not connected #15

elliotslab opened this issue Jun 9, 2015 · 4 comments

Comments

@elliotslab
Copy link

When I the docker image the output is

[Tue Jun 09 2015 15:41:01 GMT+0000 (UTC)] INFO running rocketchat
[Tue Jun 09 2015 15:41:01 GMT+0000 (UTC)] INFO login

I try creating a user bot and rocketbot but is still not working

this are my configs

_meteorurl = "192.168.0.11:3000"
_hubotuser = "rocketbot"
_hubotpassword = "demodemo"
_roomid = "57om6EQCcFami9wuT"

to run the container I copy/paste the same command from inside the clones repo

@Sing-Li
Copy link
Member

Sing-Li commented Jun 9, 2015

@oinirio it seems you may not have access to that IP address from inside the running container.

While container running and stuck at login, in another shell - try:

docker exec -i -t  <container id>   bash

This will run a shell inside the container. Then troubleshoot using ping.
You can get the running container-id by:

docker ps

If you're running native docker on Linux, there should be no problem. But if you are on a Mac or PC and running docker inside the boot2docker VM - then try using 192.168.59.103:3000 for _meteorurl instead (assuming you're also running Rocket.Chat on the host machine).

@elliotslab
Copy link
Author

@Sing-Li I'm running openSuse and the ping works from inside the container to my LAN by running

docker inspect <container id>

I got the container internal IP and the ping works from localhost -> container

@Sing-Li
Copy link
Member

Sing-Li commented Jun 9, 2015

@oinirio Did "ping 192.168.0.11" worked from INSIDE the container (not using inspect) ?

Did you turn the default firewall off?

@elliotslab
Copy link
Author

@Sing-Li My bad was the firewall actually, it's working now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants