-
-
Notifications
You must be signed in to change notification settings - Fork 223
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
RealTime behind Proxy #110
Comments
So |
Thanks Daniel, I will give that a try, still a beginner in ruby, I'll try to find where to add some log lines. Sent from my iPhone
|
With basic
addr is set to a slack-msgs.com domain, and port is set to 443 at this point. |
It seems like faye-websocket supports proxies, documented in https://github.com/faye/websocket-driver-ruby#http-proxies. We instantiate the client here, so it just needs the right options exactly as you've been passing them in. So you might just be able to switch connection libraries to that and it will work. It's still a problem for celluloid-io, and I couldn't find anything on it, would you please ask https://groups.google.com/forum/#!forum/celluloid-ruby and follow up here? |
So I don't know if this helps but it helped me track down why this error is being raised. By commenting out that line of code I found it will tell you what might be blocking you. This showed me the following error when I was getting the same error as above. D, [2016-11-08T14:35:14.124152 #13119] DEBUG -- Slack::RealTime::Concurrency::Celluloid::Socket#connect!: WebSocket::Driver::Client
E, [2016-11-08T14:35:14.129978 #13119] ERROR -- : Actor crashed!
Errno::ECONNREFUSED: Connection refused - connect(2) for 52.87.151.152:443 Would be nice if it just raised connection refused error rather than Target thread must not be current thread |
Agreed @NewDark, that should be fixed independently, want to give it a shot? |
I have been trying to fix it I have not found a way yet but if I do I will make a pull request |
I mean getting a better exception would be a good start. |
Oh yeah can total do that |
I have been trying to do RTI slack client for sometime behind proxy server with no luck. I tried jslack - java APIs where I am able to do incoming webhooks. Please share code if you make it work. |
@atul2017 Proxy servers don't seem to be doing me any good as they tend to require a lot of work to get working with Web sockets. I would recommend trying to open up the ports for this domain name. wss://ms9.slack-msgs.com/websocket/1234567. The ms9 and so on changes per request and that can be a pain but some firewalls will let you do wildcards. That depends on how new they are and who is in charge of them. |
I think we still have an issue with proxies and RTM connections, so I'll reopen this. |
@dblock No problem, I was just cleaning up issues on projects we no longer use and won't be able to confirm any fixes on. |
Based on advise from slack-ruby/slack-ruby-bot#97 I have tested the hi_web example from behind my corporate firewall and it works without issue.
However the hi_real_time example does not, even when altered to include the proxy server in the configuration. Currently the only machines on the network with the proxy are headless, so I cannot test the normal Slack client either.
Am I configuring the proxy correctly here in this code?
Log:
hi.rb :
The text was updated successfully, but these errors were encountered: