-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
🐛 Bug: "Some Internal error occured" Error when submitting form from mobile with images in attachment field #11116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm having the same issue, same env. Very sad that this base functionality is not working now. @dstala please look into this. |
Any ideas on the further steps on that please? |
hii @ilyak0 Unfortunately we are not able to reproduce the issue. I would need some more details to debug?
Would you be able to share a form where I can reproduce the issue? |
This comment has been minimized.
This comment has been minimized.
I hope you don't mind doing some submissions to check 😅. Else can you create a sample form where I can test around. |
@DarkPhoenix2704 sure, you're very welcome to do so |
@DarkPhoenix2704 Also in the same base I can't download contents as csv/xls now.. |
Is there any error logs you can share from NocoDB instance? |
@DarkPhoenix2704 Will send you tomorrow. Did you see any errors by submitting forms from mobile? I see 2 successful entries from you. |
We've managed to sort it on our own -- there were some issues with the Nginx congfigs, causing 413 Request Entity Too Large and 414 Request-URI Too Large errors. |
Closing this issue, then. Create new issue is issue still reproducable. |
@DarkPhoenix2704 continuing here |
Please confirm that the bug report does not already exist
Steps to reproduce
When submitting the form, from mobile with attachment field filled with document or images, this issue is comming while, same form is working in desktop
Desired Behavior
It should work accept the form with photos or docs in attachment field
Project Details
0.262.5 running in Docker compose
Attachments
No response
The text was updated successfully, but these errors were encountered: