My NAS is a Synology device, so not exactly that flexible. Assuming I can get some sort of Perl version installed then it would be an option. Synology Linux version is severely deprecated.
It does appear that perl 5.34 is available and can be added from the Synology Disc Station Manager: Perl - Add-on Packages | Synology Inc.
They also have a python 3.9 package (which I would expect to be much larger than perl so space on your system partition may be a concern): Synology Inc. Wyng can use python versions going back to 3.8.
1 Like
BTW… The Wyng v0.8.0 release is now out! 
3 Likes
I see the first 0.8 beta was tagged 2 years ago, you must be super happy to have a 0.8 release today. Let’s celebrate 
!
Yes. I should have made an incremental v0.4 release at that point instead of bumping the version way up. Lesson learned! 
Great news! It’s really a tool that I really appreciate:D Tell me @tasket, there’s no need to use wyng-util-qubes anymore? Only wyng is enough? 
Testing of the new 0.8 release went well. Thanks for your efforts! As @Tezeria has mentioned, is the wyng-util-qubes wrapper still supported?
I cannot create an ssh backup. Are there settings in sshd or firewall (I blocked everything but tcp and the ip) that need to be set?
Normal ssh connections work, creating it without the wrapper also does not work
sudo wyng-util-qubes create --dest=qubes-ssh://wyng:user@1.1.1.1:200/mnt
Wyng-util-qubes v0.9 beta rel 20251105
Wyng 0.8.0 release 20251201
XXXXXXXXX)'.
mkdir -p -m 777 /tmp/wyngrpc/ && tdir=$(mktemp -d /tmp/wyngrpc/tmpXXXXXXXXXXXX) && echo && echo $tdir && cat >$tdir/dest_helper.py
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
[0, 127]
StorageError: Destination not ready to receive commands.
Is your remote ssh user using bash? Same for the Qubes os side in the appvm. I had issues using fish.
1 Like
That was the issue. I also considered this because of the fish style error message but I did not change the shell of both ends…
This could be fixed with extra flags in wyng to configure the path of the shell to use on both ends. But it’s more work for @tasket unfortunately, it’s easier to change the shell at the moment 
Some questions:
- Can I use one wyng archive for multiple different qubes installs? Are there issues I will run into
- How do you guys read a password from a file for the qubes wrapper --passcmd does not work. Is it okay to pipe like this
cat pw | wyngor is this insecure / the password will be left somewhere
If you want to say if you could use wyng archive for multiple Qubes-Os installation, Yes you can, i create backup from 4.2.4 for an installation on 4.3.rc3 and all be ok.
@Tezeria @qub411 The wyng-util-qubes component is still needed to get the full VM settings backup & restore in a convenient form. For now, this represents the Qubes-Wyng integration and will be supported into the foreseeable future.
Also, I realize the wyng-util-qubes name seems a little clumsy to use… renaming it to something else is fine as long as it sits in the same directory as wyng.
@Mirai @solene Noted about shell types and specifying the shell path. Thanks!
OT: Update for perl support on dest/remote which I mentioned here earlier – there is a test branch now that uses perl instead of python, much easier to setup on router/NAS.
BTW, Wyng now has a fediverse account where I’ve posted the good news about Qubes project funding Wyng’s further development! (I just wanted to mention it briefly here while responding to other posts… it being OT for this thread about basic Wyng usage).
5 Likes
@mirai You can use a single archive to backup multiple systems. There are a couple of issues: 1) Backups may slow down if the volume names are the same (because the VM names are the same). This is because Wyng will see the volume snapshot on system A will no longer match the archived volume after its been updated by system B, and the snapshots are key to faster backups. The slowdown isn’t permanent, it only happens when switching between systems. 2) The util backs up the system’s qubes.xml, so two VMs named “work” on A and B need to reference the same templates and netvms, or else the util may report an error for those settings during a restore (its not serious if you remember to correct the settings right away after restore finishes).
Passphrase input: The pipe input method actually does work, and I can’t say it leaves behind anything more than other methods – as long as the source isn’t from text on the command line. The passcmd option should work if you use the Wyng pass-through method like wyng-util-qubes -w passcmd='cat /tmp/mypass'.
thanks for the answer And thank you for your work on wyng 
1 Like
@mirai @solene I forgot to mention I added a possible fix for the shell type issue you reported in the Wyng fix08 branch. It now puts a shebang for ‘sh’ ahead of remote commands.
2 Likes
You may want to consider:
and
Couple things:
- the newest bin on fix08 is not signed
- how do pass multiple arguments to wyng with the qubes util -w
- I cannot restore disposables on 4.3
Error
Wyng-util-qubes v0.9 beta rel 20251105
Traceback (most recent call last):
File "/usr/local/bin/wyng-util-qubes", line 910, in <module>
elif action == "restore": wq_context.restore()
~~~~~~~~~~~~~~~~~~^^
File "/usr/local/bin/wyng-util-qubes", line 809, in restore
res = _do_restore(self, selected=vms, session=session) ; self.close()
File "/usr/local/bin/wyng-util-qubes", line 356, in _do_restore
selected = available - ({} if options.include_disposable=="on" else dispvms) \
~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TypeError: unsupported operand type(s) for -: 'set' and 'dict'
@tasket unfortunately wyng still fails if the shell on the sshd qube is fish. Had to change the shell for ‘user’ just root was not enough
Wyng-util-qubes v0.9 beta rel 20251105
Wyng 0.8.1 (fix08) release 20260419
XXXXXXXXX)'.
mkdir -p -m 777 /tmp/wyngrpc/ && tdir=$(mktemp -d /tmp/wyngrpc/tmpXXXXXXXXXXXX) && echo && echo $tdir && cat >$tdir/dest_helper.py
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
[0, 127]
StorageError: (5, 'Destination not ready to receive commands.')
From stackoverflow there might be a solution?