Cursor
realtime
Server-Sent Events Disconnecting in Cursor Application
Your Cursor-generated application uses Server-Sent Events (SSE) for real-time updates (live notifications, streaming responses, dashboards), but the SSE connection drops after a few seconds or minutes. Users see the real-time feed freeze, and the browser's EventSource silently reconnects only to disconnect again in a loop.
SSE connections are long-lived HTTP connections that must stay open indefinitely. This conflicts with many infrastructure components that expect short request-response cycles. Reverse proxies, load balancers, serverless platforms, and CDNs all have default timeouts that terminate SSE connections prematurely.
The issue is often intermittent — it works fine during development where there's no proxy layer, but fails in production where Nginx, Cloudflare, or a serverless platform sits between the client and server.
Error Messages You Might See
EventSource failed: net::ERR_INCOMPLETE_CHUNKED_ENCODING
EventSource connection lost, reconnecting...
504 Gateway Timeout
Error: stream timeout after 60000ms
ReadableStream has been disturbed or locked
Common Causes
- Reverse proxy timeout — Nginx, Apache, or Cloudflare terminates idle connections after 60-120 seconds by default
- Serverless function timeout — Vercel (30s), Netlify (26s), and Lambda (15min max) kill long-running functions, terminating the SSE stream
- No keep-alive heartbeat — Without periodic data sent on the connection, intermediaries assume it's dead and close it
- Missing SSE headers — The response lacks required headers like
Content-Type: text/event-stream,Cache-Control: no-cache, orConnection: keep-alive - Response buffering enabled — Nginx or Node.js response compression buffers SSE data instead of streaming it, causing events to arrive in batches or not at all
How to Fix It
- Send heartbeat comments every 15-30 seconds — Send SSE comment lines (
: heartbeat\n\n) at regular intervals to keep the connection alive through proxies and load balancers - Configure proxy timeouts — For Nginx: set
proxy_read_timeout 86400s;andproxy_buffering off;. For Cloudflare: enable WebSockets/SSE in the dashboard or use Cloudflare Tunnel - Disable response buffering — Add
X-Accel-Buffering: noheader for Nginx, and disable compression on SSE endpoints - Implement robust client reconnection — Use EventSource's built-in reconnection with a custom
retry:field, and includeLast-Event-IDhandling to resume from where the client left off - Avoid serverless for SSE — If your SSE needs long-lived connections, deploy on a traditional server (VPS, container) rather than serverless functions. Alternatively, use a managed service like Ably or Pusher
- Set correct response headers — Ensure every SSE endpoint sends:
Content-Type: text/event-stream,Cache-Control: no-cache,Connection: keep-alive
Real developers can help you.
Franck Plazanet
I am a Strategic Engineering Leader with over 8 years of experience building high-availability enterprise systems and scaling high-performing technical teams. My focus is on bridging the gap between complex technology and business growth.
Core Expertise:
🚀 Leadership: Managing and coaching teams of 15+ engineers, fostering a culture of accountability and continuous improvement.
🏗️ Architecture: Enterprise Core Systems, Multi-system Integration (ERP/API/ETL), and Core Database Structure.
☁️ Cloud & Scale: AWS Expert; architected systems handling 10B+ monthly requests and managing 100k+ SKUs.
📈 Business Impact: Aligning tech strategy with P&L goals to drive $70k+ in monthly recurring revenue.
I thrive on "out-of-the-box" thinking to solve complex technical bottlenecks and am always looking for ways to use automation to improve business productivity.
Pratik
SWE with 15+ years of experience building and maintaining web apps and extensive BE infrastructure
Meïr Ankri
Full-stack developer specializing in React / Next.js / Node.js with 6+ years of experience. I've worked across various sectors including automotive (Reezocar/Société Générale), healthcare (Medical Link SaaS), and e-commerce (Glasman). I build web apps end-to-end, from architecture to production, with a focus on scalability, performance, and code quality. I also mentor junior developers and contribute to technical decisions and code reviews.
rayush33
JavaScript (React.js, React Native, Node.js) Developer with demonstrated industry experience of 4+ years, actively looking for opportunities to hone my skills as well as help small-scale business owners with solutions to technical problems
Prakash Prajapati
I’m a Senior Python Developer specializing in building secure, scalable, and highly available systems. I work primarily with Python, Django, FastAPI, Docker, PostgreSQL, and modern AI tooling such as PydanticAI, focusing on clean architecture, strong design principles, and reliable DevOps practices. I enjoy solving complex engineering problems and designing systems that are maintainable, resilient, and built to scale.
Jacek Rozanski
Senior PHP/Symfony developer and DevOps engineer with 20+ years of professional experience, running opcode.pl (web development agency, est. 2004).
Day job: I'm the sole backend developer at merketing company where I own and maintain 11 PHP/Symfony microservices on AWS (ECS Fargate, RDS, S3, CloudFront), handle the full CI/CD pipeline (Bitbucket Pipelines, Docker), and manage monitoring with Sentry and CloudWatch. These services handle high request volumes in production every month.
What I bring to AI-built apps:
- I audit and fix security issues (OWASP methodology), performance bottlenecks, and architectural problems in codebases generated by Cursor, Claude Code, Lovable, Bolt, and v0
- I refactor AI-generated prototypes into production-grade applications with proper error handling, testing, and clean architecture (SOLID, DDD, hexagonal architecture)
- I set up the infrastructure AI tools don't touch: AWS hosting, CI/CD pipelines, automated deployments, database optimization, monitoring, and alerting
- I integrate external services: payment providers, email systems, partner APIs, SSO/auth
Tech stack: PHP 8.x, Symfony, React, Next.js, PostgreSQL, MySQL, Docker, AWS (ECS, RDS, S3, SQS/SNS, CloudFront), Terraform, Supabase. I also use AI tools daily (Claude Code, Cursor) in my own workflow, so I understand both the strengths and the gaps in AI-generated code.
Based in Poland (CET timezone). Available for async work and calls during EU/US business hours.
David Olverson
Solo dev shipping production apps with AI-assisted development. I specialize in rescuing broken Lovable/Bolt/Cursor builds and taking them to production. 10+ apps shipped including SaaS CRMs, gaming platforms, real estate tools, and Discord bots. Stack: Next.js 16, TypeScript, Tailwind CSS, FastAPI, PostgreSQL, Prisma. I use Claude Code with 50+ custom skills for rapid delivery. Average turnaround: 2-4 weeks from broken prototype to production.
Anthony Akpan
Developer with 8 years of experience building softwares fro startups
Kingsley Omage
Fullstack software engineer passionate about AI Agents, blockchain, LLMs.
Daniel Vázquez
Software Engineer with over 10 years of experience on Startups, Government, big tech industry & consulting.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
Can I use SSE with serverless platforms like Vercel?
Standard SSE with long-lived connections doesn't work well with serverless platforms due to function execution time limits. Vercel supports streaming responses for up to 30 seconds. For longer connections, use a dedicated WebSocket service (Ably, Pusher, Supabase Realtime) or deploy the SSE endpoint on a traditional server.
How is SSE different from WebSockets?
SSE is unidirectional (server to client only), uses standard HTTP, and has built-in reconnection. WebSockets are bidirectional, use a separate protocol (ws://), and require manual reconnection logic. Use SSE when you only need server-to-client updates; use WebSockets when you need two-way communication.