Support self-hosted hubots

[slackapi]

Support self-hosted hubots

[MZAWeb]

I'm having the exact same problem

[plukevdh]

same here.

[erunion]

From what I've seen, they need to be able to hit the Hubot URL in the integration config.

[plukevdh]

Is there anything magical needed to set that up? Just the ENV param?

[evansolomon]

You need a URL in the slack config. Slack hits your hubot server with post requests for each message, so it needs to be accessible from a URL.

I'm not really sure if I understand the question, particularly the "self hosted" description, but the URL but is definitely important.

[matt-oakes]

I have hubot with hubot-slack installed using dokku on our own publicly accessible server. I've tried setting the HEROKU_URL config variable, but that doesn't seem to help. Any idea?

[desmondmorris]

@evansolomon thanks for this. To be clear when I say self-hosted, I mean installed somewhere other than Heroku.

Can you give more details on what the POST payload to that URL looks like? My understanding is that hubot does not open any web accessible ports by default. What endpoint is slack hitting? What response is it expecting?

[desmondmorris]

As a test, I set the hubot url in the configuration options to a requestbin endpoint http://requestb.in/1gemf3r1?inspect.

After reloaded my hubot, I am not seeing any requests posted to the requestbin endpoint. Any ideas @evansolomon?

[MZAWeb]

Hubot's default port is 8080. Try your public ip / domain :8080

[desmondmorris]

@MZAWeb good call! Thanks, I will take a look.

[evansolomon]

Hubot runs an instance of Express, so all of the web server stuff is just an Express server. You can customize the port by setting the PORT env variable.

For an easy test, you should be able to hit /hubot/version and get a response with the hubot version you're running.

[evansolomon]

@matto1990 you don't need to set HEROKU_URL if you're not using Heroku. I think it's only used for pinging that URL on some interval to prevent dynos from sleeping.

[matt-oakes]

Thanks Evan. I read that after I posted. Still can't figure out why it
doesn't work on non-heroku installs though. It's definitely accessible from
the web and slack is point to the right URL.
On 28 Feb 2014 17:55, "Evan Solomon" [email protected] wrote:

@matto1990 https://github.com/matto1990 you don't need to set
HEROKU_URL if you're not using Heroku. I think it's only used for pinging
that URL on some interval to prevent dynos from sleeping.

Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-36376635
.

[matt-oakes]

I just solved this by making sure the URL in Slack has a slash after it. It
all works now!
On 28 Feb 2014 18:39, "Matt Oakes" [email protected] wrote:

Thanks Evan. I read that after I posted. Still can't figure out why it
doesn't work on non-heroku installs though. It's definitely accessible from
the web and slack is point to the right URL.
On 28 Feb 2014 17:55, "Evan Solomon" [email protected] wrote:

@matto1990 https://github.com/matto1990 you don't need to set
HEROKU_URL if you're not using Heroku. I think it's only used for pinging
that URL on some interval to prevent dynos from sleeping.

Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-36376635
.

[bdefore]

what would be the suggested configuration to run hubot on the same server that's running jenkins (which by default fires up jetty at 8080)? we use hubot to do some common engineering tasks on our ci machine.

[bdefore]

i was able to open up 8081 on my ec2 instance, set PORT=8081 as an env variable, restart hubot, and update my integration settings Hubot URL to http://ec2-xxx-xxx-xxx-xxx.us-west-1.compute.amazonaws.com:8081/ and now it's working

[desmondmorris]

I think I can put the fork in this one.

Thank you @MZAWeb @evansolomon @matto1990 for helping figure this out.

[matt-oakes]

Just a side note for @tinyspeck: it would be great if Slack could detect if you hadn't added the trailing slash and add one.

[stv-io]

hey guys, I'm currently setting this up in our env, and was thinking, perhaps @tinyspeck could help, what are the public IPs which we can whitelist from our firewall to connect through to the Hubot listener?

[clintmiller]

I've got a similar setup where I'm not hosting Hubot on Heroku. In the Slack Hubot integration, there is no field to enter a "Hubot URL." How is this supposed to work?

[gbougeard]

Hi, I have the same issue : I deployed a containerized hubot-slack on ec2 and it cannot connect to slack.
When I run the container on my machine, the connection is done and successful.
I think it does not work on EC2 beacuse my instance might be private but as I do not see any point about how hubot-slack and slack communicate, I don't get what I miss.
Btw, there is no more Hubot URL configuration in the Slack Hubot integration.

[evansolomon]

@gbougeard this sounds like a security group egress rule issue. The client connects to Slack by a websocket, so you need to make sure the server can access the internet (this is disabled in AWS by default I think since they switched to VPCs).

[gbougeard]

Yes I finally successfully configure my security groups.
Thanks

[memelet]

Configured the security exactly how? I have opened all egress ports to 0.0.0.0 and still cannot connect to slack.