3 months ago
When I set up Permify instance and select public network it gives following error:
Application failed to respond
This error appears to be caused by the application.
If this is your project, check out your deploy logs to see what went wrong. Refer to our docs on Fixing Common Errors for help, or reach out over our Help Station.
If you are a visitor, please contact the application owner or try again later.
Request ID:
hPTznyZlTEOQ_TOdrJsmnA
3 Replies
3 months ago
What are the limitations for this since I am getting following errors too:
Permify lookupEntity error
Permify write error
Ollama embed error connect ETIMEDOUT 151.101.2.15:11434
Status changed to Awaiting User Response sam-a • about 2 months ago
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 2 months ago
15 days ago
This looks like a port/service wiring issue rather than a Railway outage.
Permify exposes two different ports by default:
- REST/HTTP API: 3476
- gRPC API: 3478
So for Railway public networking, set the target port to 3476 if you want the public Railway URL to load/respond over HTTP. If your app talks to Permify with the gRPC client, use port 3478 from your app over Railway private networking instead of the public HTTP domain.
The Ollama error is separate:
connect ETIMEDOUT 151.101.2.15:11434
Port 11434 is Ollama's local server port. A Railway service cannot reach an Ollama process running on your laptop, and that external IP is not an Ollama service listening on 11434. Either run Ollama as its own Railway/private-network service and point your app to that internal host:11434, or switch embeddings to a hosted model API.
Quick check:
- Public URL / browser check -> target port 3476.
- App-to-Permify REST -> http://:3476.
- App-to-Permify gRPC -> :3478.
- Ollama embeddings -> a reachable Ollama service URL, not localhost and not a random public IP on 11434.
15 days ago
Small formatting correction: the host placeholder was stripped above.
Use your Permify service's Railway private hostname in those examples:
- REST: http://PERMIFY_PRIVATE_HOST:3476
- gRPC: PERMIFY_PRIVATE_HOST:3478
For example, copy the private networking host from the Permify service in Railway, then append the correct port for the client you are using.