I get a tiny proxy error when I do an apt install on a template

User Support
21

Thanks, I think I had forgotten about this as it was a long time ago that I had built the environment before. I will install it in the template again and proceed.

22

I’m sorry for repeating myself, but I was able to do it while touching sys-firewall and sys-net settings, but I even changed the sys-net settings, and I was suspicious that it was done by accident, so I reinstalled it, but now the screen is flickering, so I reinstalled it again and made new settings.

I changed default-dvm and the resolv.conf of debian12 template and rebooted because I wanted to be able to connect to the net more than updating, after restart ,The resolv.conf value for untrusted is still the default.

I have also done the above procedure for update, but could not reproduce the problem. How can I set it up properly?

23

Not sure, but if I remember correctly, the untrusted qube is based on Fedora by default. Check its settings to confirm.

1 Like
24

I was using debian12 for untrusted. debian template’s settings resolve.conf are not changed after rebooting os, but untrusted’s settings are not reflected even after creating a new appvm. I’m wondering if the specs have been changed since rc5?

25

You’re right, changes made in the template inside /etc/resolv.conf are not reflected inside the qube (I tested it). One way to fix this would be to add the nameserver entry using /rw/config/rc.local:

# Example with 1.1.1.1
sed -i '1s/^/nameserver 1.1.1.1\n/' /etc/resolv.conf

Or add it to NetworkManager running inside sys-net.

1 Like
26

Thanks, I will try to set it up again tomorrow as I have to go to bed today. By the way, I think I saw such a reply in another topic.

1 Like
27

Good morning, I have a problem. I added an additional DNS (1.1.1.1) to the network icon in the upper right corner and the update worked! The resolv.conf in the Debian12 template is 1.1.1.1/1.0.0.1, untrusted is the QubesOS default address (10. 139.1.1. restarting did not bring it to 1.1.1.1), sys-firewall is also the default address, and sys-net is set to 192.168.1.1/1.1.1.1.

This solved the problem for the update and net browsing. Thank you very much. If I have any more problems with updates, etc., I will try to modify the settings with the commands you gave me.

Translated with DeepL.com (free version)

1 Like