Kay
2011-03-02 10:59:40 UTC
Hello!
I have set up an internal Nexus repository from the bundle
nexus-oss-webapp-1.9.0.1-bundle.tar.gz.
I have added proxy repositories as well as hosted ones and address the
Nexus instance via the entry (the port 8081 had to be changed to 8181
due to concurrency)
nexus-central
Internal Nexus
http://repo-host:8181/nexus/content/groups/public
*
There are no additional repositories or mirrors configured in
settings.xml. The Nexus-repository connects to the net via a
http-proxy.
I can use the repository to build on repo-host.
On another host "sec-host", which can access repo-host without a
http-proxy, using the same settings.xml as on repo-host, I am running
into problems right at Maven's first attempt to access the Nexus
instance:
------------------------------------------------------------------------
$ mvn
[...]
Downloading:
http://repo-host:8181/nexus/content/groups/public/org/apache/maven/plugins/maven-site-plugin/2.0-beta-7/maven-site-plugin-2.0-beta-7.pom
[WARNING] Unable to get resource
'org.apache.maven.plugins:maven-site-plugin:pom:2.0-beta-7' from repository
central (http://repo1.maven.org/maven2): Error transferring file: Server
returned HTTP response code: 504 for URL:
http://repo-host:8181/nexus/content/groups/public/org/apache/maven/plugins/maven-site-plugin/2.0-beta-7/maven-site-plugin-2.0-beta-7.pom
------------------------------------------------------------------------
I can administer and browse the Nexus server from a http-browser
started on sec-host via the URL http://repo-host:8181/nexus. Also, on
sec-host I can successfully issue
wget
http://repo-host:8181/nexus/content/groups/public/org/apache/maven/plugins/maven-site-plugin/2.0-beta-7/maven-site-plugin-2.0-beta-7.pom
and download the file.
There are no proxies configured in /etc/wgetrc, and, as already
mentioned, the connection between the two machines does not need an
http-Proxy. I have verified this by deactivating http-Proxies in the
Browser on sec-host: no connection to external http-addresses (as
expected), but I can still browse http://repo-host:8181/nexus.
So it does not seem to be a network problem. Is there some access
control on the Nexus level which causes the inaccessibility? I could
not find a related entry in the documentation.
Thanks for hints!
Kay
--
View this message in context: http://maven.40175.n5.nabble.com/Nexus-repository-inaccessible-by-Maven-but-by-HTTP-Browser-and-wget-tp3406368p3406368.html
Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.
I have set up an internal Nexus repository from the bundle
nexus-oss-webapp-1.9.0.1-bundle.tar.gz.
I have added proxy repositories as well as hosted ones and address the
Nexus instance via the entry (the port 8081 had to be changed to 8181
due to concurrency)
nexus-central
Internal Nexus
http://repo-host:8181/nexus/content/groups/public
*
There are no additional repositories or mirrors configured in
settings.xml. The Nexus-repository connects to the net via a
http-proxy.
I can use the repository to build on repo-host.
On another host "sec-host", which can access repo-host without a
http-proxy, using the same settings.xml as on repo-host, I am running
into problems right at Maven's first attempt to access the Nexus
instance:
------------------------------------------------------------------------
$ mvn
[...]
Downloading:
http://repo-host:8181/nexus/content/groups/public/org/apache/maven/plugins/maven-site-plugin/2.0-beta-7/maven-site-plugin-2.0-beta-7.pom
[WARNING] Unable to get resource
'org.apache.maven.plugins:maven-site-plugin:pom:2.0-beta-7' from repository
central (http://repo1.maven.org/maven2): Error transferring file: Server
returned HTTP response code: 504 for URL:
http://repo-host:8181/nexus/content/groups/public/org/apache/maven/plugins/maven-site-plugin/2.0-beta-7/maven-site-plugin-2.0-beta-7.pom
------------------------------------------------------------------------
I can administer and browse the Nexus server from a http-browser
started on sec-host via the URL http://repo-host:8181/nexus. Also, on
sec-host I can successfully issue
wget
http://repo-host:8181/nexus/content/groups/public/org/apache/maven/plugins/maven-site-plugin/2.0-beta-7/maven-site-plugin-2.0-beta-7.pom
and download the file.
There are no proxies configured in /etc/wgetrc, and, as already
mentioned, the connection between the two machines does not need an
http-Proxy. I have verified this by deactivating http-Proxies in the
Browser on sec-host: no connection to external http-addresses (as
expected), but I can still browse http://repo-host:8181/nexus.
So it does not seem to be a network problem. Is there some access
control on the Nexus level which causes the inaccessibility? I could
not find a related entry in the documentation.
Thanks for hints!
Kay
--
View this message in context: http://maven.40175.n5.nabble.com/Nexus-repository-inaccessible-by-Maven-but-by-HTTP-Browser-and-wget-tp3406368p3406368.html
Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.