question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] Using custom sync server does not work (server returns 404)

See original GitHub issue

Steps to reproduce

Deploy your own sync server (uising docker: mozilla/syncserver:latest) behind an nginx reverse proxy with ssl). Turn on sync on firefox desktop 81.0 works fine (setting identity.sync.tokenserver.uri = https://subdomain.domain.tld/token/1.0/sync/1.5 and using default firefox accounts server). Using the same settings in firefox android 81.1.1 (setting user-defined sync server to https://subdomain.domain.tld/token/1.0/sync/1.5) fails, firefox android shows “last sync: Jan, 1st, 1970”. Debug message of self hosted syncserver shows:

INFO:mozsvc.metrics:{"code": 404, "request_time": 0.002107858657836914, "remoteAddressChain": ["141.*.*.*", "172.*.*.*"], "agent": "MozacFetch/57.0.6", "path": "https://subdomain.domain.tld/1.0/sync/1.5", "method": "GET"}

Considering the log message, it seems as if firefox android is using the wrong server url - the ‘token’ part is stripped off.

Expected behavior

Firefox android should sync with self-hosted syncserver.

Actual behavior

Sync fails.

Device information

  • Android device: Nokia 7.1, Android 10
  • Fenix version: 81.1.1(Build #2015764547)

┆Issue is synchronized with this Jira Task

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:19 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
tslprecommented, Oct 29, 2020

Tested another workaround (which doesn’t need to touch the web sever): just add a “/token” to the custom address - e.g. https://server/token/token/1.0/sync/1.5

That works…

0reactions
stale[bot]commented, May 18, 2021

See: https://github.com/mozilla-mobile/fenix/issues/17373 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error: Unable to Connect to the Sync Server. The Remote ...
There is more than one potential cause for this error. A "404" error is displayed by Internet Information Services when a requested resource...
Read more >
fresh repo init/sync gives curl 404 error on clone.bundle files
On a fresh repo init, I see this error message (ran with --trace). ... requested URL returned error: 404. Server does not provide...
Read more >
Troubleshooting Common Problems with Web Deploy
When you run into issues with Web Deploy, there are several logging ... WebException: The remote server returned an error: (404) Not Found....
Read more >
Fix the Most Common API Gateway Request Errors - Dashbird
But like every software system, it comes with its own problems. ... errors in the range of 500 to 599 mean something on...
Read more >
Installing npm package fails with 404 - node.js - Stack Overflow
And Delete all the field eg - email , auth etc. Find out what is the registry url of your application and put...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found