Can you give a bit more context on this issue?

We have been redirecting our API calls through a proxy due to network issues when accessing the railways domain directly. This setup has been working well for a long time, but suddenly it has started failing.

Just checking, are you using a proxy or a custom domain?

we are using proxy

Have you tried using a custom domain?

xxxx.xxxx.up.railway.app is working but proxy to this not working. I have similar issue earlier, they resolved from their side

Is there anyone from railway side to help on this ?

Why not switch to the pregenerated URL if it's working then?

Also, what sort of network issues were you facing?

We are having some issues with Jio customers

Jio network is blocking railway domain accessing directly

^

It is working till now, it's stopped working today. We don't want to go with custom domain.

Based on my research on this, this issue occurs when a web browser receives data that it cannot properly unzip or decode. My guess is, your proxy is automatically decompressing the response, but still passing the original Content-Encoding header back to the client. The browser tries to decode an already decompressed data, and fails. And this probably started happening because somewhere in the network layer compression for all HTTP API responses was introduced.

You can set Accept-Encoding to identity (this removes compression). Example: req.headers['accept-encoding'] = 'identity';, Or remove Content-Encoding header on the client before parsing the response.

You can read this Stack Overflow thread for more info on this: https://stackoverflow.com/questions/14039804/error-330-neterr-content-decoding-failed

You can also try to clear you DNS/Browser cache, and disable your firewall, as this issue could be caused by cache as well.

This issue has been happening again today. It seemed to resolve after a certain time, but now it’s reoccurring at the same time as before. Why isn’t Railway support addressing this?