Etsi tuesta

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Lue lisää

Firefox does not sync

  • 3 vastausta
  • 7 henkilöllä on sama ongelma
  • 4 näyttöä
  • Viimeisin kirjoittaja qscgz

more options

Hi,

I've set up my own sync server and runs very well. I am able to sync between the desktop versions of Firefox without any issues.

When I try to login to an existing sync account from my Android device (Relase and the beta version), after entering the user name, password, key and URL ( https://my.url.com/mozsync/ ), Firefox complains with this error message:

"Please enter valid server URL"

I don't use any self signed certificates and I don't get any certificate warning when I connect to other services running on this host.

It looks like, that the Firefox Android browser isn't doing anything, because I don't see log on the sync server.

Hi, I've set up my own sync server and runs very well. I am able to sync between the desktop versions of Firefox without any issues. When I try to login to an existing sync account from my Android device (Relase and the beta version), after entering the user name, password, key and URL ( https://my.url.com/mozsync/ ), Firefox complains with this error message: "Please enter valid server URL" I don't use any self signed certificates and I don't get any certificate warning when I connect to other services running on this host. It looks like, that the Firefox Android browser isn't doing anything, because I don't see log on the sync server.

Kaikki vastaukset (3)

more options
more options

The URL I've entered is correct, including the leading https:// . The server runs on the standard https port 443 and I'm using official ssl certificates.

I have to say, that the sync server does not run on the webserver root. The URL in my case is something like https://my.domain.com/mozsync/ .

As mentioned, the desktop Browser syncs perfectly.

more options

Well, this seems to be a bug in the Android version of Firefox.