Hallo zusammen,
ich habe in Portainer einen Stack mit syncstorage-rs:0.13.7 erstellt. Das Serverlog sieht gut aus :
Nov 04 21:39:18.344 INFO Starting 2 workers
Nov 04 21:39:18.344 INFO Starting "actix-web-service-0.0.0.0:8000" service on 0.0.0.0:8000
Nov 04 21:39:18.344 INFO Server running on
http://0.0.0.0:8000 (mysql) No quota
Firefox-Konto habe ich auch eingerichtet.
http://192.168.178.150:5000/__heartbeat__ sieht auch gut aus
{"quota":{"enabled":false,"size":0},"version":"0.13.7","database":"Ok","status":"Ok"}
Leider funktioniert der sync nicht:
1730758657050 Sync.LogManager DEBUG Flushing file log
1730758657054 FirefoxAccounts TRACE not checking freshness of profile as it remains recent
1730758657054 FirefoxAccounts TRACE not checking freshness of profile as it remains recent
1730758657056 Sync.LogManager DEBUG Log cleanup threshold time: 1729894657056
1730758657063 Sync.LogManager DEBUG Done deleting files.
1730758718838 FirefoxAccounts TRACE not checking freshness of profile as it remains recent
1730758920573 FirefoxAccounts INFO Polling device commands.
1730758920573 Sync.Service DEBUG User-Agent: Firefox/132.0 (Windows NT 10.0) FxSync/1.134.0.20241021175835.desktop
1730758920573 Sync.Service INFO Starting sync at 2024-11-04 23:22:00 in browser session P4OfkHREzhatyo
1730758920573 Sync.Service DEBUG In sync: should login.
1730758920574 Sync.Service INFO User logged in successfully - verifying login.
1730758920574 FirefoxAccounts DEBUG FxAccountsProfileClient: Requested profile
1730758920574 FirefoxAccounts DEBUG getOAuthToken enter
1730758920574 FirefoxAccounts TRACE getCachedToken returning cached token
1730758920574 FirefoxAccounts DEBUG getOAuthToken returning a cached token
1730758920574 Sync.SyncAuthManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys
1730758920575 Services.Common.RESTRequest DEBUG GET request to
https://profile.accounts.firefox.com/v1/profile
1730758920575 Sync.Status DEBUG Status.login: error.login.reason.network => success.status_ok
1730758920575 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed
1730758920575 Sync.Service DEBUG Fetching unlocked auth state returned success.status_ok
1730758920577 Services.Common.RESTRequest DEBUG GET request to
https://api.accounts.firefox.com/v1/account/device/commands?index=0
1730758920763 Services.Common.RESTRequest DEBUG GET
https://profile.accounts.firefox.com/v1/profile 304
1730758920773 Services.Common.RESTRequest DEBUG GET
https://api.accounts.firefox.com/v1/account/device/commands?index=0 200
1730758920773 Hawk DEBUG (Response) /account/device/commands?index=0: code: 200 - Status text:
1730758920773 Hawk DEBUG Clock offset vs
https://api.accounts.firefox.com/v1: -2773
1730758922622 Sync.Resource WARN GET request to
http://192.168.178.150/1.5/4/info/collections failed: [Exception... "The connection was refused" nsresult: "0x804b000d (NS_ERROR_CONNECTION_REFUSED)" location: "<unknown>" data: no] No traceback available
1730758922623 Sync.Service DEBUG verifyLogin failed: [Exception... "The connection was refused" nsresult: "0x804b000d (NS_ERROR_CONNECTION_REFUSED)" location: "<unknown>" data: no] No traceback available
1730758922623 Sync.Status DEBUG Status.login: success.status_ok => error.login.reason.network
1730758922623 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed
1730758922623 Sync.Status DEBUG Status.login: error.login.reason.network => error.login.reason.network
1730758922623 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed
1730758922623 Sync.ErrorHandler ERROR Sync encountered a login error
1730758922623 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score.
1730758922625 Sync.SyncScheduler DEBUG Next sync in 3600000 ms. (why=schedule)
1730758922626 Sync.Service DEBUG Exception calling WrappedLock: Error: Login failed: error.login.reason.network(resource://services-sync/service.sys.mjs:1041:15) JS Stack trace:
onNotify@service.sys.mjs:1041:15
1730758922626 Sync.Service DEBUG Not syncing: login returned false.
1730758922626 FirefoxAccounts TRACE not checking freshness of profile as it remains recent
Suche händeringend nach einer Fehlerlösung