--- title: "Database Private Network Defaults, New Edge Proxy Migration, Request for Nits" date: 2024-07-19 number: 0195 url: https://railway.com/changelog/2024-07-19-database-private-networking --- # Database Private Network Defaults, New Edge Proxy Migration, Request for Nits Happy Friday, Passengers! We’re in the midst of a sprint to improve platform usability and reliability and we need your help. Before we get started, we invite you to [let us know](https://help.railway.app/feedback/request-tell-us-about-your-nits-on-the-a3c5878e) about any nits, papercuts, issues, or footguns with the platform. We’re going to challenge ourselves to fix every issue on the list — so please don’t be shy. Let us know what issues you’re running into no matter how small. Ok? Ok! Now let’s get into the changelog. ## Database Private Network Defaults [Image: We changed the default database connection type to private to prevent unwanted egress charges] Nobody likes surprise egress charges — that includes us. We’ve noticed a number of users running up unexpected bills because they were connecting to their Railway database via [Public Networking](https://docs.railway.app/guides/public-networking). We encourage you to [use Private Networking](https://docs.railway.app/guides/optimize-usage#use-private-networking) whenever possible. To underline that recommendation, we made the Private Network connection string the default in the UI. (No egress charges if you’re using the private network.) This is what else we’ve changed: - All databases now expose the private URL by default - All databases now expose the public URL separately as `${dbName}_PUBLIC_URL` - We’ve also updated the connect modal within the `Data` tab on a database (see image above) Does that sound good? Together we can stop unwanted egress charges! Let us know what you think by dropping a comment in [Help Station](https://help.railway.app/feedback). ## New Edge Proxy Migration [Eight weeks ago](https://railway.app/changelog/2024-05-17-new-edge-proxy-beta#introducing-the-new-edge-proxy-(beta)) we told you all about the new Edge Proxy that we (then) rolled out in beta. [Four weeks ago](https://railway.app/changelog/2024-06-14-nyoooom#edge-proxy-rollout-update) we told you that we made the Edge Proxy (then) generally available. Today, we’re letting you know that we’re going to start force-migrating all service domains, regardless of user plan tier, to the new Edge Proxy. This will happen next week. **No action is needed on your end.** As a reminder, these are the benefits of the new Edge Proxy: - You’ll experience near-instant deploy cutovers instead of waiting for a minute until it’s provisioned as currently happens today - You’ll get new detailed error pages with a traceable Request ID that you can forward to us when debugging an issue And there are some benefits that this will unlock down the line: - We’ll be able to further improve service start time - We’ll be able to provide automatic port detection - We’ll be able to support [multiple ports per service](https://help.railway.app/feedback/expose-multiple-ports-9c904897) - We’ll be able to provide network logs and metrics - We’ll be able to add support for advanced routing rules and load balancing strategies - We’ll be able to improve service quality and DDoS attack mitigation options Note that your custom domains will continue to use the legacy proxy if you haven’t already opted in … but what are you waiting for? The new Edge Proxy offers faster deploys, better networking troubleshooting with request IDs, and will have much more in the near future. At some point next week, we’ll make the existing proxy toggle in the dashboard change only the proxy in use for custom domains. Later on this quarter, we will follow this same force opt-in migration for custom domains. (This means that our goal will be to deprecate the legacy proxy entirely sometime this quarter.) If you have further questions or comments about the migration, please drop us a line in the [Help Station thread](https://help.railway.app/feedback/introducing-railway-s-new-edge-proxy-e6c7d6cf). ## Request for Nits As mentioned in the introduction, it’s a big month at Railway as we work to increase platform reliability and user experience. We’d love your feedback on what we can make better on the platform. Join us in [this](https://help.railway.app/feedback/request-tell-us-about-your-nits-on-the-a3c5878e) Help Station thread and let us know what we can do to improve your experience on the platform. We’ll strive to fix everything on the list. Have a great weekend! ✌️ ## Fixes and Improvements - We [upgraded Nixpacks to v1.24.6](https://github.com/railwayapp/nixpacks/releases/tag/v1.24.6) - We introduced a new guide to [Deploying a Monorepo to Railway](https://docs.railway.app/tutorials/deploying-a-monorepo) (h/t Community Member Brody!) - We fixed a bug where users were unable to edit service domains if more than one service was present - We fixed an issue where template health stats were not showing up for some templates - We fixed a bug where updating a team template would redirect you to your personal workspace rather than your team workspace - We made it published templates clickable from your account page