Firefox Home (1.1.1) not working with sync server full !

18 views
Skip to first unread message

Franz Skale

unread,
Mar 5, 2012, 8:26:19 AM3/5/12
to servic...@mozilla.org

Dear list,
Firefox Home Iphone App ist not working with syncserver-full from the hg
repository.
The Firefox Sync works but the iphone app (1.1.1) tells me "username not
found" when i enter the details.
I found out,that the app requests
https://servername.domain.com/1.0/xxxxxxxxxxxxxxxxx/node/weave.
The Server then throws a 404 error.
I found no reference in the source to the URL.
Please tell me what to be done, to get the iphone app working with the
weave sync sever.

Thanks in advance


Franz

_______________________________________________
Services-dev mailing list
Servic...@mozilla.org
https://mail.mozilla.org/listinfo/services-dev

Franz Skale

unread,
Mar 5, 2012, 3:29:37 PM3/5/12
to Allison Naaktgeboren, servic...@mozilla.org

Hi,
my setup:
server-full from the hg default branch.

Working: FF 10.0.2 (sync setup)

the last version (before hp update) worked with the firefox home iphone am.
this version now isn't accepting the username/password/sync key provided
in the setup screen.
My server has a commercial ssl cert by the way.

Details on the iphone setup using a custom sync server (server-full
default branch): (already setup the sync with ff 10.0.2)
i fill out the details, account,password and sync key along with the server.
After one second following appears on the iphone: Username not found
And on the apache server only one line in the accesslog:

GET /user/1.0/xxxxxxxxxxxxxxxxxxxxxxx/node/weave HTTP/1.1" 404 581 "-"
"Firefox Home 1.1.1 (iPhone; iPhone OS 5.0.1; de_AT)"

When i do the same procedure on an other browser: (FF 10.0.2 ther browser)

"GET /user/1.0/a HTTP/1.1" 200 581 "-" "Firefox/10.0.2
FxSync/1.13.0.20120215223356.desktop"
"GET /user/1.0/xxxxxxxxxxxxxxxxxxxxxxxxxxx HTTP/1.1" 200 420 "-"
"Firefox/10.0.2 FxSync/1.13.0.20120215223356.desktop"
"PUT /user/1.0/xxxxxxxxxxxxxxxxxxxxxxxxxxx HTTP/1.1" 200 613 "-"
"Firefox/10.0.2 FxSync/1.13.0.20120215223356.desktop"
"GET /user/1.0/xxxxxxxxxxxxxxxxxxxxxxxxxxx/node/weave HTTP/1.1" 404 500
"-" "Firefox/10.0.2 FxSync/1.13.0.20120215223356.desktop"
"GET /1.1/xxxxxxxxxxxxxxxxxxxxxxxxxxx/info/collections HTTP/1.1" 200 474
"-" "Firefox/10.0.2 FxSync/1.13.0.20120215223356.desktop"
"GET /1.1/xxxxxxxxxxxxxxxxxxxxxxxxxxx/storage/meta/global HTTP/1.1" 200
794 "-" "Firefox/10.0.2 FxSync/1.13.0.20120215223356.desktop"
"GET /1.1/xxxxxxxxxxxxxxxxxxxxxxxxxxx/info/collections HTTP/1.1" 200 474
"-" "Firefox/10.0.2 FxSync/1.13.0.20120215223356.desktop"
"GET /1.1/xxxxxxxxxxxxxxxxxxxxxxxxxxx/storage/crypto/keys HTTP/1.1" 200
682 "-" "Firefox/10.0.2 FxSync/1.13.0.20120215223356.desktop"
"GET /1.1/xxxxxxxxxxxxxxxxxxxxxxxxxxx/info/collections HTTP/1.1" 200 635
"-" "Firefox/10.0.2 FxSync/1.13.0.20120215223356.desktop"
"GET /1.1/xxxxxxxxxxxxxxxxxxxxxxxxxxx/storage/meta/global HTTP/1.1" 200
794 "-" "Firefox/10.0.2 FxSync/1.13.0.20120215223356.desktop"
"GET /1.1/xxxxxxxxxxxxxxxxxxxxxxxxxxx/info/collections HTTP/1.1" 200 474
"-" "Firefox/10.0.2 FxSync/1.13.0.20120215223356.desktop"
"GET /1.1/xxxxxxxxxxxxxxxxxxxxxxxxxxx/storage/crypto/keys HTTP/1.1" 200
682 "-" "Firefox/10.0.2 FxSync/1.13.0.20120215223356.desktop"

So the iphone app is not requesting the right url to check, that the
user exists in the store.
I found a test script in the deps directory which refers to the url
/node/weave.

Rgds.
Franz

Am 05.03.12 20:52, schrieb Allison Naaktgeboren:
> Hi Franz,
> The does it function with the desktop sync client (embedded inside firefox)? It is unclear to me from your report if the issue is with your server-full setup or with the iphone app.
>
> thanks,
> Ally

Toby Elliott

unread,
Mar 5, 2012, 5:18:29 PM3/5/12
to i....@dah.am, servic...@mozilla.org, Allison Naaktgeboren
The 404 is actually the correct response from most server installs. It should be interpreted by the client as "this server doesn't do separate node assignment, use the same domain that you used for this request".

You can see that behavior from the other browser below, so it seems like it's something quirky in FF Home that may have changed in the last update.

Toby

Fabian Wenk

unread,
Mar 6, 2012, 5:20:10 AM3/6/12
to servic...@mozilla.org
Hello Franz

On 05.03.2012 14:26, Franz Skale wrote:
> Firefox Home Iphone App ist not working with syncserver-full from the hg
> repository.
> The Firefox Sync works but the iphone app (1.1.1) tells me "username not
> found" when i enter the details.

I had seen this same errors also when I did my first setup of
server-full. But after sorting out some stuff with Toby, I got it
working. See my "Mozilla Custom Sync Server Installation on
FreeBSD" [1] guide.

[1] http://www.wenks.ch/fabian/mozilla-custom-sync-server/

It is important to have done the 'hg clone ...' after 06.
February 2012.

> I found out,that the app requests
> https://servername.domain.com/1.0/xxxxxxxxxxxxxxxxx/node/weave.
> The Server then throws a 404 error.

In the etc/sync.conf (with my guide it is in
etc/mozilla-sync.conf) the following section needs to be set
correctly:

[nodes]
fallback_node = https://mozilla-sync.example.com/

> I found no reference in the source to the URL.
> Please tell me what to be done, to get the iphone app working with the
> weave sync sever.

Just follow my install guide, after this Firefox Home 1.1.1 does
work.


bye
Fabian

Franz Skale

unread,
Mar 6, 2012, 7:28:02 PM3/6/12
to Fabian Wenk, servic...@mozilla.org

Hi,
you forgot to mention, that you must set that value in the FF config:

1.) about:config
2.) services.sync.clusterURL == services.sync.serverURL

Then the sync process works.
Why, the services.sync.clusterURL isn't set automatically via initial
sync request ?

Thanks

Franz


Am 06.03.12 11:20, schrieb Fabian Wenk:

Franz Skale

unread,
Mar 6, 2012, 2:47:17 PM3/6/12
to Fabian Wenk, servic...@mozilla.org


Hi,
thanks it works now.
But now the reCaptache feature isn't working anymore.
I'am feeling quite uncomfortable without Captcha.
Perhaps anyone knows a solution for the problem:

Details:

GET /misc/1.0/captcha_html HTTP/1.1" 404 500 "-" "Mozilla/5.0
(Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20100101 Firefox/10.0.2"

Of course, i enable captcha and generated a reCaptcha Keypair.


King regards

Franz


Am 06.03.12 11:20, schrieb Fabian Wenk:

Jethro Carr

unread,
Mar 6, 2012, 8:28:18 PM3/6/12
to i....@dah.am, Fabian Wenk, servic...@mozilla.org
On Wed, 2012-03-07 at 01:28 +0100, Franz Skale wrote:
> you forgot to mention, that you must set that value in the FF config:
>
> 1.) about:config
> 2.) services.sync.clusterURL == services.sync.serverURL
>
> Then the sync process works.
> Why, the services.sync.clusterURL isn't set automatically via initial
> sync request ?

hi Franz,

I was seeing this exact issue with all Firefox clients before I upgraded
my server to the latest release, not sure if it's the issue you're
seeing, but it sounds similar.


1. Make sure you've updated, there was a bug I came across that caused
this issue, I opened a bug report about it:
https://bugzilla.mozilla.org/show_bug.cgi?id=727395

Turned out to be a duplicate of a known issue that was fixed in late
Feb: https://bugzilla.mozilla.org/show_bug.cgi?id=721558


2. Make sure fallback_node is properly set, in the new [nodes]
configuration example - see the latest sample configurations in trunk
for example.

regards,
jethro

--
Jethro Carr
www.jethrocarr.com
www.amberdms.com

signature.asc

Fabian Wenk

unread,
Mar 7, 2012, 8:57:14 AM3/7/12
to servic...@mozilla.org
Hello Franz

On 06.03.2012 20:47, Franz Skale wrote:
> thanks it works now.

You're welcome!

> But now the reCaptache feature isn't working anymore.
> I'am feeling quite uncomfortable without Captcha.

Sorry, I can not help you here, I do not use the Captcha. I think
if the URL of your Sync Server it not known to the public, then
nobody will (ab)use your server. So it does not matter if there
is a Captcha or not.

Maybe somebody else on this mailing list is able to help you with
the Captcha.

Fabian Wenk

unread,
Mar 7, 2012, 9:01:25 AM3/7/12
to servic...@mozilla.org
Hello Franz

On 07.03.2012 01:28, Franz Skale wrote:

> you forgot to mention, that you must set that value in the FF config:
>
> 1.) about:config
> 2.) services.sync.clusterURL == services.sync.serverURL

I did not forget this, it was not needed with my installation.
Probably this is only needed, when there was already a setup with
an other sync server (eg. from Mozilla, or with the old weave
server) running.

Before I started to connect my Firefox to my new sync server, I
did deactivate the old weave setup in the Preferences and even
restarted Firefox.

> Then the sync process works.
> Why, the services.sync.clusterURL isn't set automatically via initial
> sync request ?

This should be done automatically. Is in the [nodes] section the
'fallback_node' set correctly?

Franz Skale

unread,
Mar 7, 2012, 4:31:46 AM3/7/12
to Jethro Carr, Fabian Wenk, servic...@mozilla.org


Hi Jethro,
i am sorry to say, that the FF Home Iphone App throws an error on
connecting to the msync server.
So it's not working.

Logfile on the webserver:

==> /var/log/apache2/sync-error.log <==
"GET /1.1/xxxxxxxxxxxxxxxxxxxxxxxxxxx/info/collections HTTP/1.1" 200
227 "-" "Firefox Home 1.1.1 (iPhone; iPhone OS 5.0.1)"
"GET /1.1/xxxxxxxxxxxxxxxxxxxxxxxxxxx/info/collections HTTP/1.1" 200 227
"-" "Firefox Home 1.1.1 (iPhone; iPhone OS 5.0.1)"

==> /var/log/apache2/sync-access.log <==
"GET /user/1.0/5zzx6xni5myldcxwg36vcqujfkhpynvb/node/weave HTTP/1.1" 200
667 "-" "Firefox Home 1.1.1 (iPhone; iPhone OS 5.0.1)"

Error on FF Home on Iphone:

Communication to the server failed with error (5)

Regards

Franz

Am 07.03.12 02:28, schrieb Jethro Carr:

Franz Skale

unread,
Mar 7, 2012, 5:02:01 AM3/7/12
to Jethro Carr, Fabian Wenk, servic...@mozilla.org


Hi, i now applied rpm-1.0.2 tag.
Now, after initial setup following value is appended to the
services.sync.clusterURL:
{"passwords": 1331112366.22, "crypto": 1331079682.38, "forms":
1331112308.26, "meta": 1331079817.77, "bookmarks": 1331112304.31,
"prefs": 1331112366.83, "history": 1331113887.45}

But this should be: https://sync.example.com/


Rgds.

Franz


Am 07.03.12 02:28, schrieb Jethro Carr:

Franz Skale

unread,
Mar 7, 2012, 7:56:36 AM3/7/12
to Jethro Carr, Fabian Wenk, servic...@mozilla.org


Hi Jethro,
i also tried your hotfix mentioned in the bug report.
No changes.
No i did a GET Reuquest on the following url:

https://mysyncserver.example.com/user/1.0/xxxxxxxxxxxxxxxxxxx/node/weave

Output:
{"passwords": 1331123182.01, "tabs": 1331123183.25, "clients": 1331123043.54, "crypto": 1331114659.64, "forms": 1331123273.69, "meta": 1331114721.81, "bookmarks": 1331123101.81, "prefs": 1331123182.64, "history": 1331123175.55}

This has nothing to do with the fallback_node in the config file.


Iphone Debug:
Mar  7 13:46:51 unknown FirefoxHome[504] <Warning>: using custom server: https://msync.example.com/
Mar  7 13:46:52 unknown FirefoxHome[504] <Warning>: Failed to initialize CryptoManager
>   7 13:47:09 unknown FirefoxHome[504] <Warning>: unable to delete private key, already deleted
Mar  7 13:47:09 unknown FirefoxHome[504] <Warning>: using custom server: https://msync.example.com/
Mar  7 13:47:10 unknown FirefoxHome[504] <Warning>: Failed to initialize CryptoManager

Rgds.

Franz


Am 07.03.12 02:28, schrieb Jethro Carr:
On Wed, 2012-03-07 at 01:28 +0100, Franz Skale wrote:

Franz Skale

unread,
Mar 7, 2012, 9:38:22 AM3/7/12
to servic...@mozilla.org, Fabian Wenk

Hi Fabian,
i made a fresh install with a new database.
Sent already debugging outputs.(FF and FF HOME)

Ciao

Franz

Am 07.03.12 15:01, schrieb Fabian Wenk:

Franz Skale

unread,
Mar 10, 2012, 5:03:39 AM3/10/12
to Fabian Wenk, servic...@mozilla.org



So, that there's no anwser over the week i want to ask, how to debug the wrong value sent via syncreg.
Since i setup a new server (yesterday), after deployment of the exact same sync.conf in the rpm-1.0.2 branch, i can tell that the value of fallback_node is not provided.
The quota values are provided so that when setup a new sync account. you must configure about:config dureing the process of initial setup.
Manually adding works, but the iphone captches another problem. (CryptoManager).


Rgds.
Franz


Am 07.03.12 13:56, schrieb Franz Skale:
Reply all
Reply to author
Forward
0 new messages