Authentication Realm Prompt Problem

[kent.l...@gmail.com]

Well, I'm pulling my hair out with this. A deploy that worked fine
one day doesn't work today. Here is my problem...

* executing `deploy:update_code'
Authentication realm: <https://*****.********.com:443> ***************
Username: ********
Password for 'deploy': ********

but then I just get this....

** [err] Authentication realm: <https://****.*******.com:443>
***********
** [err] Username:

Of course, I can't enter anything at that point and the deploy fails
and leaves an SVN process running on the server.

I have tried everything. Any suggestions?

[kent.l...@gmail.com]

Okay, as hoped, this was something very silly. But, I thought I'd
post it up here in case this particular issue bites anyone else.

It must go back to our SVN server config. but if I don't add a
trailing slash to my "set :repository, "https://svn.server.com/
myrepo/"

then my deploys do not work. Very silly, but hopefully helps someone
else as something to try.

Kent

On Nov 19, 5:04 pm, "kent.lang...@gmail.com" <kent.lang...@gmail.com>
wrote:

[Gary King]

I have a similar problem. Your suggestion does not seem to work.

My situation is that my Subversion repository is hosted on another
computer, so when I do 'cap deploy', Capistrano gets my project from
the external SVN server, then it tries to SSH to my production
machine. That's when I get the "Authentication realm" message. It asks
for the password for the production server, I give it, then it asks
for a Username, and for whatever I put there, it just hangs
afterwards.

Any suggestions?

On Nov 20, 3:50 pm, "kent.lang...@gmail.com" <kent.lang...@gmail.com>
wrote:

[Hardbap]

@Gary -

I had the same problem. I was able to fix it by ssh into my web server
and running a svn co into a temp directory. This got rid of the
Authentication Realm error.

Hope this helps.

Mike

[Gary King]

I already tried that but it didn't seem to work. I eventually just
moved the SVN server to localhost.

[jsilva...@gmail.com]

Same problem, but checking out the project to temp directory works for
me too