Uploading a larger file to the Nexus Repository

Sonatype Nexus Repository
1

Hi,
I’m using the Sonatype Nexus Repository Manager
OSS 3.26.1-02 and able to upload the artifactory to the repository. It’s working well for small sized files. For example, I’m doing the following to upload the files:

curl -v -u $(NEXUS_USERNAME):$(NEXUS_PASSWORD) \
--upload-file foo.tar.bz2 \
https://nexus.artifacts.xyz.link/repository/Applications/foo/$(NEXUS_EXE_VERSION)_foo.tar.bz2

However, if I upload the file with size of 10 GB then it gives the following error:

User-Agent: curl/7.58.0

Accept: /

Content-Length: 10676888289

Expect: 100-continue

< HTTP/1.1 413 Request Entity Too Large
< Server: nginx/1.14.0 (Ubuntu)
< Date: Thu, 24 Sep 2020 11:27:46 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
<

413 Request Entity Too Large

413 Request Entity Too Large

nginx/1.14.0 (Ubuntu) * Closing connection 0 * TLSv1.2 (OUT), TLS alert, Client hello (1):

Could you please provide me the info on how to upload the big files?

2

The response headers are clearly showing that this error is coming from nginx, not Nexus Repo.

< Server: nginx/1.14.0 (Ubuntu)

Adjust the client_body_max_size in nginx:

https://help.sonatype.com/display/NXRM3M/Run+Behind+a+Reverse+Proxy#RunBehindaReverseProxy-nginx

Regards,

Rich

3

Hi @rseddon,

Thanks for your reply. What’s the relation between ngnix and Nexus repository? Currently, I have only an account for Nexus Repository and I want to upload artifactory there. How can I adjust the client_body_max_size in nginx? Do I need to create an account for this? Sorry for the dump question, I’m just a beginner in these things.

By the way, the link you provided does not work for me. I don’t have login credentials for sonatype.

4

Sorry, use this link: https://help.sonatype.com/pages/viewpage.action?spaceKey=NXRM3&title=Run+Behind+a+Reverse+Proxy

nginx is not a part of Nexus Repo, someone has set it up in front of your instance as a reverse proxy.

5

Thanks a lot. The issue has been resolved after adjusting the client_body_max_size on nginx server.