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
Getting 404 error from WS URL in RTMClient#start() with aiohttp 3.7.0 or lower versions #912
Comments
@mgtech-sydney I guess the default SSL version in Python 3.6.7 on Windows OS may be a bit old. Can you try the following code out? import logging
logging.basicConfig(level=logging.DEBUG)
import ssl
from slack_sdk.rtm import RTMClient
# Use this specific SSL version
ssl_context = ssl.SSLContext(ssl.PROTOCOL_SSLv23)
token = "xoxb-***"
RTMClient(token=token, ssl=ssl_context).start() |
Hi @seratch - output from running the above below, no change in the error. I also ran this on python:3.7-alpine docker image and got the same result.
|
Can you check the OpenSSL version you are using? You can check the version by printing |
I'm getting this too, from an ubuntu bionic container:
I am using Python 3.7.5 and OpenSSL 1.1.1:
Adding in |
I got the same error since last night(01/11), without modifying any code. Maybe it's a slack server error? |
I am using Python 3.7 and docker environment and the same error occurs but I cannot find the cause. Is it an error on the slack server? |
We are sorry for the disruption. I have been trying to reproduce the situation on my end. However, I haven't managed to see the error with my classic apps yet. We would like to figure out if this is specific to this SDK or Python runtime first. It would be greatly appreciated if anyone could help us identify the conditions. What happens if you try to connect using the same classic bot token with If the issue occurs with Node SDK too, we will communicate to the server-side teams an closely work with them. If this happens only with this Python SDK, I will continue looking at the steps to reproduce. |
I am having the same problem here as everyone using the RTMClient. I am using Python 3.7 and my RTM chatbot was working up until about 1 hour ago. |
I got the same error since about 3-4 hours ago. |
me too |
Same problem. Python 3.6, OpenSSL 1.1.1. Looks like there may be a lot of us. Perhaps we should switch to 👍 on the post if we have no new info to add? |
@seratch I'm not familiar with node, i try to do the following steps:
and there‘s no output or error with correct token. If I set a wrong token, it raise an |
I see the same problem since couple of hours. |
2 similar comments
I see the same problem since couple of hours. |
I see the same problem since couple of hours. |
My bot started experiencing the same issue at 6:45pm PST and has not been able to re-connect since. Python 3.6.8 |
For those of you experiencing this issue, we'd like to know if you are (👍) or are not (👎) using the |
@jvperrin and @mgtech-sydney did you both redact the URL on the last line of this stack trace, or is this the exact URL you saw? if you redacted it, given that those URLs expire within 10 mins, they would no longer be dangerous to share. and just being cautious, if you'd like to email me (ankur @ slack-corp dot com), seeing those URLs might be helpful to our investigation.
|
Hi @aoberoi The below is a URL from our production environment (Alpine:Python3.7) which saw the error.
I can generate the error / URL locally in a Windows environment if that would help you as well. |
@aoberoi we are seeing the same thing just started in the last 3 hours. No proxy that I am aware of.
|
this worked for me - thanks very much |
For me also. Thanks. |
Confirming the aiohttp upgrade works. I was on 3.6.2, upgraded to 3.7.3 and everything started working again. |
we just deployed a new release upgrading slackclient from v2.7.3 to v2.9.3 and it seems to be working now. |
Working for me too after aiohttp upgrade. Thanks for the help! |
Upgrading aiohttp worked for me too. Thanks a lot! |
Upgrading to aiohttp-3.7.3 and slackclient-2.9.3 fixed the issue. Thanks a ton. [slackbot@xxxxslackbot]$ pip3 install -U aiohttp --proxy http://x.x.x:8888 --user slackbot [slackbot@xxxx slackbot]$ |
Saving me. SAVING ME!!!! aiohttp-3.7.3 |
@seratch I am still getting the same error even after upgrading aiohttp and slackclient. Could someone help?
|
@hkonala The stacktrace indicates that your app still loads aiohttp v3.6 |
@seratch it is saying opsdroid 0.19.0 requires slackclient==2.6.2 and aiohttp==3.6.2
During handling of the above exception, another exception occurred:
|
@hkonala I am sorry to say that, in your case, there is no workaround until the issue is fixed on the server-side. I cannot tell the exact timing of the deployment, but they will resolve this early tomorrow, Pacific Time. Again, we are sorry for the disruption. |
@seratch Thanks for the info!! will wait for the fix :) |
Upgraded to aiohttp==3.7.3 and it works |
What is the status of the fix? |
Install aiohttp, work for me too! |
A freaking heads up from slack sure would had been nice. They sure have interrupted business a lot lately. |
For anyone else running into this that isn't using aiohttp, it appears this was the change to aiohttp that made the difference. If your client implementation sends any capitalization other than In my case, I patched autobahn here: https://github.com/crossbario/autobahn-python/blob/master/autobahn/websocket/protocol.py#L3576 |
According to the server-side teams, no apps should be experiencing this issue now. We apologize for the inconvenience and appreciate your patience. |
Yes @seratch .. Things seem to be working fine now. |
RTMClient.start() failing as of 2021-01-09. Connection attempted with both slack_sdk and (legacy) slackclient.
The Slack SDK version
slack-sdk 3.1.1
(Also occuring on slackclient 2.9.3)
Python runtime version
Python 3.6.7
OS info
Microsoft Windows [Version 10.0.18362.1256]
Steps to reproduce:
Testing via https://api.slack.com/methods/rtm.connect/test is successful with the same token as used when running code sample above.
Actual result:
The text was updated successfully, but these errors were encountered: