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!
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.
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