Upgrade StorageSync errors: 170997429 failed with status code 408
Hi There,
I seem to be having some sort of sync issues that I can't figure out. My changes made from my primary PC seem to sync upstream to my account. Changes made on-line sync to one of my machines, but not the other.
Error details:
[JavaScript Error: "HTTP GET https://api.zotero.org/users/5613105/items/top?format=versions&since=42&includeTrashed=1 failed with status code 408"]
...
[JavaScript Error: "HTTP GET https://api.zotero.org/users/5613105/items/top?format=versions&since=42&includeTrashed=1 failed with status code 408"]
[JavaScript Error: "IndexedDB Maintenance finished with error: NS_ERROR_NOT_AVAILABLE: ActorsParent.cpp:18877"]
[JavaScript Error: "HTTP GET https://api.zotero.org/users/5613105/items/top?format=versions&since=42&includeTrashed=1 failed with status code 408"]
...
[JavaScript Error: "The connection was refused when attempting to contact wss://stream.zotero.org/."]
[JavaScript Error: "WebSocket connection closed: 1006 "]
[JavaScript Error: "Error connecting to server. Check your Internet connection."]
[JavaScript Error: "The connection to wss://stream.zotero.org/ has terminated unexpectedly. Some data may have been transferred."]
...
[JavaScript Error: "HTTP GET https://api.zotero.org/users/5613105/items/top?format=versions&since=42&includeTrashed=1 failed with status code 408"]
...
version => 5.0.64, platform => Win32, oscpu => Windows NT 10.0; WOW64, locale => en-US, appName => Zotero, appVersion => 5.0.64, extensions => Zotero LibreOffice Integration (5.0.14.SA.5.0.64, extension), Zotero Word for Windows Integration (5.0.12.SA.5.0.64, extension), ZotFile (5.0.9, extension)
Traceroute info:
1 1 ms 1 ms 1 ms SYNOLOGYROUTER [10.0.4.1]
2 27 ms 26 ms 26 ms 192.168.1.1
3 * * * Request timed out.
4 * * * Request timed out.
5 48 ms 32 ms 49 ms bundle-ether58.ken-edge903.sydney.telstra.net [203.54.181.213]
6 74 ms 49 ms 55 ms bundle-ether17.ken-core10.sydney.telstra.net [203.50.11.172]
7 37 ms 52 ms 35 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
8 33 ms 27 ms 34 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
9 255 ms 236 ms 188 ms i-52.tlot-core02.bx.telstraglobal.net [202.84.137.101]
10 221 ms 230 ms 244 ms i-93.eqla01.telstraglobal.net [202.84.251.194]
11 265 ms 231 ms 173 ms be4637.ccr41.lax05.atlas.cogentco.com [154.54.10.133]
12 187 ms 185 ms 180 ms be3359.ccr42.lax01.atlas.cogentco.com [154.54.3.69]
13 199 ms 231 ms 264 ms be2932.ccr32.phx01.atlas.cogentco.com [154.54.45.161]
14 238 ms 230 ms 244 ms be2930.ccr21.elp01.atlas.cogentco.com [154.54.42.78]
15 217 ms 239 ms 233 ms be2927.ccr41.iah01.atlas.cogentco.com [154.54.29.221]
16 275 ms 224 ms 236 ms be2441.ccr31.dfw01.atlas.cogentco.com [154.54.41.66]
17 262 ms 211 ms 228 ms be2763.ccr41.dfw03.atlas.cogentco.com [154.54.28.74]
18 302 ms 237 ms 228 ms 38.142.85.58
19 267 ms 249 ms 243 ms 54.239.105.107
Trace route info indicates it seems to be able to reach the host. Any clues on why it keeps timing out?
I seem to be having some sort of sync issues that I can't figure out. My changes made from my primary PC seem to sync upstream to my account. Changes made on-line sync to one of my machines, but not the other.
Error details:
[JavaScript Error: "HTTP GET https://api.zotero.org/users/5613105/items/top?format=versions&since=42&includeTrashed=1 failed with status code 408"]
...
[JavaScript Error: "HTTP GET https://api.zotero.org/users/5613105/items/top?format=versions&since=42&includeTrashed=1 failed with status code 408"]
[JavaScript Error: "IndexedDB Maintenance finished with error: NS_ERROR_NOT_AVAILABLE: ActorsParent.cpp:18877"]
[JavaScript Error: "HTTP GET https://api.zotero.org/users/5613105/items/top?format=versions&since=42&includeTrashed=1 failed with status code 408"]
...
[JavaScript Error: "The connection was refused when attempting to contact wss://stream.zotero.org/."]
[JavaScript Error: "WebSocket connection closed: 1006 "]
[JavaScript Error: "Error connecting to server. Check your Internet connection."]
[JavaScript Error: "The connection to wss://stream.zotero.org/ has terminated unexpectedly. Some data may have been transferred."]
...
[JavaScript Error: "HTTP GET https://api.zotero.org/users/5613105/items/top?format=versions&since=42&includeTrashed=1 failed with status code 408"]
...
version => 5.0.64, platform => Win32, oscpu => Windows NT 10.0; WOW64, locale => en-US, appName => Zotero, appVersion => 5.0.64, extensions => Zotero LibreOffice Integration (5.0.14.SA.5.0.64, extension), Zotero Word for Windows Integration (5.0.12.SA.5.0.64, extension), ZotFile (5.0.9, extension)
Traceroute info:
1 1 ms 1 ms 1 ms SYNOLOGYROUTER [10.0.4.1]
2 27 ms 26 ms 26 ms 192.168.1.1
3 * * * Request timed out.
4 * * * Request timed out.
5 48 ms 32 ms 49 ms bundle-ether58.ken-edge903.sydney.telstra.net [203.54.181.213]
6 74 ms 49 ms 55 ms bundle-ether17.ken-core10.sydney.telstra.net [203.50.11.172]
7 37 ms 52 ms 35 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
8 33 ms 27 ms 34 ms bundle-ether1.sydp-core04.sydney.reach.com [203.50.13.90]
9 255 ms 236 ms 188 ms i-52.tlot-core02.bx.telstraglobal.net [202.84.137.101]
10 221 ms 230 ms 244 ms i-93.eqla01.telstraglobal.net [202.84.251.194]
11 265 ms 231 ms 173 ms be4637.ccr41.lax05.atlas.cogentco.com [154.54.10.133]
12 187 ms 185 ms 180 ms be3359.ccr42.lax01.atlas.cogentco.com [154.54.3.69]
13 199 ms 231 ms 264 ms be2932.ccr32.phx01.atlas.cogentco.com [154.54.45.161]
14 238 ms 230 ms 244 ms be2930.ccr21.elp01.atlas.cogentco.com [154.54.42.78]
15 217 ms 239 ms 233 ms be2927.ccr41.iah01.atlas.cogentco.com [154.54.29.221]
16 275 ms 224 ms 236 ms be2441.ccr31.dfw01.atlas.cogentco.com [154.54.41.66]
17 262 ms 211 ms 228 ms be2763.ccr41.dfw03.atlas.cogentco.com [154.54.28.74]
18 302 ms 237 ms 228 ms 38.142.85.58
19 267 ms 249 ms 243 ms 54.239.105.107
Trace route info indicates it seems to be able to reach the host. Any clues on why it keeps timing out?
-
newtopiaBump
-
dstillmanAre you able to try from a different network?
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.