HTTP413 Request Entity Too Large on OTA with Blynk Local Server

Hi,

I’m trying to perform OTA via Blynk Local Server, but after first configuration to implement OTA functionality when I try to start with an OTA update I get following error:

  • Trying ipmyhostname…
  • TCP_NODELAY set
  • Connected to myhostname (ipmyhostname) port 9443 (#0)
  • schannel: SSL/TLS connection with myhostname port 9443 (step 1/3)
  • schannel: disabled server certificate revocation checks
  • schannel: verifyhost setting prevents Schannel from comparing the supplied target name with the subject names in server certificates.
  • schannel: sending initial handshake data: sending 177 bytes…
  • schannel: sent initial handshake data: sent 177 bytes
  • schannel: SSL/TLS connection with myhostname port 9443 (step 2/3)
  • schannel: failed to receive handshake, need more data
  • schannel: SSL/TLS connection with myhostname port 9443 (step 2/3)
  • schannel: encrypted data got 1127
  • schannel: encrypted data buffer: offset 1127 length 4096
  • schannel: sending next handshake data: sending 126 bytes…
  • schannel: SSL/TLS connection with myhostname port 9443 (step 2/3)
  • schannel: encrypted data got 51
  • schannel: encrypted data buffer: offset 51 length 4096
  • schannel: SSL/TLS handshake complete
  • schannel: SSL/TLS connection with myhostname port 9443 (step 3/3)
  • schannel: stored credential handle in session cache
  • Server auth using Basic with user ‘admin@blynk.cc’

POST /admin/ota/start HTTP/1.1
Host: myhostname:9443
Authorization: Basic YWRtaW5AYmx5bmsuY2M6YWRtaW4=
User-Agent: curl/7.55.1
Accept: /
Content-Length: 803314
Expect: 100-continue
Content-Type: multipart/form-data; boundary=------------------------9282d35c41289c3b

  • schannel: client wants to read 102400 bytes
  • schannel: encdata_buffer resized 103424
  • schannel: encrypted data buffer: offset 0 length 103424
  • schannel: encrypted data got 120
  • schannel: encrypted data buffer: offset 120 length 103424
  • schannel: decrypted data length: 60
  • schannel: decrypted data added: 60
  • schannel: decrypted data cached: offset 60 length 102400
  • schannel: encrypted data length: 31
  • schannel: encrypted data cached: offset 31 length 103424
  • schannel: server closed the connection
  • schannel: schannel_recv cleanup
  • schannel: decrypted data returned 60
  • schannel: decrypted data buffer: offset 0 length 102400
    < HTTP/1.1 413 Request Entity Too Large
    < content-length: 0
  • HTTP error before end of send, stop sending
    <
  • Closing connection 0
  • schannel: shutting down SSL/TLS connection with myhostname port 9443
  • schannel: clear security context handle

My .bin file is of 803088 byte.

How can I solve this problem? I don’t understand if there is a configuration parameter related to local Blynk Server to increase possible file size?

I have Esp32 Sparkfun Thing module with last Blynk library version and Blynk Local Server (that runs on Raspberry Pi3 B+)

Let me know if you needs other infos.

Thanks.
Regards

No one has any idea how to solve the problem?

Hi,

I solved, changing web.request.max.size parameter in server.properties file.

Without custom server.properties file changes done to Blynk config page was lost
and I didn’t realize it, now I introdue a custom local configuration file.

Starting server with custom server.properties file and following configuration:

web.request.max.size=1524288

solved my HTTP 413 error.

Now I have to analyze and solve HTTP500…

Thanks!

Now I get HTTP 500 error for following reason:

13:07:53.437 INFO - Header auth attempt. User: admin@blynk.cc, pass: ******
13:07:53.438 DEBUG- Incoming POST /admin/ota/start
13:07:54.648 INFO - Requested OTA for all devices…
13:07:54.668 ERROR- Error during file upload.
java.lang.RuntimeException: Unable to read build number fro firmware.
at cc.blynk.utils.FileUtils.getPatternFromString(FileUtils.java:248) ~[server-0.41.10-java8.jar:?]

can be related to following define?

#define BLYNK_NO_INFO

For now (until evening) I can’t access fisically to ESP32 to update new firmware without previous define.