schungx
(Stephen Chung)
7. Januar 2019 um 05:08
1
Not sure what happened, but after upgrading to the latest beta, all custom user avatars are gone, replaced by a standard image of a light-gray user.
The default-generated avatars for users with no custom avatar uploads are not affected.
The image links to those avatars are:
https://xxxxx.com/user_avatar/xxx.com/user/50/179_2.png
EDIT: Uploading a new avatar image will show up. Therefore, all the previously-uploaded avatar images are all lost.
No, it just takes time for the images to re-optimize. See the other topic on this. Give it 24 hours.
5 „Gefällt mir“
schungx
(Stephen Chung)
7. Januar 2019 um 05:23
3
I suppose you mean this one:
Not sure if something you changed with the fuzzy image loading is being applied to user profile pictures, but I’ve noticed that after upgrading to 2.2.0.beta7 quite a few user images are either failing to load entirely (leaving just an empty white space) or are loading very, very slowly.
As seen here: https://share.otf.ca/
I’ll keep my fingers crossed for 24 more hours…
bletch
(Danny Goodall)
7. Januar 2019 um 06:37
4
Yep, had the same issue after upgrade. 15 mins later the avatars were back.
3 „Gefällt mir“
Let us know if it is still an issue.
schungx
(Stephen Chung)
7. Januar 2019 um 14:24
6
Half a day now and still the default pics…
schungx
(Stephen Chung)
8. Januar 2019 um 03:39
7
Nope. It doesn’t go back to normal. All the avatars are still the default pics.
Any command line to manually rebuild them?
sam
(Sam Saffron)
8. Januar 2019 um 04:05
8
How is your sidekiq queue looking? Is it empty?
There is some nginx level caching if queue is empty go ahead and rebuild
schungx
(Stephen Chung)
8. Januar 2019 um 04:09
9
Looks empty.
How should I rebuild? Do a “./launcher rebuild app”?
sam
(Sam Saffron)
8. Januar 2019 um 09:12
10
Quote avatars becoming default is probably due to:
FIX: always serve new avatar for previous version Previously we killed caching on old avatars cause we kept serving blank this meant we would front many more avatar requests after a version change This change ensures all old avatars do not cause...
Reading time: 1 mins 🕑
Likes: 4 ❤
Added bonus, stuff will run faster as well. Let me know how it goes.
4 „Gefällt mir“
schungx
(Stephen Chung)
8. Januar 2019 um 09:31
11
Well, unfortunately, I did a ./launcher rebuild app
and it is still showing the default pic.
So that’s not it.
Version is v2.2.0.beta7 +60
sam
(Sam Saffron)
8. Januar 2019 um 10:10
12
what is an example URL of a broken avatar? I want you to try some things.
1 „Gefällt mir“
sam
(Sam Saffron)
8. Januar 2019 um 11:25
14
Sorry , I need the url on your site I want you to adjust numbers there to diagnose what is up
3 „Gefällt mir“
Hi,
If you need an example, I have the same problem on my site:
By the way, I experience another problem with links of pictures from Imgur or Flickr. The display is broken after 15 minutes and replaced by an unreachable item icon.
The installed version is v2.2.0.beta7 +42
sam
(Sam Saffron)
8. Januar 2019 um 23:28
17
If you edit loliver4’s profile and open the avatar selection screen, do you see it there? Is it using a local avatar or a gravatar?
Can you run
./launcher enter app
rails c
Upload.find(3262)
Is the file it is referencing in your file system? What is the size of the file?
Something is not right here…
Also seeing a redirect here:
http://libertysim.s3.dualstack.eu-west-3.amazonaws.com/original/2X/a/a5fce085968b65330ee85eec7ea8aac9aa2af9fa.jpeg
Did you move your S3 stuff around?
2 „Gefällt mir“
sam
(Sam Saffron)
9. Januar 2019 um 10:15
20
This particular topic is a bug in azure blob storage plugin, @vinothkannans is looking at it.
1 „Gefällt mir“
gauthier
(gauthier)
9. Januar 2019 um 10:32
21
Hi
[1] pry(main)> Upload.find(3262)
=> #<Upload:0x0000564ef0da8a00
id: 3262,
user_id: 2858,
original_filename: "13962749_845715052226788_5249706654812763874_n.jpg",
filesize: 60477,
width: 360,
height: 360,
url: "//libertysim.s3.dualstack.eu-west-3.amazonaws.com/original/2X/7/71d87b34609aec9e248e7f9739daf0f970ac5a67.jpeg",
created_at: Sun, 06 Jan 2019 05:30:22 UTC +00:00,
updated_at: Sun, 06 Jan 2019 05:30:22 UTC +00:00,
sha1: "71d87b34609aec9e248e7f9739daf0f970ac5a67",
origin: nil,
retain_hours: nil,
extension: "jpeg",
thumbnail_width: 360,
thumbnail_height: 360,
etag: "\"8cb513f4b9899fa26bb7de856c935c59\"">
No special change on S3 was done…
S3 response
<Error>
<Code>PermanentRedirect</Code>
<Message>
The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
</Message>
<Endpoint>libertysim.s3.dualstack.eu-west-2.amazonaws.com</Endpoint>
<Bucket>libertysim</Bucket>
<RequestId>5353DFE7A14AB123</RequestId>
<HostId>
QDQ3mKgq95kH92AloN1gH+LwGIgP9FWq77ck5yHVKSoIXx14nqiGN3u5gjOwxegfd9zVb7nN0J4=
</HostId>
</Error>
As per the above response from S3 if I change the hostname to libertysim.s3.dualstack.eu-west-2.amazonaws.com
then the URL is working. I’m not sure how it’s messed up. But it doesn’t look like a problem from Discourse side.
http://libertysim.s3.dualstack.eu-west-2.amazonaws.com/original/2X/a/a5fce085968b65330ee85eec7ea8aac9aa2af9fa.jpeg
3 „Gefällt mir“