Start.me Comic | Render Problems

[Pathduck]

@VivaLaUSA Looks like either StartMe's content delivery network provider has problems, or the problem lies on your network provider's DNS.

You have the wrong IP address for images.weserv.nl

$ nslookup images.weserv.nl
Server:         192.168.0.1
Address:        192.168.0.1#53

Non-authoritative answer:
Name:   images.weserv.nl
Address: 104.21.234.186
Name:   images.weserv.nl
Address: 104.21.234.187
Name:   images.weserv.nl
Address: 2606:4700:3038::6815:eaba
Name:   images.weserv.nl
Address: 2606:4700:3038::6815:eabb

$ nslookup cdg.weserv.nl
Server:         192.168.0.1
Address:        192.168.0.1#53

Non-authoritative answer:
Name:   cdg.weserv.nl
Address: 51.15.191.75
Name:   cdg.weserv.nl
Address: 2001:bc8:6005:122:ae1f:6bff:fe21:58f2

When I make the request, the IP address is the correct 104.21.234.186 shown in the devtools network headers as:
Remote Address: 104.21.234.186:443
Your headers output does not have the remote address, maybe you didn't copy it.

I'd try the same commands I did in the command prompt.

I'd also try clearing the OS DNS cache, first closing the browser and then doing a:
ipconfig /flushdns

The DNS host cache can also be cleared in the browser at:
chrome://net-internals/#dns

[VivaLaUSA]

@Pathduck said in Start.me Comic | Render Problems:

This 200 OK code means the request to the image resource was successful. This is NOT the same as in your original images where you showed the resource was blocked by ORB.

That error wasn't for "Headers" specifically - it is what I get from "Network" data in general. I was told to not be concerned about this and instead concentrate on my "Headers" data (which is a better way to get to the bottom of the issue).

Is your actual "Headers" data the same as mine (that I posted previously specifically regarding "Headers")?

[Pathduck]

@VivaLaUSA said in Start.me Comic | Render Problems:

which is a better way to get to the bottom of the issue

No the best way is to save a HAR file and share it with support. If they know their jobs they'd know what to do with it.

Is your actual "Headers" data the same as mine (that I posted previously specifically regarding "Headers")?

I get a 200 OK like you (obviously).
And like I said you clearly did NOT get a 200 OK the first time with those image, the request failed.
But there's a lot of stuff missing from your headers, so I suspect you didn't copy all of it properly.

Here are my headers:

Request URL: https://images.weserv.nl/?t=fit&a=attention&dpr=1.5&il=1&q=85&page=0&w=600&h=1200&url=ssl%3A64.media.tumblr.com%2Fcc8ef8aecab597c3334974541403d9a0%2F3419b01804c8e91c-47%2Fs640x960%2F4d1533ccec664e40ce10c3ffe823fff57f7f277e.gif
Request Method: GET
Status Code: 200 OK
Remote Address: 104.21.234.186:443
Referrer Policy: no-referrer
accept-ranges: bytes
access-control-allow-origin: *
age: 9596
alt-svc: h3=":443"; ma=86400
cache-control: public, max-age=31536000
cf-cache-status: HIT
cf-ray: 8f009e1aba06caa9-HAM
content-disposition: inline; filename=image.gif
content-length: 33750
content-type: image/gif
cross-origin-resource-policy: cross-origin
date: Tue, 10 Dec 2024 22:19:38 GMT
expires: Wed, 10 Dec 2025 14:08:14 GMT
last-modified: Tue, 10 Dec 2024 14:08:14 GMT
link: <https://64.media.tumblr.com/cc8ef8aecab597c3334974541403d9a0/3419b01804c8e91c-47/s640x960/4d1533ccec664e40ce10c3ffe823fff57f7f277e.gif>; rel="canonical"
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=tvg8YPVp0SFt5ipcIbvjBdnQ0vERIYNqF%2BED2xhX7%2Fulmdp48sw%2F3dEUscV%2BuE%2BBngfAgHOQ6Zvpd%2F1kKg5EwoW2dsZ%2BaWHYXmSX9BMlO6R5zzIyZ7nzTeXUXqJ1O3ICDsay"}],"group":"cf-nel","max_age":604800}
server: cloudflare
server-timing: cfL4;desc="?proto=TCP&rtt=13447&min_rtt=13376&rtt_var=5067&sent=6&recv=7&lost=0&retrans=0&sent_bytes=3708&recv_bytes=1268&delivery_rate=327452&cwnd=129&unsent_bytes=0&cid=0270f072bef5c322&ts=37&x=0"
strict-transport-security: max-age=31536000; includeSubDomains; preload
timing-allow-origin: *
vary: Accept-Encoding
x-cache-status: MISS
x-content-type-options: nosniff
x-images-api: 5
x-upstream-response-length: 40772
:authority: images.weserv.nl
:method: GET
:path: /?t=fit&a=attention&dpr=1.5&il=1&q=85&page=0&w=600&h=1200&url=ssl%3A64.media.tumblr.com%2Fcc8ef8aecab597c3334974541403d9a0%2F3419b01804c8e91c-47%2Fs640x960%2F4d1533ccec664e40ce10c3ffe823fff57f7f277e.gif
:scheme: https
accept: image/avif,image/webp,image/apng,image/svg+xml,image/*,*/*;q=0.8
accept-encoding: gzip, deflate, br, zstd
accept-language: en-GB,en-US;q=0.9,en;q=0.8
cache-control: no-cache
pragma: no-cache
priority: u=1, i
sec-ch-ua: "Chromium";v="130", "Google Chrome";v="130", "Not?A_Brand";v="99"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Windows"
sec-fetch-dest: image
sec-fetch-mode: no-cors
sec-fetch-site: cross-site
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36

[VivaLaUSA]

Just to make sure I was posting the correct "Headers" data:

Request URL:
https://images.weserv.nl/?t=fit&a=attention&dpr=1&il=1&q=85&page=0&w=600&h=1200&url=ssl%3A64.media.tumblr.com%2Fcc8ef8aecab597c3334974541403d9a0%2F3419b01804c8e91c-47%2Fs640x960%2F4d1533ccec664e40ce10c3ffe823fff57f7f277e.gif
Request Method:
GET
Status Code:
200 OK
Referrer Policy:
no-referrer
cache-control:
max-age=2678400
cf-cache-status:
DYNAMIC
cf-ray:
8f00c7382b56ab86-SJC-PIG
content-encoding:
zstd
content-type:
text/html
date:
Tue, 10 Dec 2024 22:47:42 GMT
expires:
Fri, 10 Jan 2025 22:47:42 GMT
last-modified:
Fri, 06 Dec 2019 14:14:41 GMT
server:
cloudflare-nginx
vary:
Accept-Encoding
:authority:
images.weserv.nl
:method:
GET
:path:
/?t=fit&a=attention&dpr=1&il=1&q=85&page=0&w=600&h=1200&url=ssl%3A64.media.tumblr.com%2Fcc8ef8aecab597c3334974541403d9a0%2F3419b01804c8e91c-47%2Fs640x960%2F4d1533ccec664e40ce10c3ffe823fff57f7f277e.gif
:scheme:
https
accept:
image/avif,image/webp,image/apng,image/svg+xml,image/*,*/*;q=0.8
accept-encoding:
gzip, deflate, br, zstd
accept-language:
en-US,en;q=0.9
priority:
i
sec-ch-ua:
"Chromium";v="130", "Google Chrome";v="130", "Not?A_Brand";v="99"
sec-ch-ua-mobile:
?0
sec-ch-ua-platform:
"Windows"
sec-fetch-dest:
image
sec-fetch-mode:
no-cors
sec-fetch-site:
cross-site
user-agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36

I'm getting this "Headers" data from here (the relevant URL is selected in the screen-shot) :

Maybe I'm looking in the wrong place in the Network "Headers"?

[VivaLaUSA]

What method are you using to copy the "Headers" data?

Mine is formatted in a different way (results getting displayed below the data). I'm using Windows "Copy" function and then pasting that (from the clipboard) to the forum topic.

[VivaLaUSA]

@Pathduck - How do I create the "HAR" file (as far as specifics) - I'm not able to observe the screen-shot you've posted in the topic on the former page (as illustrated below):

[Pathduck]

@VivaLaUSA You click the button I have highlighted in the screenshot.
In the devtools network log. It even shows in the images you posted.
https://requestly.com/blog/how-to-generate-har-files-in-chrome-firefox-safari/
Vivaldi = Chromium.

What method are you using to copy the "Headers" data?

I'm just selecting all and copying+pasting. Then I'm doing a little search+replace to remove line breaks after the colons to make it shorter overall.

Maybe the browser is loading from cache, so try Ctrl+F5. But the remote address should still show, along with several other headers you don't have in your log.

But the headers are not that important any longer, we know you're getting the wrong IP.

So perform the command line steps I posted earlier.

Also, under chrome://net-internals/#dns, in the DNS Lookup field, fill in images.weserv.nl and hit Lookup. The result should be a string like:
Resolved IP addresses of "images.weserv.nl": ["104.21.234.187","104.21.234.186"].

[VivaLaUSA]

Did the following:

Reloaded Start-page - no change regarding Comic Widget (at least it appears we're getting the results we should in the second screen-shot).

[Pathduck]

@VivaLaUSA OK look like now you're at least getting the correct IP. Now try all the other things again - try opening the url directly (it's probably changed since yesterday), look at the headers and make sure the response code is 200 OK and that the header Remote Address is the expected one.

Also clear cache again.
Reload the page with Ctrl+F5.
Save a HAR file if necessary.

[VivaLaUSA]

@Pathduck
I want to thank you (and everyone else) - for trying to help out regarding this Widget rendering issue (that occur for a limited number of specific browsers).

An overview of where I stand:
The issue persists (all the time) however with both Vivaldi and Pale Moon browsers and actually from what I can tell Google Chrome as well every time I check it, but since I don't use Chrome I don't check it that often - some other browsers exhibit the issue occasionally (~1-5% of the time, I.e. Brave, Edge and Opera to name a few). While other browsers virtually never exhibit the issue, i.e. Floorp, Epic and Ghostery to name a few.

I've turned over a lot of info to Start.me support and gotten back a couple of replies - they thanked me for the data points and report that they continue to investigate the issue, specifically whatever problems there may be with "weserv.nl" as to why the Widget fails to render specifically in both the browsers I've reported, Vivaldi and Pale Moon.

This may take some time - I'll change to browsers that work (at least for now) and wait for the Start.me support findings at some point.

So thanks again for all the help.

[Pathduck]

@VivaLaUSA Well, hopefully you've learned enough troubleshooting tips and devtool stuff to better figure out whatever strange mysterious web site issue befalls you in your next "working" browser