-
Notifications
You must be signed in to change notification settings - Fork 694
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
Avatar External Provider URL is not working on versions later than 3.2.4 #2231
Comments
On web browser this dont happens? Seems like a server issue to me. |
It doesn't happen on Web Browser. I am able to see Avatars on Web version. |
Would you mind in sharing with me the URL that you used? |
The Avatar URL I am using is hosted on a local IP and the URL is mapped in my Windows host file. So the URL is not accessible outside the network. You can use any online image URL like this one: https://www.winhelponline.com/blog/wp-content/uploads/2017/12/user.png It will show same avatar for all the users but you can test the broken avatar with this at least. |
I couldnt reproduce the problem here. Could you test with our newest release? |
I am sorry. It turned out that my SSL had expired and that was causing this issue. But I am not sure that how it was working fine with older versions even with the expired SSL certificate. |
Describe the bug
When I set the
Avatar External Provider URL
from Administrator area and refresh the RocketChat client, the avatars are all broken.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The avatars should be loaded from the provider's URL
Screenshots
Administration side:
![Screenshot_235](https://user-images.githubusercontent.com/1608798/141875329-57841631-e432-40ef-919f-6aed910dd8c0.png)
Client side:
![Screenshot_234](https://user-images.githubusercontent.com/1608798/141875338-62d0fef5-3ebc-4442-9b6e-61c046ecfd70.png)
Additional context
I have tested version by version. It's working perfectly fine till 3.2.4 and not working on any later version.
The text was updated successfully, but these errors were encountered: