a month ago
Users on my app can post html formatted comments and in these, upload images and the javascript library converts it all to base 64 (summernote.js).
summernote image uploads don't work on railway with larger images like a screenshot from my iphone whereas the identical code on crappier heroku servers still works.
i know you guys have overractive ai that block/handle ddos requests because it would block users trying to access the edit form even on the first load (which finally got resolved but nobody ever replied affirmatively to that thread after I posted logs and reproduced the problem, for me to thank), but anyone who programs any app differently from whatever your AI expects doesn't get appropriate traffic flow or their request to go thru.
I used to be able to just post the image directly from my screenshots but now i have to compress the image first to a whole different file format and lower the size before my POST request from my client device submitting the html form actually goes thru.
PLEASE STOP USING AI AND HIRE A COMPETENT DEVOPS TEAM instead of this bounty bs.
PLEASE ALLOW THE FULL POST REQUEST TO GO THRU AND STOP BLOCKING MY USERS TRAFFIC!
I just reproduced the issue at 15:23
from the application logs:
'EST Invalid or incomplete POST params
I, [2025-10-03T19:23:21.556504 #1] INFO -- : [ee630cc8-e469-4b73-90ea-ac056053ef97] Started POST "/comments" for 76.38.5.119 at 2025-10-03 19:23:21 +0000
F, [2025-10-03T19:23:22.928791 #1] FATAL -- : [ee630cc8-e469-4b73-90ea-ac056053ef97]
[ee630cc8-e469-4b73-90ea-ac056053ef97] ActionController::BadRequest (Invalid request parameters: total query size (22823940) exceeds limit (4194304)):'
This request goes thru on Heroku but not Railway because of how railway has been configured and it's breaking my app. PLEASE FIX NOW.
6 Replies
a month ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
a month ago
Hello,
> i know you guys have overractive ai that block/handle ddos requests
I am not sure where you got this information, but you are quite mistaken. We do not offer or perform any DDoS mitigation or filtering whatsoever. There is also no AI involved in any network pathways.
Additionally, we do not impose any upload size limits; the only limit is a 15-minute timeout on incoming HTTP requests.
Please feel free to POST your data that is failing to this test endpoint: https://utilities-us-east.up.railway.app/?filter=upload
I'll also go ahead and open this thread up to our community, as this is not a platform issue.
Best,
Brody
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 brody • about 1 month ago
a month ago
[ee630cc8-e469-4b73-90ea-ac056053ef97] ActionController::BadRequest (Invalid request parameters: total query size (22823940) exceeds limit (4194304)):'
Assuming the log line is from your application (is this Rails?) the incoming request hits the request body limit that's set in your application.
Per this log line, your application has maximum upload size set to 4MB while the request is almost 23MB.
I am not a Rails expert, but it seems this can be changed via something like config.action_dispatch.request_parameters_limit = 100.megabytes on your application config
brody
Hello,> i know you guys have overractive ai that block/handle ddos requestsI am not sure where you got this information, but you are quite mistaken. We do not offer or perform any DDoS mitigation or filtering whatsoever. There is also no AI involved in any network pathways.Additionally, we do not impose any upload size limits; the only limit is a 15-minute timeout on incoming HTTP requests.Please feel free to POST your data that is failing to this test endpoint: https://utilities-us-east.up.railway.app/?filter=uploadI'll also go ahead and open this thread up to our community, as this is not a platform issue.Best,Brody
a month ago
my last issue was regarding that and it was promptly acknowledged by the team at Railway and corrected after I showed you guys timestamps logs and screenshots from both client and server. don't gaslight me. I've already proven your team wrong before.
READ THE LOGS
vedmaka
[ee630cc8-e469-4b73-90ea-ac056053ef97] ActionController::BadRequest (Invalid request parameters: total query size (22823940) exceeds limit (4194304)):'Assuming the log line is from your application (is this Rails?) the incoming request hits the request body limit that's set in your application.Per this log line, your application has maximum upload size set to 4MB while the request is almost 23MB.I am not a Rails expert, but it seems this can be changed via something like config.action_dispatch.request_parameters_limit = 100.megabytes on your application config
a month ago
There is no body or maximum request size limit set in the application.
The only limit in the app is set to cap the character count to 30mb worth of characters.
The infrastructure doesn't allow anything over 4mb thru the RACK.
FINALLY THE IDENTICAL CODEBASE ON HEROKU STILL WORKS (I STILL HAVE HEROKU FOR OTHER APPS AND TESTED IT).
YOUR INFRASTRUCTURE DOES NOT WORK!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
FYI UPDATE: the latest version of RACK has a 4mb limit that was not there before. It *IS* a block at the rack level and now I have to modify procfile or default rack config to go back to the expected longtime behavior.
a month ago
SOLUTION: either change every form in your app and hard-specify multipart forms to adapt to the new rack behavior. (i'm currently using this one)
or
if you don't have ddoss or rackattack issues you can use a procfile or environment variable such as (RACK_QUERY_PARSER_BYTESIZE_LIMIT) to adjust the maximum rack post size.
Status changed to Solved brody • about 1 month ago