Re: [qubes-users] Re: Unable to uninstall or reinstall Whonix
To remove Whonix templates first remove all the appVMs based on those templates. In dom0 type : qvm-remove sys-whonix qvm-remove anon-whonix Then to remove the Whonix templates. In dom0 type : qvm-remove whonix-gw qvm-remove whonix-ws Essax Sent with [ProtonMail](https://protonmail.com) Secure Email. > Original Message > Subject: [qubes-users] Re: Unable to uninstall or reinstall Whonix > Local Time: September 20, 2017 4:46 PM > UTC Time: September 20, 2017 8:46 PM > From: xueyilu...@gmail.com > To: qubes-users > > I believe it is "sudo yum erase qubes-template-whonix-gw" for uninstalling (I > typed it in a Whonix Konsole) and "sudo qubes-dom0-update > --enablerepo=qubes-templates-community qubes-template-whonix-gw > qubes-template-whonix-ws". I haven"t deleted the old Whonix-gw and Whonix-ws > templates yet, because there seems to be no option other than the terminal > commands, which don"t work. > > -- > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to qubes-users+unsubscr...@googlegroups.com. > To post to this group, send email to qubes-users@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/544c6624-d40b-498c-ad9e-94ab43a10d55%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/eTIkeY5lI2O5KsXCS3wUvdPk1TGMqPKY4tZ_cUWG6wuRoo_7gfPZ54den_vc-XVElXDycn8xDI7-4yX54pK-ppo3M_AwhAKe2FeEJnmsIJ4%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: [3.2rc2] Cannot execute Qubes configuration after installing
I had the same issue when installing Qubes on a usb drive. It was also very slow and I also selected the default options. The Executing Qubes Config prompt appeared then the progress/loading bar stopped/froze after a while. I let it continue for about an hour and a half (with the frozen progress bar) and it finished configuring. I believe the frozen status bar may be a glitch when installing on slower media (usb drives, HDDs) I could be wrong though. Essax Sent with [ProtonMail](https://protonmail.com) Secure Email. > Original Message > Subject: [qubes-users] Re: [3.2rc2] Cannot execute Qubes configuration after > installing > Local Time: September 1, 2017 2:52 AM > UTC Time: September 1, 2017 6:52 AM > From: broncosm...@gmail.com > To: qubes-users > kotot...@gmail.com > > On Sunday, July 31, 2016 at 2:02:11 AM UTC-7, koto...@gmail.com wrote: >> Hello, >> >> After installing Qubes OS on a 32giga USB2 stick - it was slow! - and >> rebooting, I selected the default options and Qubes began to install the >> VMs. When the prompt "Executing Qubes configuration" appears after a while, >> the loading bar stops. The mouse still works but nothing happens. Pressing >> Ctrl-Alt-F1 allowed me to take photos of the screen: >> >> https://postimg.org/image/7je7ki9fr/ >> https://postimg.org/image/7r12opjsn/ >> >> I could not see any shell on the other virtual terminals, so no debugging >> was possible. >> >> I"m using a Lenovo X240 laptop with Core i7 vPro. >> >> Thanks in advance for your help. > > I am facing the exact same problem right now. Has anyone found a solution? > > -- > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to qubes-users+unsubscr...@googlegroups.com. > To post to this group, send email to qubes-users@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/3317c60d-7622-403b-8e2d-68892f40efd6%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0oaoNAR47aSWGee8lb4dbmwoXCfh1e-8MiiXnPn_PRWvBoZH2alsknIWXeuabskk_cbzf_98dU35zP-74RkuNHicNrWRsY8SjbYa6TejQCo%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Not able to connect with 2 firewall-proxy/vpns at same time
I have multiple firewall-proxy/vpns setup as per the qubes docs. I have always been able to use more than one at the same time with out any problems connecting to my vpn providers servers. Starting a few day ago I am no longer able to connect with more than one firewall-proxy/vpn at a time. I start and connect with vpn1 . I start vpn2 and it fails to connect. Then I start vpn2 from the CLI and this is the output I get everytime. ( I just posted the important part at the end ) Mon Jul 31 17:20:43 2017 us=x Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1602,tun-mtu 1500,proto UDPv4,comp-lzo,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-client' Mon Jul 31 17:20:43 2017 us=870023 Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1602,tun-mtu 1500,proto UDPv4,comp-lzo,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-server' Mon Jul 31 17:20:43 2017 us=x TCP/UDP: Preserving recently used remote address: [AF_INET]xxx Mon Jul 31 17:20:43 2017 us=870070 Socket Buffers: R=[212992->212992] S=[212992->212992] Mon Jul 31 17:20:43 2017 us=870086 UDP link local: (not bound) Mon Jul 31 17:20:43 2017 us=870101 UDP link remote: [AF_INET] Mon Jul 31 17:20:43 2017 us=951538 TLS: Initial packet from [AF_INET]Server ip xxx, sid=x Mon Jul 31 17:20:43 2017 us=951664 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Mon Jul 31 17:20:44 2017 us=42751 VERIFY OK: nsCertType=SERVER Mon Jul 31 17:20:44 2017 us=938100 NOTE: --mute triggered... Mon Jul 31 17:20:44 2017 us=938181 1 variation(s) on previous 3 message(s) suppressed by --mute Mon Jul 31 17:20:44 2017 us=938321 [server] Peer Connection Initiated with [AF_INET] Mon Jul 31 17:20:45 2017 us=987500 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1) Mon Jul 31 17:20:46 2017 us=66601 AUTH: Received control message: AUTH_FAILED Mon Jul 31 17:20:46 2017 us=66649 SIGTERM received, sending exit notification to peer Mon Jul 31 17:20:49 2017 us=214365 TCP/UDP: Closing socket Mon Jul 31 17:20:49 2017 us=214441 SIGTERM[soft,exit-with-notification] received, process exiting If I were to shutdown vpn1, I would have no problems connecting with vpn2. My vpn service provider also has a limited vpn service that is free of charge. I configured a firewall-proxy/vpn with those configuration files and I could use that and one of my other proxy/vpns at the same time. Taking into consideration the vpn logs and the fact that I can connect with the free service I'm leaning towards the problem being with my vpn provider. I'm going to start a support ticket with my provider but I wanted to hear if anyone else thought as I do or if there could be another problem I'm not seeing in the logs. Thanks in advance Essax Sent with [ProtonMail](https://protonmail.com) Secure Email. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/_Q5bZgOCN1vyKKhaegjrUG63zw7ymbUGzi1giV6_PWqG8mV3Gb7xYyyaerrDjFlsTRuQhOv3JQHuzwbw3V1ijMwCopsFszOozwGuyKo-HxQ%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes
Was just reading through the qubes docs. You can delete your current sys-usb and make a new sys-usb and make it an appVM(sys-usb). Then you could attach it to a sys-firewall or sys-net . Im not 100% sure this will help but it is worth a try. Sorry I don't have time to write out the instructions. The link to the doc: [Qubes-doc-usb](https://www.qubes-os.org/doc/usb/) Essax Sent with [ProtonMail](https://protonmail.com) Secure Email. > Original Message > Subject: Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes > Local Time: July 14, 2017 11:42 AM > UTC Time: July 14, 2017 3:42 PM > From: p...@mailbox.org > To: Patrik Hagara > qubes-users@googlegroups.com > > Actually I do have the qubes-proxy-usb installed on my sys-usb (that's how > I'm able to use my mouse) however I'm not sure if the qubes-proxy-usb can be > used to pass the HW wallet. > > How I'm I suppose to pass my Ledger nano s or trezor via the proxy? > >> On 14 July 2017 at 15:40 Patrik Hagara wrote: >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> On 07/14/2017 02:19 PM, Mr. DONG wrote: >> >>> Unfortunately that doesn't work either. >>> >>> The "qvm-usb -l" doesn't show my legder nano s. In fact I can only >>> see it attached on the sys-usb, not on dom0. >>> >>> The qvm-usb list output shows no difference either I attach or not >>> the HW wallet. The only way I can attach to another appvm is if I >>> attach the entire PCI controller, via the usb-passthrough does not >>> work. >>> >>> Any alternatives? >>> >>> On 14 July 2017 at 10:48 Patrik Hagara >>> wrote: >>> >>> On 07/14/2017 02:54 AM, 'Essax' via qubes-users wrote: >>> >>> Have you tried these steps: >>> >>> 1) Attach hardware wallet to sys-usb 2) Go to the dom0 Gui and and >>> right click on the appVM you want to attach it to. 3) In the box >>> that opens scroll down to Attach/detach block devices and your >>> hardware wallet should show up to the right. 4) Right click on >>> your hardware wallet to attach it to your appVM. >>> >>> /Essa*x*/ >>> >>> Original Message Subject: [qubes-users] Re: >>> Working with a BTC hardware wallet on Qubes Local Time: July 13, >>> 2017 4:23 PM UTC Time: July 13, 2017 8:23 PM From: p...@mailbox.org >>> To: qubes-users@googlegroups.com >>> >>> I do have a sys-usb vm, however I cannot attach a netVM to it since >>> the sys-usb is also a netvm. >>> >>> I possibly will need to create a new sys-usb vm or is there any >>> other alternative? >>> >>> Attaching it as a block device won't work, since bitcoin hardware >>> wallet is not a mass storage device. Luckily, it's not emulating a >>> HID device either, which would get picked up by the dom0 USB >>> keyboard/mouse input proxy. Thus, there's no graphical means of >>> attaching USB bitcoin hardware wallet in Qubes to another VM... >>> >>> You can, however, attach it via the qvm-usb command line tool: >>> >>> 1) connect the bitcoin hardware wallet 2) in dom0 terminal, run >>> |qvm-usb -l| to list USB devices attached 3) locate the line with >>> bitcoin wallet and note the first column (eg. "sys-usb:2-1.6") 4) >>> run |qvm-usb -a bitcoin sys-usb:2-1.6| from a dom0 terminal to >>> attach the wallet to bitcoin AppVM >>> >>> Cheers, Patrik >> >> Most likely you don't have qubes-usb-proxy installed in the sys-usb's >> template (make sure to also install this package in the target bitcoin >> banking AppVM's template). See [1] for more info. >> >> [1] >> https://www.qubes-os.org/doc/usb/#attaching-a-single-usb-device-to-a-qub >> e-usb-passthrough >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v2 >> >> iQIcBAEBCAAGBQJZaMnNAAoJEFwecd8DH5rlmTkP/jiwIpUlTMr6OMEUw3afH46X >> h1Z+hcADH40Z1M2FVTH3oqginIjoGs0kJyd490vcpaic3Js1EO6+I0eXtvF4n2qt >> J5LWSHQ/AQg3xjfBAFSsl2kEXnNa0CGF9hl0ZLCJOaHKcbpcJfS69fH79kT7KtJG >> KJ4bOgENGCHaxgHb6vqtvdaYgnj8ltHqRvIZjwThai1PBsQcmw1HSf+uBMzQNRFw >> 5E39a1Rb6vkvpdG1EDjEXrtzU8TdLH/96eCGODD0+t6vbAAp0t9EEheeqFjDdtz1 >> 65FNUWYx+WxkCvjcDaMK6GR/NY447C9cCM3xm55rQlFH7/vzH9CkMTM52+ZW0bqB >> 27B8d+BatKYaIKQbrxHBWxdN7LDsJkcr+YHVHGt2F7nqt14LsLaRf+52gj6A+MHq >> utn+5cVUpVT//GKlox+vEwfxZC/TjRqr4Im6tqAWQX+OZrpH9q4yP+asb6Ca2YdY >> 3K9qoJZmtUVCaMiVQLqTRcjzHdVpMllS7scSs4wcJDHvi+K
Re: [qubes-users] Re: Working with a BTC hardware wallet on Qubes
Have you tried these steps: 1) Attach hardware wallet to sys-usb 2) Go to the dom0 Gui and and right click on the appVM you want to attach it to. 3) In the box that opens scroll down to Attach/detach block devices and your hardware wallet should show up to the right. 4) Right click on your hardware wallet to attach it to your appVM. Essax Sent with [ProtonMail](https://protonmail.com) Secure Email. > Original Message > Subject: [qubes-users] Re: Working with a BTC hardware wallet on Qubes > Local Time: July 13, 2017 4:23 PM > UTC Time: July 13, 2017 8:23 PM > From: p...@mailbox.org > To: qubes-users@googlegroups.com > > I do have a sys-usb vm, however I cannot attach a netVM to it since the > sys-usb is also a netvm. > > I possibly will need to create a new sys-usb vm or is there any other > alternative? > > -- > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to qubes-users+unsubscr...@googlegroups.com. > To post to this group, send email to qubes-users@googlegroups.com. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/qubes-users/1455174408.2312.1499977395517%40office.mailbox.org](https://groups.google.com/d/msgid/qubes-users/1455174408.2312.1499977395517%40office.mailbox.org?utm_medium=email&utm_source=footer). > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cQfcFtvu65bDkUPeJv9eORHYWELlb4LLb0pUnjwb-oSLAvg-O-i6TUTJDUoRhboFNOdyrLvrCeE84XVql9jlX1QDRmejPSmhSrlcHf1vxTE%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Sys-net with a 2 port NIC, how to allow/block interfaces?
Hi Unman Thanks ! Thats is exactly what I wanted to accomplish. Although I could use a little clarification on a couple things. > You can examine the IP addresses allocated to the qubes using > "qvm-ls -n". I ran this command and there are three ip addresses listed for most of the qubes. Going from left to right---> I know the first one is the qube ip address. The second ip address is only given to proxy-vms (What is this ip for?) And the third ip address is the up stream gateway ip?? > Each firewall provides masquerade NAT to downstream qubes. This means > that you can simply do the following: > firewall-vm0 : eth0 - 10.137.10.10 > firewall-vm1 : eth0 - 10.137.10.100 I'm sure you can guess my next question. Those two ip addresses would be the actual ip of the qubes. (sorry I have to be sure : ) Essax Sent with [ProtonMail](https://protonmail.com) Secure Email. > Original Message > Subject: Re: [qubes-users] Sys-net with a 2 port NIC, how to allow/block > interfaces? > Local Time: July 5, 2017 9:24 PM > UTC Time: July 6, 2017 1:24 AM > From: un...@thirdeyesecurity.org > To: Essax > Google groups Qubes-users > On Wed, Jul 05, 2017 at 08:08:02PM -0400, "Essax" via qubes-users wrote: >> I have laptop with a 2 port NIC. I would like to have 1 subset of appVMs >> that are connected to sys-net to use the eth0 interface and the other subset >> to use the eth1 interface. It is not possible to assign 1 port into seperate >> sys-nets. I have tried that and only eth0 will function. Its also my >> understanding that eth0 is the interface used between qubes. ( is this >> wrong? ) If so would this prevent me from using iptables in firewall-vm1 to >> block traffic to the eth0 interface. That would block traffic to sys-net as >> well (I think). The only solution I have come up with would be to go to dom0 >> GUI --> appvm1---> edit VM firewall rules ---> allow networks except >> 172.16.1.1/24 . This would not block traffic to the eth0 interface but it >> would prevent if from going any further than the 172.16.1.1 pfsense >> interface. Then I could do the same for firewall-vm0 and block it from the >> 192.168.1.1 pfsense interface. Is there a better way to do this with >> iptables. >> pfsense-192.168.1.1/24eth1firewall-vm1appvm1 >> sys-net >> pfsense-172.16.1.1/24--eth0firewall-vm0VPN/proxyvmappvm0 >> >> Thanks in advance >> Essax > I"m not sure what you mean by "eth0 is the interface used between > qubes". Each qube is attached to its upstream proxy, its eth0 > connecting to a vifX interface on the proxy. > You can examine the IP addresses allocated to the qubes using > "qvm-ls -n". > On your proposal the downstream qubes would only be able to connect to > the networks attached to eth0 and eth1. This may be what you want. If > you want to connect to the net (or another network) via those connected > networks, there is an alternative. > Each firewall provides masquerade NAT to downstream qubes. This means > that you can simply do the following: > firewall-vm0 : eth0 - 10.137.10.10 > firewall-vm1 : eth0 - 10.137.10.100 > On sys-net- > iptables -I FORWARD -o eth0 -j DROP > iptables -I FORWARD -o eth1 -j DROP > iptables -I FORWARD -s 10.137.10.100 -o eth1 -j ACCEPT > iptables -I FORWARD -s 10.137.10.10 -o eth0 -j ACCEPT > Those rules explicitly block and allow traffic. You could combine into > one rule but this makes it clearer what is happening and will allow you > to track counters as traffic flows. > I think it"s neater than your proposal. > You"ll also want to keep the rules allowing established traffic back > though sys-net. > You can put these rules in to rc.local, and qubes-firewall-user-script, > as set out here: > www.qubes-os.org/doc/firewall > unman > -- > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to qubes-users+unsubscr...@googlegroups.com. > To post to this group, send email to qubes-users@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/20170706012459.nixgcf6n3mwqwobt%40thirdeyesecurity.org. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/WszUs9sGM9qi48M2RaOxkmtA5od7C02DWQdga-3Im3D960qCOv7CkSuSqp10tSctYnMrnZGuWWmYgbWH5J4r1p9SIrZKzw3UFyErA94U5wc%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Sys-net with a 2 port NIC, how to allow/block interfaces?
I have laptop with a 2 port NIC. I would like to have 1 subset of appVMs that are connected to sys-net to use the eth0 interface and the other subset to use the eth1 interface. It is not possible to assign 1 port into seperate sys-nets. I have tried that and only eth0 will function. Its also my understanding that eth0 is the interface used between qubes. ( is this wrong? ) If so would this prevent me from using iptables in firewall-vm1 to block traffic to the eth0 interface. That would block traffic to sys-net as well (I think). The only solution I have come up with would be to go to dom0 GUI --> appvm1---> edit VM firewall rules ---> allow networks except 172.16.1.1/24 . This would not block traffic to the eth0 interface but it would prevent if from going any further than the 172.16.1.1 pfsense interface. Then I could do the same for firewall-vm0 and block it from the 192.168.1.1 pfsense interface. Is there a better way to do this with iptables. pfsense-192.168.1.1/24eth1firewall-vm1appvm1 sys-net pfsense-172.16.1.1/24--eth0firewall-vm0VPN/proxyvmappvm0 Thanks in advance Essax Sent with [ProtonMail](https://protonmail.com) Secure Email. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/yQ0Xt5URRed9eRoNFHjZy4TXx4hBIxcnQPtCMQhJu9epRY0cI_3O6_oS-WPZBl5CzDwlbYjIxwlREimUVjbGEKbQJdXKA2y9fartzH5VHAg%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Whonix-ws template will not connect to sys-whonix after upgrade
I upgraded my whonix-ws template with apt-get upgrade. Now when I try to upgrade the template I get. Whonix-Gateway NetVM required for updates! Please ensure that this TemplateVM has a Whonix-Gateway as its NetVM. No updates are possible without an active (running) Whonix-Gateway VM. I checked the GUI and ran the command qvm-prefs -l whonix-ws netvm and they both have sys-whonix as the netvm for whonix-ws temp. I updated all of my other templates over Tor while using sys-whonix as their netvm with out any problems I also cloned a whonix-ws temp for testing to make sure it was the upgrade that caused the problem and sure enough as soon as I did the upgrade I could not connect it to sys-whonix. (the gui and qvm-prefs said other wise though) When I ran sudo apt-get update from whoinix-ws konsole i get Err http://sgvtcaew4bxjd7ln.onion jessie/updates Release.gpg Cannot initiate the connection to 10.137.255.254:8082 (10.137.255.254). - connect (101: Network is unreachable I'm kinda lost here as what to do and I'm not sure what logs would be needed to figure out the problem. I also reported the problem on whonix forum because I wasn't sure if this was a Qubes or Whonix issue. Thanks in advance Essax Sent with [ProtonMail](https://protonmail.com) Secure Email. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/J7QctZ_evHhqmPQqzGgnQ4YRQRMhxNauueX2Vkno78gUzfwKhXts8NIO-_dgf0LaOAv3KHPhk4DIOdEwyB0OPq7H7hFa9q-V2C2QHld2o0E%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Vault-appvm empty after Debian-8 template dist-upgrade
I upgrade my Debian-8 template with sudo apt-get dist-upgrade. The only problem I had after the upgrade was my vault-appvm was emply when I launched it. I searched through every directory trying to find my data base with no luck. Fortunately I was able to follow the instructions in the [Qubes Documentation](https://www.qubes-os.org/doc/software-update-vm/) and roll back the changes to my TemplateVM. Once I did that my vault data base was back to normal. If this happens to you and you want to revert the changes to your Debian-8 TemplateVM you would type this command in your Dom0 terminal. qvm-revert-template-changes debian-8 Please note It requires that all AppVMs based on this template be halted during this operation. For the technical details about how this command works and the steps it performs, see [here](http://For the technical details about how this command works and the steps it performs, see) Obviosly another solution would be to restore from backups or download a new TemplateVM. Just be aware if your vault-appvm is based off debian to cautious if your dist-upgrade Essax Sent with [ProtonMail](https://protonmail.com) Secure Email. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/w0Xl31OJ2d7z5QisSEUXGFE7Sz_cp2thbQdQrnHRyN7JbgsX3Cfp2AgoV5z8db7c5psQfcKEMDlHqlshemRLwNdDJHY5tM2b6q99WCxjx08%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
