a year ago
ERROR: failed to build: failed to solve: failed to push production-europe-west4-drams3a.railway-registry.com/618d8fb8-8fba-4d6c-8e61-e9ae835717d4:8d58cea2-cada-4f12-a138-17811f394cda: failed to copy: unexpected status from PUT request to https://production-europe-west4-drams3a.railway-registry.com/v2/618d8fb8-8fba-4d6c-8e61-e9ae835717d4/blobs/uploads/d6fa148d-7ab4-44cc-8e9d-3e188b26f58a?%5Fstate=zni5X-zGz8uzonRXTeC3Mjt-EAauGgBC-RaDxymJykF7Ik5hbWUiOiI2MThkOGZiOC04ZmJhLTRkNmMtOGU2MS1lOWFlODM1NzE3ZDQiLCJVVUlEIjoiZDZmYTE0OGQtN2FiNC00NGNjLThlOWQtM2UxODhiMjZmNThhIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDI1LTA4LTE5VDE3OjA2OjA2LjA1MTQwMDc4NloifQ%3D%3D&digest=sha256%3A69632ac86712509413492d61469a20d7c21a9cba5fca49ebd153d79b71023da8: 413 Request Entity Too Large
3 Replies
a year ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 413 Request Entity Too Large
- 🧵 Failing to deploy a Python FastAPI service due 413 Request Entity failed to push production-*.railway-registry.com/
- 🧵 413 Request Entity Too Large on Production but it uploads on Local server
If you find the answer from one of these, please let us know by solving the thread!
Status changed to Awaiting User Response Railway • 11 months ago
a year ago
it was too big. I reduced the size. now its working fine. I was pulling all of the torch. I switched to torch[cpu] to reduce the size drastically
Status changed to Awaiting Railway Response Railway • 11 months ago
Status changed to Solved shivakharbanda • 11 months ago