Templates do not need to connect to anything. Open a dom0 terminal (xterm/uxterm) and type 'journalctl -f' then open a fedora-26 terminal and type 'sudo yum update'
then tell us what it says on the dom0 journalctl output. Type 'sudo vi /etc/qubes-rpc/policy/qubes.UpdatesProxy' Its going to look like this: $type:TemplateVM $default allow,target=sys-whonix $tag:whonix-updatevm $default allow,target=sys-whonix $tag:whonix-updatevm $anyvm deny ## Note that policy parsing stops at the first match, ## so adding anything below "$anyvm $anyvm action" line will have no effect ## Please use a single # to start your custom comments # Default rule for all TemplateVMs - direct the connection to sys-net $type:TemplateVM $default allow,target=sys-net Make sure the last line points to your sys-net. Go into your sys-net qube settings. (Right click>settings>Services) Go to the last tab, Services. Type "qubes-updates-proxy" click add. If the qube is running, open a terminal and type "systemctl restart qubes-updates-proxy" -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0aa3941b-3d2c-485d-be68-d8534a0eae34%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
