Sentry-cli: 413 caused by: sentry reported an error: unknown error (http status: 413)
413
liuaaaddxiaoer
All 5 comments
Could you provide more detail on what you did, what you were expecting to happen and what happened instead?
markstory
on 6 Dec 2018
Indeed, the information you give is very limited. Maybe i can help you. I just fixed an issue where two of three uploads of debug symbols worked with sentry-cli. The non working got a error 413 -> Payload too large.
I run a self hosted instance of sentry with nginx in front for https.
In my case nginx was the one who threw the 413. To fix that, just increase the setting client_max_body_size in your nginx.conf in the http section to e.g. 100m
Hope this help someone.
siredmar
on 27 Nov 2019
Closing the issue, as it seems like the original issue has been resolved.
Please do not hesitate to ping me if it is still relevant, and I will happily reopen and work on it.
Cheers!
kamilogorek
on 5 Mar 2020
nginx.conf
I have the same issue.
My error message is:
error: API request failed
caused by: sentry reported an error: unknown error (http status: 413)
Where did i find this nginx.conf file to make the change you mentioned?
PrantikMondal
on 26 Aug 2020
nginx configuration is used in our onpremise instances - https://github.com/getsentry/onpremise/blob/master/nginx/nginx.conf
kamilogorek
on 26 Aug 2020
Related issues
ramyma
路
5Comments
tclindner
路
3Comments
BioPhoton
路
3Comments
fungilation
路
4Comments
alexregier
路
4Comments
Most helpful comment
Indeed, the information you give is very limited. Maybe i can help you. I just fixed an issue where two of three uploads of debug symbols worked with sentry-cli. The non working got a error 413 -> Payload too large.
I run a self hosted instance of sentry with nginx in front for https.
In my case nginx was the one who threw the 413. To fix that, just increase the setting
client_max_body_sizein your nginx.conf in the http section to e.g. 100mHope this help someone.