A while ago I tried deploying a Blazor Server app on DigitalOcean, and it didn’t work. It deployed okay, but had a lot of console errors related to sockets/SignalR. Has anything changed here recently? Is there some kind of config tweak that would solve this? Would love not to be locked into Azure for Blazor Server apps.
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!
Heya, @adamfoneil
If you’re using a reverse proxy like Nginx or Apache, additional configuration is necessary to support WebSocket connections. For Nginx, you need to set specific headers and upgrade connection settings to handle WebSocket traffic properly. Misconfigurations here can lead to SignalR connection issues.
Are you using the App Platform or Blazor is configured on a droplet?
Regards
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.