Acknowledged
CIQQA-3382

makeImageRequest failing to several websites with 404 error

Starting sometime July 1, 2025, makeImageRequests to various websites started returning a 404 not found error on all devices and in the simulator.  This is an intermittent problem and seems to affect all servers within a specific domain.  It also only appears to affect makeImageRequests as makeWebRequests to the same server are working correctly.  

Steps taken to define the problem:

tested downloads from the following hosts

ciq.sabeard.net

  • makeImageRequest with SDK 4.0.6 works
  • makeImageRequest with SDK 8.2.2 returns a 404 error
  • najeWebReqyest with either SDK works
  • Putting the image URL in a browser works, but in the simulator or on the device, gets a 404 error

ciqtest.sabeard.net

  • exact same behavior as ciq.sabeard.net

maps.aerisapi.com

  • images downloaded from this host appear to work with both SDKs as well as from the web browser.

Doing some packet captures and monitoring webserver logs.  The pattern I can see is with SDK 4.0.6, the simulator directly connects to the webserver and is able to properly download the images.  So I know the webservice is running and functional.  I also can see the HTTP request in the webserver logs.  When using SDK 8.2.2, I can see the simulator makes a TLS connection to services.garmin.com and also to api.gsc.garmin.com.  In the webserver logs.  I can see 1 connection to the webserver for the makeWebRequest URL, but that is the only connection attempt I can see in the server logs.  Nothing for the image download.  So I can only assume that there is a problem with the Garmin servers that pre-process the images which is causing the 404 error,.

Looking back at my webserver logs, whatever problem the servers are having first occurred around 12:54pm CDT on July 15, 2025.  That is the last time my webserver received any image download request from my radar app,

I will be happy to provide direct URLs via email if that will help with troubleshooting.

sabeard
Parents Comment Children
  • in reply to sabeard

    Thank you for a quick answer. It is a solution indeed; good to know.
    I found that if I upload an image to GitHub, it also works :)
    For testing, it is ok, but for a permanent solution, GitHub might have some limits and, after some time, will start blocking it Disappointed

    But on some other image hosting sites, it does not, and I get a 404. Looks like Garmin has white list or black list of server, which are acceptable for images. At least, they could publish this list of acceptable or non-acceptable servers for images.

  • in reply to zlelik

    I ended up finding out that if I route my request through an Amazon API gateway proxy it works fine so that is the solution I have stuck with.  I could not wait for Garmin to fix their servers.