Post

@danielroe.dev Do you have an idea, why this is happening. I have a Nuxt site, where we use the routeRules to proxy calls to the CMS api. If the site is left idle for 5min in browser, then its like these rules stop, working (or stop run though the serverside) but acces it directly though client-side

Rasmus P

@rasmusp.com

The reason for this, is that is only the nuxt server side that can communicate with the CMS, because of Firewall rules. So we cant make client-side calls. Everything works on the "first" render, but if left idle then is just stops working

22/9/25, 4:47 pm0 reposts0 likes

daniel r(ooooooh) in nyc 🇺🇸

@danielroe.dev

22 Sept 2025

hmm. so difficult to guess without a reproduction

Rasmus P

@rasmusp.com

22 Sept 2025

I know its difficult, was hoping for some pointer in which direction to look. Dont know if a quick repo of how we set it up on the nuxt side would help ?

daniel r(ooooooh) in nyc 🇺🇸

@danielroe.dev

22 Sept 2025

sure, tell me more is it a useFetch call to the proxied url?

Rasmus P

@rasmusp.com

22 Sept 2025

it a useAsyncData with $fetch, see the error. But we also proxy "/media" to the img url, in the CMS. and this also "loses" connection So in some way, it feels like that after +5 min, something in the proxy/h3/routesRules shuts off, and the client side calls the CMS directly .