Loading chunk failed for Parallel Routes in Next.js 15
Answered
Persian posted this in #help-forum
PersianOP
Everything else is working fine, but this particular resource is not accessible.
This is a dockerized Next.js 15 standalone SSR application, deployed on a VM on a Apache-based cloud, with reverse proxy.. I have deployed and tested the same container to another VPS with NGINX, and it is working absolutely fine.
This is a dockerized Next.js 15 standalone SSR application, deployed on a VM on a Apache-based cloud, with reverse proxy.. I have deployed and tested the same container to another VPS with NGINX, and it is working absolutely fine.
Answered by Persian
Issue resolved. The Apache was decoding the URL while proxying the request.
The file path has special characters (like [ ] @) which may not be correctly handled by Apache.
I added the following directive before ProxyPass rules in site configurations:
This tells Apache not to decode encoded slashes or special characters, and just forward them raw.
I also added
The file path has special characters (like [ ] @) which may not be correctly handled by Apache.
I added the following directive before ProxyPass rules in site configurations:
AllowEncodedSlashes NoDecode
This tells Apache not to decode encoded slashes or special characters, and just forward them raw.
I also added
nocanon
to ProxyPass to prevent Apache from decoding URLs.1 Reply
PersianOP
Issue resolved. The Apache was decoding the URL while proxying the request.
The file path has special characters (like [ ] @) which may not be correctly handled by Apache.
I added the following directive before ProxyPass rules in site configurations:
This tells Apache not to decode encoded slashes or special characters, and just forward them raw.
I also added
The file path has special characters (like [ ] @) which may not be correctly handled by Apache.
I added the following directive before ProxyPass rules in site configurations:
AllowEncodedSlashes NoDecode
This tells Apache not to decode encoded slashes or special characters, and just forward them raw.
I also added
nocanon
to ProxyPass to prevent Apache from decoding URLs.Answer