Hot Summer Deals are Here!
Celebrate with up to 90% off on 16,800 resources
04
Days
05
Hours
30
Mins
56
Secs

Images not loading

Status
PebbleHost
High performance, consistent uptime and fast support. Minecraft hosting that just works.

Jayson

Supreme
Feedback score
17
Posts
1,258
Reactions
741
Resources
0
For some reason some of the images on my post are not working anymore, it works fine on spigot and s*ngoda but not on here

https://www.mc-market.org/resources/17144/
The error has been fixed, thank you. The error was attributed to an oversized file cache resulting in the inability to process additional images. We have since determined a solution to prevent this same issue from occurring in the future.

same, both my threads fail to show the images instead it shows
Yep, same is happening with me for my signature, threads and everyone else. It just says

As for these, the error is caused by a bad image URL. Looking at the image link provided, your BBCode was [IMG]http://[/IMG] and [IMG]http://.[/IMG] respectively.

Please see the below. If you are unable to troubleshoot why your image URLs are not accepted by us, please create a ticket.

In most cases, the link provided to us is simply incorrect. For example, this Imgur link (https://imgur.com/a/3rpyv5U) is invalid because it does not go directly to the actual image, but instead HTML. The actual source should be https://i.imgur.com/quJHupt.png. As a general test, just visit the URL and see if it is just the image or if there is a frame around it. Note that in some very rare cases, image hosts may check the referrer and decide on their own on whether to display just the image or add the wrapper, but I would not recommend this.

In other cases, we may get blocked by the image host such as if the host is using Cloudflare and trying to block bots.

We do not accept self signed SSL certificates, however, we do accept hosts that do not have SSL certificates at all. This is a common issue for hosts using cPanel issued SSL certificates.

In many cases, the content type can be incorrect and thus the request is aborted. For instance, we may get an "image" content type instead of "image/jpeg" and thus it will not go through. I have seen this occur for some people using Amazon S3 which can easily be fixed via the AWS Management Console.

A popular error is people using proxy URLs which are not permitted. Always try and get the direct URL. This can be extracted from the proxy URL. For instance, https://proxy.mc-market.org/b7a0f6295eb0e230a4a2145a4c59d924bedba63a?url=https%3A%2F%2Fi.imgur.com%2FquJHupt.png should be https://i.imgur.com/quJHupt.png which is a decoded portion of the url portion of the query string.

Especially with larger thread designs and with the trend of animations, requests may be aborted because they are simply too big! (Seriously...I have seen a 300MB thread design, but the thread author broke it up into chunks so that the visitor had to load it all up and it was not blocked by us) Try and make your thread designs as small as possible in file size (check the Content-Length response header) to make your thread as accessible as possible. Really consider if a slide in is actually necessary...it just makes it harder to read for users and especially with header sliders where the viewer has to wait to finish reading the text. You are just annoying them.

We do not permit PHP files as images unless the extension is changed. Note that if you are making a "woah your IP is ____, buy our VPN" ad, it will not work. This is regardless of the content type you set as we simply check the URL for a `.php`.

If a post author requires assistance with repairing a broken image which renders fine in their browser and they have verified that our proxy is not being blocked, please create a ticket with the proxy link generated.
 
Last edited:

Mick

BuiltByBit Owner
Management
Feedback score
28
Posts
6,411
Reactions
7,662
Resources
0
The error has been fixed, thank you. The error was attributed to an oversized file cache resulting in the inability to process additional images. We have since determined a solution to prevent this same issue from occurring in the future.
Thanks Jayson :blobheart:

I'll move this to the bug report archives.
 
Status
Top