OpenSprinkler Forums OpenSprinkler Unified Firmware “The request was too large” error until OpenSprinkler.sh restart

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #79639

    qhvalley
    Participant

    Rebuilding my Pi system (flamed triacs, new hardware needed). Built new Pi os – Debian 12/bookworm. Compiled OSPi – 2.4.0, firmware 2.2.0 (5). On system boot, cannot connect with the app, and web access reports “The request was too large”. If I restart OSPi with the shell script, all works as expected. journalctl shows nothing obvious to me.

    Suggestions welcomed!

    #79671

    Ray
    Keymaster

    If you try to access:
    https://demo.opensprinkler.com/
    do you get the same error? The demo runs firmware 2.2.1(0) currently. The request too large error is usually due to the request header larger than the buffer size. This shouldn’t happen unless if you have a firewall or proxy that inserts additional data to the header.

    #79686

    darren.macleod
    Participant

    I have also run into the same issue.
    Starting with a fresh install i can see the webpage on port 8080 but as soon as i reboot, i get “The request was too large” in the browser window.
    I have no issues in seeing the website on the above demo.

    #79687

    adepiero
    Participant

    Same issue here. I opened an issue on the official GitHub page.

    #79688

    Ray
    Keymaster

    We are able to reproduce the issue so we are working on fixing it right now.

    #79725

    Tony Stuck
    Participant

    The request too large error is usually due to the request header larger than the buffer size. This shouldn’t happen unless if you have a firewall or proxy that inserts additional data to the header.

    Yeah, for what it’s worth, I’ve run into this also, but it’s because I expose my OpenSprinkler web UI via Cloudflare Tunnels and put Cloudflare Access in front of it, so the world can’t see. CF Access drops a few authorization cookies (just shy of 1600 bytes) which get forwarded to the OpenSprinkler server, and it sounds like that’s too much for the buffer?

    I ended up running an nginx proxy on the machine that runs my Cloudflare Tunnel to cut out the CF cookies before sending the requests to my OpenSprinkler controllers. If you’re increasing the buffer size to be able to handle this, that’d be convenient 🙂

    #79732

    Ray
    Keymaster

    We plan to address this in the next version of OTF library. Currently the incoming request is read into a 2K buffer, which is more than sufficient for most requests. Of course if Cloudflare adds a lot of extra header it can quickly exceeds the buffer size, we just didn’t know it could be a very large buffer.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.

OpenSprinkler Forums OpenSprinkler Unified Firmware “The request was too large” error until OpenSprinkler.sh restart