-
SummaryI have a local setup with a next js server and a strapi server. I can hit the localhost url of a strapi image like so I have remote patterns set to the following and that seems to be correct What could I be doing wrong? Additional informationOperating System:
Platform: win32
Arch: x64
Version: Windows 11
Available memory (MB): 65361
Available CPU cores: 20
Binaries:
Node: 22.16.0
npm: 11.4.2
Yarn: 1.22.21
pnpm: N/A
Relevant Packages:
next: 16.0.1 // There is a newer version (16.0.3) available, upgrade recommended!
eslint-config-next: N/A
react: 19.2.0
react-dom: 19.2.0
typescript: 5.9.3
Next.js Config:
output: standalone
⚠ There is a newer version (16.0.3) available, upgrade recommended!
Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
Read more - https://nextjs.org/docs/messages/opening-an-issueExampleNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi, I had the same problem after migrating from Next 15.5.3 to Next 16.0.3. I also use Strapi on the backend. images: {
dangerouslyAllowLocalIP: true,
}But i think this setting should only be enabled in development mode, as it may cause security issues in production. |
Beta Was this translation helpful? Give feedback.
Hi, I had the same problem after migrating from Next 15.5.3 to Next 16.0.3. I also use Strapi on the backend.
Try adding this line in
next.config.ts- it solved my problem:But i think this setting should only be enabled in development mode, as it may cause security issues in production.