11 days ago
My project “Exploração Surpreendente” has a service named “Projeto-conquista-online” in the production environment, with a persistent volume.
Settings → Networking displays “Não foi possível carregar a rede pública” (“Failed to load public networking”). The same message also appears under Scaling.
The service has no active deployment, and its creation/configuration changes are still pending. I have not applied them because the application requires a valid PUBLIC_URL before starting.
The account is on Limited Trial. GitHub is connected and the Railway GitHub App is installed.
The problem persists after refreshing, clicking Retry, using an incognito window, and testing both Edge and Chrome. Requests named internal?q=networking return HTTP 200, but I have not inspected their response bodies.
Could this be caused by the service still being pending creation, by Limited Trial restrictions, or by a dashboard issue? How can I configure a public domain before the first deployment?
1 Replies
11 days ago
Your workspace doesn't show any applied services yet, so "Projeto-conquista-online" exists only as staged, pending changes. A service that hasn't been applied has no service instance in the environment yet, and that's the likely reason both the Networking and Scaling panels fail to load. We found nothing on your account pointing to a Limited Trial restriction or a browser problem as the cause.
Public domains are set from the service's Settings → Networking → Public Networking (Generate Domain, or add a custom domain), as described in our Public Networking docs. That section needs the service to exist, so it becomes available once you apply the pending changes.
Status changed to Awaiting User Response Railway • 11 days ago
4 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 4 days ago