@lexaiden By now, there are two thinks that are not added by tokenserver automatically.
- A service pattern (that is what you did)
- Your node with your server-url (Explained in "Troubleshooting"->"Node is not automatically added" in my how-to comment.)
The nodes-service-ID should be the same ID of "sync-1.5" pattern (and not the ID of "sync.1.1" pattern or any other ID that does not exists.)
In both of my sql-examples (Insert-nodes-sql and Insert-services-sql) I used id 2 for "sync-1.5" pattern.
But you should check, if you also used the same id (for example ID 2).
Pinned Comments
jewelux commented on 2021-12-12 19:15 (UTC) (edited on 2023-01-12 18:59 (UTC) by jewelux)
Database
To setup a fresh MySQL DB and user:
(mysql -u root)
:Config
Open file
/etc/firefox-syncstorage.toml
to set your own parameters. Here is an example.Firefox
In
abount:config
change tokenserver url to your service url.Run service
systemctl start firefox-syncstorage.service
Add node record
Currently it is necessary to add your node (incl. service pattern) to tokenserver database.
Your can add the node record by the following sql. Don't forget to replace the example url
https://mydomain.tld
with your service url.Troubleshooting
Trouble with Apache as reverse proxy
If you use TLS you should modify the request header and set X-Forwarded-Proto to https. Here is an example of a virtual host file:
Sync in Firefox Mobile Nightly is broken
Firefox Mobile client expected X-Timestamp in response header.
Here is an example to set X-Timestamp header in apache virtual host file:
The issue is fixed and the workaround should not be necessary anymore.