Hello, I am encountering an error when
Hello, I am encountering an error when trying to migrate a database to my self-hosted solution:
the error is 413 Request Entity too large. The context is that I am using a MySql server as backend and I am wondering if there are configurations that must be set that are not yet described in the guide. We managed to migrate this database from the cloud to the litesql we did for testing but now the production solution using MySql throw this error.
Does anyone knows how to fix it? Thanks.
I was thinking... could it be that the docker image of the convex backend i am using is old?
ghcr.io/get-convex/convex-backend:5143fec81f146ca67495c12c6b7a15c5802c37e2
12 Replies
Can you give more details and repro steps?
What command are you specifically running when you get that output? How are you getting the 413 output?
What have you tried doing to debug so far?
Hi, I am getting that error when running npx convex import {my_file.zip} --replace. So I am trying to import a snapshot of a database, I can tell you that the zip file is 26MB.
Do you know where the 413 is coming from? A 26MB import is well within size limits and should work.
Do you have any proxies before your backend that could be producing the 413?
Yes I am using nginx to allow https I can give you my composer if you want
if you could narrow down where the 413 is coming from, that would help you debug further
how would you suggest I do that?
depends on your setup, but claude or gpt can be really helpful. Eg Here's what it told me in a few seconds of interrogation
Ye thanks I was under the impression that it must be caused by the backend but it seems the reason could be this
nginx default value
which I did not change
if you can isolate the problem specifically to Convex, then I can probably help more
otherwise, I think you have to debug your own stack
yes in case I ll call you thanks
Ok tested it was indeed nginx
But I have another question:
Basically since I need this solution for a small network and I wanted to put the server in an internal machine I can't use a service like Let's Encrypt which require a publicly visible name to make a valid certificate. So I issued my own certificate but now convex is giving me problems
Uncaught ConvexError: Error executing ocr documents: Error: error sending request for url (https://10.60.131.173:3210/api/storage/a213be38-fe29-4671-8e08-0fb1c0e87a3c): client error (Connect): error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:2091: (self-signed certificate): error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:2091:
Now I updated my OS which contains the convex server to trust this certificate as I was hoping maybe convex was validating certificates using OS ca-certificates but didn't work. Is there a way to tell convex to trust this certificate and consider it valid?