Files
Claude 9fe942a510 Fix WebSocket connection blocked by Cloudflare by prioritizing polling transport
Changed Socket.IO transport order from ['websocket', 'polling'] to
['polling', 'websocket'] in the frontend terminal hook.

Why this fixes the issue:
- Cloudflare blocks direct WebSocket connections with 400 Bad Request
- HTTP polling works perfectly and bypasses Cloudflare's WebSocket protection
- Socket.IO now connects via polling first, then attempts upgrade to WebSocket
- If WebSocket upgrade fails (due to Cloudflare), connection stays on polling
- This ensures reliable connectivity without requiring Cloudflare config changes

Testing script included demonstrates:
✓ Polling transport: WORKS
✗ Direct WebSocket: BLOCKED by Cloudflare
✓ Auto-upgrade (polling→websocket): WORKS with graceful fallback

https://claude.ai/code/session_01SePwA78FSw4urCoyR2cqFh
2026-01-31 13:28:03 +00:00
..
2026-01-26 04:26:15 +00:00

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.