should be available TuesdayAny ETA on a 0.11 update? Have a couple of clients that were updated to 0.11 automatically, and with the new db changes they no longer sync.
Tuesday has come and gone and refreshing the plugin's does not seem to indicate that a new version is available. Despite being appearing to be just a minor version change, it does appear that .11 has some significant changes that might make creating the new plugin more difficult. - is there any thing I or others can do to help this along? Thanks.should be available Tuesday
sorry life got in the way. I should have time tonight, update will be available tomorrowTuesday has come and gone and refreshing the plugin's does not seem to indicate that a new version is available. Despite being appearing to be just a minor version change, it does appear that .11 has some significant changes that might make creating the new plugin more difficult. - is there any thing I or others can do to help this along? Thanks.
no prob, glad it worksThanks - I installed the new version and everything is working very well. The clients that updated to .11 have all been able to sync so everyone is happy again (accept the mobile users - but that is a different issue). Thanks again.
Couldn't retrieve https://192.168.1.55/plugins/syncthing/10/_s/status: No JSON object could be decoded
The JSON error has to do with the plugins middleware that interacts between FreeNAS and the plugins jail, and not to do with the syncthing itself.I'm not sure if this is related to the Freenas update that was pushed out last week, but I'm having the hardest time for the life of me getting Syncthing to work after the updates. I'm not sure if it is Syncthing related (going from .10 to .11) or if it is related to the Freenas GUI.
From scratch, I can install 11.2, but it refuses to enable the plugin, throwing a decoding JSON error.
Code:Couldn't retrieve https://192.168.1.55/plugins/syncthing/10/_s/status: No JSON object could be decoded
Ok, well I figured I'd go back to the last known version to work for me, 10.30. I installed it, it shows up fine, and I'm able to start it up. When I try to update it through the Freenas GUI, it attempts to update, and then hangs. After watching it try for half an hour I stopped it, and then it starts throwing that JSON error again.
I've tried installing 11.1 with the same results, throwing that JSON decoding error listed above to no avail.
I'm moving cross country and would hate to put this away broken :(
Is 192.168.1.55 your freenas IP, or the IP of the jail?11.1, 11.2 standalone, installing through the Freenas GUI or uploading the plugins directly throw this error when it comes time to run the application (post installing into jail). Even whilst upgrading from 10.30 to either of those versions through the Freenas GUI.
10.30 is the last version I am able to get running without issue.
That seems to be what everyone is saying =/I'm not sure how to disabled vimage, I tried as it is selected, but it's not letting me deselect it.
May 14 18:28:08 freenas manage.py: [common.pipesubr:59] Popen()ing: /sbin/ping -q -t 2 -o 192.168.1.245 May 14 18:28:12 freenas warden: Building new Jail... Please wait... May 14 18:28:12 freenas warden: zfs clone Home/jails/.warden-template-pluginjail@clean Home/jails/syncthing_1 May 14 18:28:14 freenas warden: Success! May 14 18:28:14 freenas warden: Jail created at /mnt/Home/jails/syncthing_1 May 14 18:28:14 freenas epair2a: Ethernet address: 02:d2:5c:00:0a:0a May 14 18:28:14 freenas epair2b: Ethernet address: 02:d2:5c:00:0c:0b May 14 18:28:14 freenas kernel: epair2a: link state changed to UP May 14 18:28:14 freenas kernel: epair2a: link state changed to UP May 14 18:28:14 freenas kernel: epair2b: link state changed to UP May 14 18:28:14 freenas kernel: epair2b: link state changed to UP May 14 18:28:14 freenas kernel: epair2a: promiscuous mode enabled May 14 18:28:14 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b May 14 18:28:14 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b May 14 18:28:26 freenas notifier: WARNING: can't open config file: /usr/local/openssl/openssl.cnf May 14 18:28:26 freenas notifier: Performing sanity check on nginx configuration: May 14 18:28:26 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok May 14 18:28:26 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful May 14 18:28:30 freenas manage.py: [freeadmin.navtree:625] An error occurred while unserializing from https://192.168.1.11/plugins/syncthing/7/_s/treemenu: No JSON object could be decoded
this is a miscommunication between the plugin's middleware layer and the freenas interface. you could try playing around with making sure the jail has a reliably determinable IP (as shown with 'jls').Hello there,
I tried installing Syncthing for the first time today and recieved this error
Code:May 14 18:28:08 freenas manage.py: [common.pipesubr:59] Popen()ing: /sbin/ping -q -t 2 -o 192.168.1.245 May 14 18:28:12 freenas warden: Building new Jail... Please wait... May 14 18:28:12 freenas warden: zfs clone Home/jails/.warden-template-pluginjail@clean Home/jails/syncthing_1 May 14 18:28:14 freenas warden: Success! May 14 18:28:14 freenas warden: Jail created at /mnt/Home/jails/syncthing_1 May 14 18:28:14 freenas epair2a: Ethernet address: 02:d2:5c:00:0a:0a May 14 18:28:14 freenas epair2b: Ethernet address: 02:d2:5c:00:0c:0b May 14 18:28:14 freenas kernel: epair2a: link state changed to UP May 14 18:28:14 freenas kernel: epair2a: link state changed to UP May 14 18:28:14 freenas kernel: epair2b: link state changed to UP May 14 18:28:14 freenas kernel: epair2b: link state changed to UP May 14 18:28:14 freenas kernel: epair2a: promiscuous mode enabled May 14 18:28:14 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b May 14 18:28:14 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b May 14 18:28:26 freenas notifier: WARNING: can't open config file: /usr/local/openssl/openssl.cnf May 14 18:28:26 freenas notifier: Performing sanity check on nginx configuration: May 14 18:28:26 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok May 14 18:28:26 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful May 14 18:28:30 freenas manage.py: [freeadmin.navtree:625] An error occurred while unserializing from https://192.168.1.11/plugins/syncthing/7/_s/treemenu: No JSON object could be decoded
Just to throw it out there, I get the same error as Kassim3, Can not get the plugin to startthis is a miscommunication between the plugin's middleware layer and the freenas interface. you could try playing around with making sure the jail has a reliably determinable IP (as shown with 'jls').
A lot of people have been getting this error lately, I don't know the exact cause or how to stop it from happening.