Cannot deploy file except on localhost

[Steve Schwartz]

We have Nexus and TeamCity (Maven build engine) on one server.  Running a Maven deploy build works only on that machine.  Trying to deploy from any other intranet machine, with the same username/password, generates a 401 from Nexus.

We do not have a proxy in the middle, though the Nexus server and the (failing) Maven clients are on separate subnets (no intervening firewalls).  We're using the embedded server; no Apache, etc.

Thanks,
Steve

[Tamás Cservenák]

Hi there,

are you sure that "any other intranet machine" has properly set up username/passwords? 401 response suggests it is not, at least the deploying clients (i guess maven) is not sending them, or is not able to response to challenge.

Thanks,

~t~

On Tue, Oct 13, 2009 at 4:56 PM, Steve Schwartz <schwartz@...> wrote:

We have Nexus and TeamCity (Maven build engine) on one server.  Running a
Maven deploy build works only on that machine.  Trying to deploy from any
other intranet machine, with the same username/password, generates a 401
from Nexus.

We do not have a proxy in the middle, though the Nexus server and the
(failing) Maven clients are on separate subnets (no intervening firewalls).
We're using the embedded server; no Apache, etc.

Thanks,
Steve

--
View this message in context: http://www.nabble.com/Cannot-deploy-file-except-on-localhost-tp25874497p25874497.html
Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Steve Schwartz]

I copied the remote credentials into the localhost settings.xml.  Confirmed that the credentials are correct.  In fact, two Nexus credentials are good on the localhost Maven client, but not on remote clients.

Tamás Cservenák wrote:

Hi there,
are you sure that "any other intranet machine" has properly set up
username/passwords? 401 response suggests it is not, at least the deploying
clients (i guess maven) is not sending them, or is not able to response to
challenge.

On Tue, Oct 13, 2009 at 4:56 PM, Steve Schwartz <[e-mail]>wrote:

>
> We have Nexus and TeamCity (Maven build engine) on one server.  Running a
> Maven deploy build works only on that machine.  Trying to deploy from any
> other intranet machine, with the same username/password, generates a 401
> from Nexus.
>
> We do not have a proxy in the middle, though the Nexus server and the
> (failing) Maven clients are on separate subnets (no intervening firewalls).
> We're using the embedded server; no Apache, etc.

[Brian Fox]

Check the rss feeds to see how Nexus sees those connections (which
user, etc). Nothing obvious comes to mind except those maven clients
aren't sending the correct credentials.

On Tue, Oct 13, 2009 at 10:56 AM, Steve Schwartz <schwartz@...> wrote:

>
> We have Nexus and TeamCity (Maven build engine) on one server.  Running a
> Maven deploy build works only on that machine.  Trying to deploy from any
> other intranet machine, with the same username/password, generates a 401
> from Nexus.
>
> We do not have a proxy in the middle, though the Nexus server and the
> (failing) Maven clients are on separate subnets (no intervening firewalls).
> We're using the embedded server; no Apache, etc.
>
> Thanks,
> Steve
>
> --
> View this message in context: http://www.nabble.com/Cannot-deploy-file-except-on-localhost-tp25874497p25874497.html
> Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-user-unsubscribe@...
> For additional commands, e-mail: nexus-user-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Brian Fox]

Are you using apache httpd as a proxy on that machine? (you said no
apache in the first email, but I'm double checking). If so, it's
possible that when you access externally, it's going through httpd and
it's grabbing the authentication.

On Tue, Oct 13, 2009 at 11:16 AM, Steve Schwartz <schwartz@...> wrote:

>
> I copied the remote credentials into the localhost settings.xml.  Confirmed
> that the credentials are correct.  In fact, two Nexus credentials are good
> on the localhost Maven client, but not on remote clients.
>
>
> Tamás Cservenák wrote:
>>
>> Hi there,
>> are you sure that "any other intranet machine" has properly set up
>> username/passwords? 401 response suggests it is not, at least the
>> deploying
>> clients (i guess maven) is not sending them, or is not able to response to
>> challenge.
>>
>> On Tue, Oct 13, 2009 at 4:56 PM, Steve Schwartz
>> <schwartz@...>wrote:
>>
>>>
>>> We have Nexus and TeamCity (Maven build engine) on one server.  Running a
>>> Maven deploy build works only on that machine.  Trying to deploy from any
>>> other intranet machine, with the same username/password, generates a 401
>>> from Nexus.
>>>
>>> We do not have a proxy in the middle, though the Nexus server and the
>>> (failing) Maven clients are on separate subnets (no intervening
>>> firewalls).
>>> We're using the embedded server; no Apache, etc.
>>
>
> --
> View this message in context: http://www.nabble.com/Cannot-deploy-file-except-on-localhost-tp25874497p25874837.html
> Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-user-unsubscribe@...
> For additional commands, e-mail: nexus-user-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...