I’m trying as hard as I can!!!
1 Like
nice. works on some computers and not others. how the hell do indiafnose that lol.
brb
URL for that image begins: goa-uploads.s3.ca-east-006.backblazeb2.com/original/
URL for the link to that post begins: community.goactuary.com/t/
I have a memory, possibly false, of some corporate internet filters taking issue with backblazeb2.com links…?
1 Like
OK i have a failed image right? SOme folks can’t see this?
https:/uploads/default/original/3X/8/f/8fd99c2b58a0cd4e6de6f796c0a506bdbf8ab2cd.jpeg
but can you point me to an image that you can see? So that I can distinguish?
and someone who can’t see images doing this would be helpful:
Open the forum, find a broken image
Open browser DevTools (F12) → Console tab, and → Network tab
Reload the page
Find the failed image request (it’ll be red in the Network tab) and tell you: the exact error message and the status code
And this is temporary. when we were on a virtual machine, space was costly so we hiked images over to a cheap image server. We migrated, and are still using that system for now. But shortly we’ll have all the images back hosted on our servers so the problem should go away.
Insert complaint about hosting 30g+ of meme images. I have to materially plan backups around this lol.
I’m going to need a “this opinion is shit but I’m not allowed to say that so you get this emoji instead” reaction.
5 Likes
like this??
1 Like
Since post counts don’t matter here, 
emoji would be welcome, but it’s probably what’s just prebuilt in.
1 Like
I cannot view the image in your post here . . . and when I click on the link in this quoted post, I get to my employer’s Net Nanny page saying that access to the site is restricted:
[redacted] has restricted access because filtering software indicates this site may contain information or material that is inappropriate for use or viewing by [redacted] employees, associates, agents, or agent team members.
I can see this one:
But not this one:
I picked these two because they’re from the same poster posted quite close together in time.
Request URL: https:/uploads/default/optimized/1X/…_32x32.png (I opted not to get the full hash of the file)
Status Code: 403 Forbidden
Referrer Policy: strict-origin-when-cross-origin
Response headers (Raw):
HTTP/1.1 403 Forbidden
Content-Type: text/html
Server: Zscaler/6.2
Cache-Control: no-cache
Access-Control-Allow-Origin: *
Content-length: 24686
When I filter to “3rd-party requests” All of the 403 items are associated with backblaze.
Thanks boss! that confirms it’s corporate firewalls, and confirms that moving the images to our own servers (which is happening today) will correct the problem. I appreciate the assist.
2 Likes
Making an example of me, eh!!?!?!
1 Like
I still can’t see this one as an example: Republicans Say the Darndest Things! - #10359 by now_samantha
What I think is now the final resolution.
- 120,000 images (yeah, you guys) moved over.
- All images now served from this website, so images should get past the corporate firewalls that were blocking some of the images.
- 5 images posted during a specific timeframe, now lost. That’s just because I was sloppy during the move. I could’ve been careful but that would’ve cost me more hours and that’s the tradeoff I made. Folks can repost them if they like, but I’m pretty sure they’re just more memes.
And unless someone has other errors, I think that’s a wrap. We should be complete migrated off of the web over to our own hardware in Toronto now. I’ll let things set a bit, then i’ll shut down all the external hosting we have.
4 Likes
I can confirm that the images I could NOT see earlier (even within this thread!) are now visible to me on my work computer.
Many thanks to our crustacean overlords!!
1 Like
I still can’t see this one on work PC.
I can’t see that one on my non-work PC.