Web Server Error /web/refreshingimage: no refreshing image U

Indigo 2023.1.1

This is the error with Indigo 2023.1.1 with the same URL as 2022
(https://api.buienradar.nl/image/1.0/Rad ... =160&h=120)

Web Server Error /web/refreshingimage: no refreshing image URL configured for element 323 on page ''
Web Server Warning HTTP 400 error for request /web/refreshingimage

I don't think the problem is with the URL, but something else on that control page. Or the way that element is defined.

OK, can you try this please at your own (new) control page?

https://api.buienradar.nl/image/1.0/Rad ... =160&h=120

(And as said before: it has worked perfectly for years and nothing has changed at that control page, it suddenly happened)

Thanks for your support.

When I do it, I get a different error:

Code: Select all

   Web Server Warning              /web/refreshingimage: error loading image, reply from url server: 301
   Web Server Error                internal server error for request /web/refreshingimage from 192.168.111.109


code 301 is "Moved Permanently", which means that URL is no longer valid. The server will return the new URL, but it looks like Indigo is not following the redirect. To find the correct URL:

Code: Select all

% curl -v "https://api.buienradar.nl/image/1.0/RadarMapNL?w=160&h=120"
*   Trying 23.205.165.187:443...
* Connected to api.buienradar.nl (23.205.165.187) port 443 (#0)
* ALPN: offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256
* ALPN: server accepted h2
* Server certificate:
*  subject: C=NL; L=Hilversum; O=RTL Nederland B.V.; CN=www.buienradar.nl
*  start date: Sep 14 00:00:00 2023 GMT
*  expire date: Sep 13 23:59:59 2024 GMT
*  subjectAltName: host "api.buienradar.nl" matched cert's "*.buienradar.nl"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
*  SSL certificate verify ok.
* using HTTP/2
* h2 [:method: GET]
* h2 [:scheme: https]
* h2 [:authority: api.buienradar.nl]
* h2 [:path: /image/1.0/RadarMapNL?w=160&h=120]
* h2 [user-agent: curl/8.1.2]
* h2 [accept: */*]
* Using Stream ID: 1 (easy handle 0x14300a800)
> GET /image/1.0/RadarMapNL?w=160&h=120 HTTP/2
> Host: api.buienradar.nl
> User-Agent: curl/8.1.2
> Accept: */*
>
< HTTP/2 301
< content-length: 0
< location: https://image.buienradar.nl/2.0/image/animation/RadarMapRainNL?height=120&width=160&extension=png&renderBackground=True&renderBranding=False&renderText=True&history=3&forecast=3&skip=1
< cache-control: public, max-age=2493
< date: Thu, 30 Nov 2023 19:09:54 GMT
< access-control-max-age: 86400
< access-control-allow-credentials: false
< access-control-allow-headers: Origin, X-Requested-With, Content-Type, Accept
< access-control-allow-methods: GET,POST,PUT
< access-control-allow-origin: *
<
* Connection #0 to host api.buienradar.nl left intact


Trying with https://image.buienradar.nl/2.0/image/animation/RadarMapRainNL?height=120&width=160 gives a 302 result, which is a normal redirect:

Code: Select all

% curl - https://image.buienradar.nl/2.0/image/animation/RadarMapRainNL?height=120&width=160
[1] 35502
zsh: no matches found: https://image.buienradar.nl/2.0/image/animation/RadarMapRainNL?height=120
[1]  + exit 1     curl -                                                                                                           
jkeenan@Kraken ~ % curl -v "https://api.buienradar.nl/image/1.0/RadarMapNL?w=160&h=120"                     
jkeenan@Kraken ~ % curl -v "https://image.buienradar.nl/2.0/image/animation/RadarMapRainNL?height=120&width=160"
*   Trying 104.89.170.180:443...
* Connected to image.buienradar.nl (104.89.170.180) port 443 (#0)
* ALPN: offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256
* ALPN: server accepted h2
* Server certificate:
*  subject: C=NL; L=Hilversum; O=RTL Nederland B.V.; CN=www.buienradar.nl
*  start date: Sep 14 00:00:00 2023 GMT
*  expire date: Sep 13 23:59:59 2024 GMT
*  subjectAltName: host "image.buienradar.nl" matched cert's "*.buienradar.nl"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
*  SSL certificate verify ok.
* using HTTP/2
* h2 [:method: GET]
* h2 [:scheme: https]
* h2 [:authority: image.buienradar.nl]
* h2 [:path: /2.0/image/animation/RadarMapRainNL?height=120&width=160]
* h2 [user-agent: curl/8.1.2]
* h2 [accept: */*]
* Using Stream ID: 1 (easy handle 0x13e00c200)
> GET /2.0/image/animation/RadarMapRainNL?height=120&width=160 HTTP/2
> Host: image.buienradar.nl
> User-Agent: curl/8.1.2
> Accept: */*
>
< HTTP/2 302
< content-length: 0
< location: https://image-cdn.buienradar.nl/br-processing/image-api/RadarMapRainNL/Animation/202311301905__160x120_True_False_True_3_3_1_0_run202311301900.gif
< cache-control: max-age=160
< date: Thu, 30 Nov 2023 19:13:35 GMT
< strict-transport-security: max-age=15768000
< access-control-max-age: 86400
< access-control-allow-credentials: false
< access-control-allow-headers: Origin, X-Requested-With, Content-Type, Accept-Encoding
< access-control-allow-methods: GET,POST,PUT
< access-control-allow-origin: *
< set-cookie: akaalb_image_buienradar=~op=image_buienradar_ALB:tm-buienradar-image|~rv=97~m=tm-buienradar-image:0|~os=acd31c62b25089f0dcf410e10561d4bf~id=0221a6d276eca6632e173c19309fd9c7; path=/; HttpOnly; Secure; SameSite=None
<
* Connection #0 to host image.buienradar.nl left intact


Which gives this URL: https://image-cdn.buienradar.nl/br-proc ... 301900.gif

Which works, but I don't know if it refreshes or not.

Matt or Jay will have to chime in on the redirect issues and if the server is supposed to handle them.

[jay (support)]

While diagnosing your other issue, we ran across the error that FlyingDiver saw and it will also be taken care of in 2023.2.

The error that you are reporting is clearly different, and it means that there is a a refreshing image on a control page that is misconfigured. Probably not the one that you are thinking that it is.

Thanks for your time Joe.

The error that you are reporting is clearly different, and it means that there is a a refreshing image on a control page that is misconfigured. Probably not the one that you are thinking that it is.

Strange that the only error we get with Indigo 2022 in the log is from this URL.
(but we're not allowed to talk about that in this thread)

And when we test the same Indigo database and the same URL in Indigo 2023 we get the error as described above.

Web Server Error /web/refreshingimage: no refreshing image URL configured for element 323 on page ''
Web Server Warning HTTP 400 error for request /web/refreshingimage from 127.0.0.1

See also the screen dump with the element number from the control page.

Try this. Create a NEW control page with that refreshing image and see what error you get, if any.

Thanks for the feedback.

That gives indeed another error:

Web Server Warning /web/refreshingimage: error loading image, reply from url server: 301
Web Server Error internal server error for request /web/refreshingimage from 127.0.0.1

Thanks for the feedback.

That gives indeed another error:

Web Server Warning /web/refreshingimage: error loading image, reply from url server: 301
Web Server Error internal server error for request /web/refreshingimage from 127.0.0.1

Which is the one that Jay said will be fixed in 2023.2. So there's something else wrong with your original control page. I would delete that set of elements and see if the control page keeps giving the same error. You might just need to recreate the control page completely. But waiting for 2023.2 so you don't get the 301 error would be a good idea.

[matt (support)]

This bug (refreshing images not following HTTP 301 redirects) will be fixed in the next release of Indigo (2023.2)