A large percentage of Niconico thumbnails on all of the live websites are not loading correctly, despite loading correctly in the past. Previously, this behavior would only occur when trying to fetch thumbnails of deleted videos. This bug is seemingly less than 12 hours old.
By sorting through various searches, it becomes clear that there is a cutoff point right in the middle of 2019, prior to which most Niconico embeds are unreliable. Example of search results on top of the date cutoff. (Note that if an entry fetches a thumbnail from a different embed, it will still work correctly.) There are some entries created after this cutoff affected by the bug (example 1, example 2), as well as older entries that are unaffected (example), but these are exceptions.
In the browser console, the following message is generated for each failed thumbnail: The resource at “[url]” was blocked by OpaqueResponseBlocking. Reason: “after sniff: status code is not in allowed range”. Trying to open the image in a new tab may either fail to redirect to the thumbnail (displaying Http/1.1 Service Unavailable) or directly show an "Access Denied" message at the thumbnail's URL.
Deleting and re-adding the PV in a single edit is enough to successfully re-fetch the thumbnail for that entry. Tested here.
It seems like the thumbnail domain tn.smilevideo.jp doesn't work anymore. We might need to migrate to https://nicovideo.cdn.nimg.jp/thumbnails/<video_id>/<video_id>
Website
VocaDB / UtaiteDB / TouhouDB
Describe the bug
A large percentage of Niconico thumbnails on all of the live websites are not loading correctly, despite loading correctly in the past. Previously, this behavior would only occur when trying to fetch thumbnails of deleted videos. This bug is seemingly less than 12 hours old.
By sorting through various searches, it becomes clear that there is a cutoff point right in the middle of 2019, prior to which most Niconico embeds are unreliable. Example of search results on top of the date cutoff. (Note that if an entry fetches a thumbnail from a different embed, it will still work correctly.) There are some entries created after this cutoff affected by the bug (example 1, example 2), as well as older entries that are unaffected (example), but these are exceptions.
In the browser console, the following message is generated for each failed thumbnail: The resource at “[url]” was blocked by OpaqueResponseBlocking. Reason: “after sniff: status code is not in allowed range”. Trying to open the image in a new tab may either fail to redirect to the thumbnail (displaying Http/1.1 Service Unavailable) or directly show an "Access Denied" message at the thumbnail's URL.
Deleting and re-adding the PV in a single edit is enough to successfully re-fetch the thumbnail for that entry. Tested here.
Checklist
Safari,Edge).and cookies.