Spksrc: Package publication fails - CloudFlare 413 Request Entity Too Large

Created on 11 Sep 2017 · 4Comments · Source: SynoCommunity/spksrc

Since I has been granted access to repository, I have never been able to publish packages.

===>  Preparing conf
src/conf/privilege
src/conf/PKG_CONX
/spksrc/spk/tvheadend/work-bromolow-5.2/conf/privilege
/spksrc/spk/tvheadend/work-bromolow-5.2/conf/PKG_CONX
(cd /spksrc/spk/tvheadend/work-bromolow-5.2 && tar cpf /spksrc/spk/tvheadend/../../packages/tvheadend_bromolow-5.2_4.2.3-10.spk --group=root --owner=root package.tgz INFO PACKAGE_ICON.PNG PACKAGE_ICON_256.PNG scripts WIZARD_UIFILES conf)
http --verify=no --auth XXXXXXXXXXXXXXX: POST https://synocommunity.com/packages @/spksrc/spk/tvheadend/../../packages/tvheadend_bromolow-5.2_4.2.3-10.spk
HTTP/1.1 413 Request Entity Too Large
CF-RAY: 39c9aea05d773e56-ZRH
Connection: keep-alive
Content-Type: text/html
Date: Mon, 11 Sep 2017 09:43:23 GMT
Server: cloudflare-nginx
Set-Cookie: __cfduid=XXXXXXXXXXX; expires=Tue, 11-Sep-18 09:43:23 GMT; path=/; domain=.synocommunity.com; HttpOnly
Transfer-Encoding: chunked

<html>
<head><title>413 Request Entity Too Large</title></head>
<body bgcolor="white">
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx/1.4.6 (Ubuntu)</center>
</body>
</html>

make[1]: Leaving directory '/spksrc/spk/tvheadend'

As far as I understand, CloudFlare rejects my requests because of body payload length... So I wonder if other SynoCommunity members have same issues - I would say no, as noticed @cytec published recently after my first failed trial.

Source

ymartin59

Most helpful comment

Use api.synocommunity.com: that subdomain doesn't go through CloudFlare.
I think you didn't use make setup-synocommunity to setup the repo, because that's the default.

Diaoul on 12 Sep 2017

😄2 👍1

All 4 comments

Related to #2825

ymartin59 on 11 Sep 2017

uhm that seems strange!
I've had all kinds of errors when publishing SPK's over the api but mostly that where timeout or some wrong/strange duplication errors.... that one is new to me too

cytec on 12 Sep 2017

Maybe you could try with my PR #2905 since that one is ready to go?
To see if it's package dependent?

Safihre on 12 Sep 2017

Use api.synocommunity.com: that subdomain doesn't go through CloudFlare.
I think you didn't use make setup-synocommunity to setup the repo, because that's the default.

Diaoul on 12 Sep 2017

😄2 👍1

Was this page helpful?

0 / 5 - 0 ratings