Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

Websocket listener on Digital Ocean hangs after a minute or so

Posted on December 13, 2024

DigitalOcean App Platform

Networking

App Platform

By lp10011

Hi. I made a websocket listener in an app platform worker to listen to the bluesky firehose.

My code works fine on Heroku. It stays up for days.

When I deployed to app platform it would start listening and processing events and then just hang after a minute or two.

It’s a golang program and I’m deploying a container. The same build process produced the container that I deployed to both platforms.

Does Digital Ocean throttle bandwidth or anything?

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby

December 18, 2024

Hey there, @lp10011! 👋

The App Platform doesn’t throttle bandwidth, there might be something else causing the connection to hang.

When using WebSockets, make sure your client is sending the following headers in the request:

Connection: Upgrade – This header indicates that the client wants to keep the connection open and use it for non-HTTP protocols.
Upgrade: websocket – This header requests the server to switch from HTTP to the WebSocket protocol.

Also make sure you’re deploying as a service, not a worker, so the port is exposed properly.

For reference, DigitalOcean has a handy Node.js WebSocket example that shows how to set up real-time bidirectional communication. While it’s in Node.js, the setup principles should be similar for your Golang app.

If your project is open source or if you have a minimal setup repo you can share, I’d be happy to try deploying it on my end to see if I can spot what might be going on!

On another note, you might consider deploying your WebSocket listener on a Droplet instead. With a Droplet, you get full root access, the flexibility to configure your server exactly how you need, and the ability to manage containers easily with tools like Docker. Check out the Docker Droplet on the Marketplace for a quick way to get started.

- Bobby

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.