file size limit or streaming timeout
localtechethicist-commits
HOBBYOP

19 days ago

Hi community,

We're experiencing an issue with static image files on our production deployment (Project: disciplined-intuition, Service: disciplined-intuition).

Problem:

Large image files (>50KB) are returning HTTP 500 errors, while smaller images load successfully.

Examples:

✓ Working (200 status): DTA_logo.png (25KB), Signify.png (5.8KB)

✗ Failing (500 status): YAY_SUCCESS_Logo.png (220KB), Yuen_Yen_Tsai.jpeg (269KB), gallery images (81-161KB)

Timeline:

I migrated from vercel to Railway Hobby Plan at about 4:45p.m GMT+8 yesterday (May 2, 2026).

All images were working correctly until ~6:24 PM GMT+8 today (May 3, 2026)

Issue started immediately after SSL certificate reissuance

Files exist in /public/img/ with correct permissions

Next.js 16.2.3 with output: 'standalone' mode

Deployment Details:

Latest deployment: 582b18b1-7ffb-400c-9034-58db4ed25e39 (SUCCESS at 18:55:24 GMT+8)

No code changes correlate with the issue—only the SSL certificate renewal timing aligns

Question:

Is there a file size limit or streaming timeout in your reverse proxy/load balancer that may have been affected by the SSL certificate reissuance?

Thank you for your help.

Attachments

Solved$10 Bounty

Pinned Solution

  • There is not any limit on files by railway.
  • This is the browser cache issue. You can try loading url in incognito mode or clear cache of browser.

  • You can see all images are loading correctly.

1 Replies

Status changed to Open Railway 19 days ago


  • There is not any limit on files by railway.
  • This is the browser cache issue. You can try loading url in incognito mode or clear cache of browser.

  • You can see all images are loading correctly.


Status changed to Solved brody 13 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...