Bug #437165 “UbuntuOne stuck in an endless authentication loop (...” : Bugs : ubuntuone-client package : Ubuntu

Revision history for this message

Tonnerre LOMBARD (tonnerre) wrote on 2009-09-26:

#1

.home.tonnerre..cache.ubuntuone.log.oauth.login.log.txt Edit (9.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.9 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (211 bytes, text/plain; charset="utf-8")

Revision history for this message

Joshua Hoover (joshuahoover) wrote on 2009-10-08:

#2

Hi Tonnerre, I'm sorry you experienced this problem with authentication. Have you tried since you filed this bug? If you can give an update it is much appreciated. Thank you, Joshua

Changed in ubuntuone-client (Ubuntu):
status:	New → Incomplete
Changed in ubuntuone-client:
status:	New → Incomplete

Revision history for this message

Tonnerre LOMBARD (tonnerre) wrote on 2009-10-10:

#3

Salut, Joshua,

Yes, the bug is still existent right in this moment. The only change is that now, instead of a rather random base64 string, it actually displays the correct host name. Still, it is stuck in an endless authentication loop as described.

Tonnerre

Revision history for this message

Joshua Hoover (joshuahoover) wrote on 2009-10-14:

#4

Hi Tonnerre,

I apologize for the inconvenience this has caused you. Can you please make sure you have all the latest Karmic updates (in particular, ubuntuone-client 1.0) and let me know if this problem persists?

Thank you,

Joshua

Revision history for this message

Tonnerre LOMBARD (tonnerre) wrote on 2009-10-20:

#5

Dear Joshua,

I have them and the problem persists.

Regards,
Tonnerre

Revision history for this message

Pete24v (pete-martin) wrote on 2009-10-30:

#6

sounds like i have the same problem too. On a fresh install of Karmic with all updates.

Revision history for this message

palinz (palinz) wrote on 2009-11-11:

#7

Same problem here. Upgraded to Karmic yesterday and updated right now.
U1 worked well for a day, then, after a system-crash, I'm now in the authentication loop. I tried to remove and reinstall by following https://answers.edge.launchpad.net/ubuntuone-client/+faq/778 without results.

Other detail:
The crash was not related to U1, I guess, but to my old graphic card problems (it happened during a screensaver-preview), but maybe U1 was syncing during crash (?).

Revision history for this message

Matt Griffin (mattgriffin) wrote on 2009-11-12:

#8

It seems to only put me in this loop after I come out of suspend and restart the client app.

Revision history for this message

Pete24v (pete-martin) wrote on 2009-11-12:

#9

it's now happening on my 64bit machine, 2 older machines work fine. All on Karmic. The 64bit machine has worked fine since the upgrade from Jaunty

Revision history for this message

Joshua Blount (jblount) wrote on 2009-11-12:

#10

The only way (so far) that I've been able to recreate this is by *not* putting in my password when the "Unlock Keyring" dialog comes up.

Can anyone confirm that they've seen this and put in their password in the "Unlock Keyring" dialog box when their computer first boots?

Changed in ubuntuone-client (Ubuntu):
status:	Incomplete → Confirmed
Changed in ubuntuone-client:
status:	Incomplete → Confirmed
tags:	added: desktop+
Changed in ubuntuone-client:
importance:	Undecided → Medium

Revision history for this message

palinz (palinz) wrote on 2009-11-12:

#11

I've put my pwd into the "Unlock Keyring" dialog the first time I started U1 and all was working well for the 1st day, until the above mentioned system-crash. Now, from when the bug rise up, even after removing and reinstalling, NO "Unlock Keyring" dialog appears, just the web browser going to the "add this computer" page.

Revision history for this message

palinz (palinz) wrote on 2009-11-12:

#12

Back home right now, I started U1 and I was redirected to the website for the usual "add this computer"... After logging, I was prompted for "Sign in to Launchpad" and, clicking on "I'm someone else" instead on "Sign In", U1 restarted to work. Now also tomboy sync works again, after resetting from the tomboy sync preference menu and this time "Sign In" was right.

I hope my explanation is understandable, sorry, tired and not EN mothertongue.

Thanks

Rick McBride (rmcbride) on 2009-11-13

Changed in ubuntuone-client:
importance:	Medium → Critical

Revision history for this message

Rick McBride (rmcbride) wrote on 2009-11-13:

#13

Download full text (3.4 KiB)

The following is turning up in the oauth logs of associated bug reports:

Token was not successfully retrieved: data was '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Proxy Error</title>
</head><body>
<h1>Proxy Error</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
The proxy server could not handle the request <em><a href="/oauth/request/">POST /oauth/request/</a></em>.<p>
Reason: <strong>Error reading from remote server</strong></p></p>
<hr>
<address>Apache/2.2.8 (Ubuntu) mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.8 OpenSSL/0.9.8g Server at one.ubuntu.com Port 443</address>
</body></html>
'
Got an OAuth error with no message.
Starting Ubuntu One client version 1.0.1
Token was not successfully retrieved: data was '<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The requested URL could not be retrieved</TITLE>
<STYLE type="text/css"></STYLE>
</HEAD><BODY>
<H1>ERROR</H1>
<H2>The requested URL could not be retrieved</H2>
<HR noshade size="1px">
<P>
While trying to retrieve the URL:
<A HREF="http://one.ubuntu.com/oauth/request/">http://one.ubuntu.com/oauth/request/</A>
<P>
The following error was encountered:
<UL>
<LI>
<STRONG>
Unable to forward this request at this time.
</STRONG>
</UL>

<P>
This request could not be forwarded to the origin server or to any
parent caches. The most likely cause for this error is that:
<UL>
<LI>The cache administrator does not allow this cache to make
direct connections to origin servers, and
<LI>All configured parent caches are currently unreachable.
</UL>
<P>Your cache administrator is <A HREF="mailto:webmaster">webmaster</A>.

<BR clear="all">
<HR noshade size="1px">
<ADDRESS>
Generated Sun, 18 Oct 2009 21:04:55 GMT by mulberry.canonical.com (squid/2.6.STABLE18)
</ADDRESS>
</BODY></HTML>
'
Got an OAuth error with no message.
Starting Ubuntu One client version 1.0.1
Token was not successfully retrieved: data was '<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The requested URL could not be retrieved</TITLE>
<STYLE type="text/css"></STYLE>
</HEAD><BODY>
<H1>ERROR</H1>
<H2>The requested URL could not be retrieved</H2>
<HR noshade size="1px">
<P>
While trying to retrieve the URL:
<A HREF="http://one.ubuntu.com/oauth/request/">http://one.ubuntu.com/oauth/request/</A>
<P>
The following error was encountered:
<UL>
<LI>
<STRONG>
Unable to forward this request at this time.
</STRONG>
</UL>

<P>
This request could not be forwarded to the origin server or to any
parent caches. The most likely cause for this error is that:
<UL>
<LI>The cache administrator does not allow this cache to make
direct connections to origin servers, and
<LI>All configured par...

The following is turning up in the oauth logs of associated bug reports:

Token was not successfully retrieved: data was '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Proxy Error</title>
</head><body>
<h1>Proxy Error</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
The proxy server could not handle the request <em><a href="/oauth/request/">POST&nbsp;/oauth/request/</a></em>.<p>
Reason: <strong>Error reading from remote server</strong></p></p>
<hr>
<address>Apache/2.2.8 (Ubuntu) mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.8 OpenSSL/0.9.8g Server at one.ubuntu.com Port 443</address>
</body></html>
'
Got an OAuth error with no message.
Starting Ubuntu One client version 1.0.1
Token was not successfully retrieved: data was '<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The requested URL could not be retrieved</TITLE>
<STYLE type="text/css"></STYLE>
</HEAD><BODY>
<H1>ERROR</H1>
<H2>The requested URL could not be retrieved</H2>
<HR noshade size="1px">
<P>
While trying to retrieve the URL:
<A HREF="http://one.ubuntu.com/oauth/request/">http://one.ubuntu.com/oauth/request/</A>
<P>
The following error was encountered:
<UL>
<LI>
<STRONG>
Unable to forward this request at this time.
</STRONG>
</UL>

<P>
This request could not be forwarded to the origin server or to any
parent caches.  The most likely cause for this error is that:
<UL>
<LI>The cache administrator does not allow this cache to make 
    direct connections to origin servers, and
<LI>All configured parent caches are currently unreachable.
</UL>
<P>Your cache administrator is <A HREF="mailto:webmaster">webmaster</A>.

<BR clear="all">
<HR noshade size="1px">
<ADDRESS>
Generated Sun, 18 Oct 2009 21:04:55 GMT by mulberry.canonical.com (squid/2.6.STABLE18)
</ADDRESS>
</BODY></HTML>
'
Got an OAuth error with no message.
Starting Ubuntu One client version 1.0.1
Token was not successfully retrieved: data was '<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The requested URL could not be retrieved</TITLE>
<STYLE type="text/css"></STYLE>
</HEAD><BODY>
<H1>ERROR</H1>
<H2>The requested URL could not be retrieved</H2>
<HR noshade size="1px">
<P>
While trying to retrieve the URL:
<A HREF="http://one.ubuntu.com/oauth/request/">http://one.ubuntu.com/oauth/request/</A>
<P>
The following error was encountered:
<UL>
<LI>
<STRONG>
Unable to forward this request at this time.
</STRONG>
</UL>

<P>
This request could not be forwarded to the origin server or to any
parent caches.  The most likely cause for this error is that:
<UL>
<LI>The cache administrator does not allow this cache to make 
    direct connections to origin servers, and
<LI>All configured parent caches are currently unreachable.
</UL>
<P>Your cache administrator is <A HREF="mailto:webmaster">webmaster</A>.

<BR clear="all">
<HR noshade size="1px">
<ADDRESS>
Generated Sun, 18 Oct 2009 22:43:47 GMT by mulberry.canonical.com (squid/2.6.STABLE18)
</ADDRESS>
</BODY></HTML>
'

Revision history for this message

Rick McBride (rmcbride) wrote on 2009-11-13:

#14

We have two problems here.

1: under some circumstances the oauth dance results in a 502 from the server. This is likely a configuration issue that needs to be fixed, perhaps by adding a cache exception for the /oauth path (thanks, jdo)

2: the http-client code should complain about the HTTP status instead 1) trying to interpret the body of the response, and 2) then trying again. (thanks Chad)

Lucio Torre (lucio.torre) on 2009-11-25

Changed in ubuntuone-client:
assignee:	nobody → John Lenton (chipaca)

John Lenton (chipaca) on 2009-12-03

Changed in ubuntuone-client:
assignee:	John Lenton (chipaca) → Rodney Dawes (dobey)

Revision history for this message

dobey (dobey) wrote on 2009-12-03:

#15

The client code doesn't retry if it fails to get a token. It only retries when syncdaemon tells the applet that auth has failed. If you fail to get a token due to a 50x error on the server or something similar, then you get a somewhat unreadable error dialog full of html, and you will have to click on "Connect" in the applet (or quit/restart it), to attempt getting another token. The error message is unfortunate, but I don't think it's something to consider critical.

All the instances of the bug where the loop does happen seem to be related to errors in the protocol getting misinterpreted as auth errors, for which the applet sees AUTH_FAILED status, and attempts to get a new token, as presumably the current/old one is invalid now. This has already been fixed by Facundo in trunk, and is in the queue to land in an SRU with several other fixes, which I hope to get out this week. Upgrading to the beta PPA packages should resolve this case, so I don't think it should be considered critical either.

If this is reproducable with nightlies/beta PPA packages, and a lot of people are seeing it, then I think we can consider it critical, and in need of another new fix. If it's then only happening in the 1.0.2 package in Karmic still, we need to raise the priority on the packaging bug task for the bug which has already been fixed, and get it in an SRU asap.

Revision history for this message

Michael Krelin (hacker-klever) wrote on 2009-12-03:

#16

Rodney, the problem persists with 1.1+r283-0ubuntu1~ppa1~karmic. I haven't dig any deeper than what's on the surface, but I do not get visible 50x pages. Server-side errors may occur, of course, during direct oauth communications. u1sync --authorize yields AUTHENTICATION_FAILED. Server errors are easy to verify on the server side, though.

Revision history for this message

dobey (dobey) wrote on 2009-12-03: Re: [Bug 437165] Re: UbuntuOne stuck in an endless authentication loop (always changes to«Authentication failed»)

#17

On Thu, 03 Dec 2009 20:41:07 -0000
Michael Krelin <email address hidden> wrote:

> Rodney, the problem persists with 1.1+r283-0ubuntu1~ppa1~karmic. I
> haven't dig any deeper than what's on the surface, but I do not get
> visible 50x pages. Server-side errors may occur, of course, during
> direct oauth communications. u1sync --authorize yields
> AUTHENTICATION_FAILED. Server errors are easy to verify on the server
> side, though.
>

Can you please attach your oauth-login.log from when this occurs? The
page isn't visible, but you should see an error dialog with a bunch of
unreadable text that has been ellipsized in it, if you are getting a
50x error from the server, after clicking "Allow this computer," or
when getting the initial request token (which is normally seamless).

Revision history for this message

Michael Krelin (hacker-klever) wrote on 2009-12-03:

#18

oauth-login.log Edit (2.2 KiB, text/plain)

I meant there is nothing hinting on 50x occurance. No dialogs with anything html-like either. Actually, no dialogs at all (except for that in the browser).

dobey (dobey) on 2009-12-04

Changed in ubuntuone-client:
importance:	Critical → Medium
status:	Confirmed → Fix Committed

Revision history for this message

dobey (dobey) wrote on 2009-12-04:

#19

Hi Michael,

I think you might be seeing a new issue perhaps. Can you file a new bug by right clicking on the applet and choosing "Report a Problem" immediately after trying this again? This way we'll have the latest copies of any necessary logs to look through, and we can track your issue there.

Thanks again.

Revision history for this message

Michael Krelin (hacker-klever) wrote on 2009-12-04:

#20

Rodney, I will, as soon as I restart X - the report will have absolutely no information that I haven't presented here, but will contain huge log of rythmbox's assertions in .xsession-errors. I am not in a hurry to get ubutuone running, I just wanted to help to track it down. So if you're also not in a hurry, clean report will be more useful. Thanks for your time.

Revision history for this message

dobey (dobey) wrote on 2009-12-22:

#21

Thi sis a dup of bug #450633

Chad Miller (cmiller) on 2010-01-12

Changed in ubuntuone-servers:
status:	New → Confirmed
importance:	Undecided → Medium

Chad Miller (cmiller) on 2010-01-12

Changed in ubuntuone-servers:
assignee:	nobody → Stuart Langridge (sil)

Revision history for this message

Flash (cyrille-gordon) wrote on 2010-01-28:

#22

I've the same problem Ubuntu One don't want authenticate but :
I 've launched Tomboy and i've configured it for synchronizing with my UbuntuOne Account :
The OpenID's authentification process runs normally and the Tomboy Notes are synchronized with my UbuntuOne Account.
But UbuntuOne's Folder won't synchronize and i continue to have an infinite loop on authentication with UbunutOne Client every time i launch UbunutOne Client.

Revision history for this message

Ioannis Vranos (cppdeveloper) wrote on 2010-01-28:

#23

I had created bug report: https://bugs.launchpad.net/ubuntuone-client/+bug/466632

which has been marked as duplicate with this one.

What I had reported was:

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

OS: Ubuntu 9.10 x64.

I have created a free account in Ubuntu one, and I am having only one PC, a laptop. However it prompts me again and again, to add the machine, as if it is a different machine, and now two machines are listed in "Computers on your account".

I have erased one or more such entries previously.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

However since some time ago, I have stopped experiencing this problem, I assume it has been fixed. So I am not sure whether the issue I had, is related to this one.

dobey (dobey) on 2010-04-05

Changed in ubuntuone-client:
status:	Fix Committed → Fix Released

John O'Brien (jdobrien) on 2010-05-06

Changed in ubuntuone-servers:
status:	Confirmed → Fix Released

Kevin Kappler (service-cms44) on 2010-09-10

Changed in ubuntuone-servers:
status:	Fix Released → Fix Committed
Changed in ubuntuone-client (Ubuntu):
status:	Confirmed → Fix Committed
Changed in clipgrab:
status:	New → Fix Committed

dobey (dobey) on 2010-09-10

Changed in ubuntuone-client (Ubuntu):
status:	Fix Committed → Fix Released
Changed in ubuntuone-servers:
status:	Fix Committed → Fix Released
Changed in clipgrab:
status:	Fix Committed → Invalid

Revision history for this message

Tonnerre LOMBARD (tonnerre) wrote on 2013-06-03:

#24

Fun fact: even in 13.04, Ubuntu One still isn't working for me, it's stuck at «Getting information, please wait…»

Revision history for this message

Tonnerre LOMBARD (tonnerre) wrote on 2013-06-03:

#25

Salut,

In the upper right corner I see:

File Sync error. (auth failed (AUTH_FAILED))

Ubuntu
ubuntuone-client package

UbuntuOne stuck in an endless authentication loop (always changes to «Authentication failed»)

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

	Status	Importance	Assigned to
Clipgrab	Invalid	Undecided	Unassigned
Ubuntu One Client	Fix Released	Medium	dobey
Ubuntu One Servers	Fix Released	Medium	Stuart Langridge
ubuntuone-client (Ubuntu)	Fix Released	Undecided	Unassigned

Ubuntuubuntuone-client package

UbuntuOne stuck in an endless authentication loop (always changes to «Authentication failed»)

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
ubuntuone-client package