-
Add in nginx config a
client_max_body_size 250M;250M- custom size for you needs. -
You are right, that was the issue! I didn't consider at all that my zipped artifacts would go past that default configured limit. Thank you.
-
Previous Value Current Value Open
Closed
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Affected Versions |
Not Found
|
Issue Votes (0)
I followed the reverse proxy instructions from here: https://code.onedev.io/projects/162/files/main/pages/reverse-proxy-setup.md. My OneDev 7.4.9 setup release runs on my Raspberry Pi bare-metal (because there's no Docker Image for aarm64), following the instructions from here: https://code.onedev.io/projects/162/files/main/pages/run-on-bare-metal-machine.md.
I have my agent started and configured on my desktop PC and configured as an executor on the OneDev server. When I specify the
serverUrlin the agent'sconf/agent.propertiesas an IP with port (e.g.http\://192.168.178.24:6610) everything works perfectly. However, when I specify theserverUrlin the agent'sconf/agent.propertiesusing my internal domain:http://onedev.raspberry-pi.localevery step of the build process seems to work, except the last publish step -- which fails:There doesn't seem to be anything additional on the server's
log/server.logaround that time, but clearly something is failing with the nginx proxied web request. Here's my nginx configuration for OneDev:Any idea what I'm doing wrong?