I am having errors on two different Rancher 2.2.6/2.2.7 installs creating a Slack Notifier - it’s probably worth a bug report - but I want to try to get to the bottom of it log-wise with better information for a bug report.
I have a single host Rancher Server running in docker a standalone hyper-v vm (homelab install) and a single host Rancher Server running in docker on a Digital Ocean droplet. Both are managing a separate rancher cluster.
Docker was docker-ce 18.09.8 with 2.2.6 and is now docker-ce 19.03.1 with 2.2.7.
In both platforms - trying to create a Slack notifier results in “Post https://hooks.slack.com/services/token: proxyconnect tcp: dial tcp :0: connect: connection refused”
I am new to Rancher. And while I’ve tried to do my due diligence digging through code to see if I see anything obvious - I don’t know where this test actually executes from - and where to get to the bottom of it logs wise (and no, as far as I can tell, creating it anyway still doesn’t work for the actual alerts).
I’ve had email and Pagerduty alerts both work.
My guess is that this might be a docker networking configuration error - or maybe the proxy configuration is not actually blank (I am not behind a proxy in either situation). But I don’t know where to begin to debug this.
Any and all pointers appreciated.