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

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

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.
Hey there! 👋
If your project is open-source, feel free to share the link and I’d be happy to take a look and try to reproduce the problem!
Besides that, since static hosting doesn’t handle dynamic routes by default, a page refresh or direct link to any route other than the home page usually results in a 404 error.
In most cases, the solution is to create a rule that directs all traffic to index.html so that React Router can manage the routing internally. You mentioned setting “index.html” as a custom catch-all page—this should allow React to interpret the routes correctly, rather than redirecting everything back to the home page.
I’ve fixed that in the past by in the DigitalOcean App Platform, by going to App settings and adding a catch-all route that points to index.html for any unmatched routes. This makes sure that React Router can handle all client-side routing as expected.
Also, make sure you’re using BrowserRouter in your React app, and that it’s properly configured to handle history-based routing. This will ensure your routes work both on the initial load and when navigating within the app.
For the other requests you mentioned, be sure to enable the ‘Preserve Path Prefix’ option as well.
Let me know if this helps or if you’re still running into issues!
- Bobby