Whonix-updatevm bug

tempmail · October 5, 2024, 9:45am

All of a sudden this exactly started to happen to me with both gw and ws templates

No response there. Tried everything suggested in a template’s response, to no avail.

But, what is interesting is that whonix-ws-dvm-template based exactly on these templates CAN be updated with netVM set to ’ ’ plus updates-proxy-setup service enabled (via cacher->sys-whonix->sys-firewall->sys-net).

So what’s the differences between ws-template and ws-dvm-template?

The latter updates via cacher, but through sys-whonix. But dvm-template doesn’t have whonix-updatevm tag.

When I set it, update isn’t possible anymore, and I’m getting errors:

Summary

E: Failed to fetch tor+https://deb.debian.org/debian/dists/bookworm-updates/InRelease  Reading from proxy failed - read (115: Operation now in progress) [IP: 127.0.0.1 8082]
E: Failed to fetch tor+https://deb.debian.org/debian-security/dists/bookworm-security/InRelease  Reading from proxy failed - read (115: Operation now in progress) [IP: 127.0.0.1 8082]
E: Failed to fetch tor+https://deb.debian.org/debian/dists/bookworm-backports/InRelease  Reading from proxy failed - read (115: Operation now in progress) [IP: 127.0.0.1 8082]
E: Failed to fetch tor+https://fasttrack.debian.net/debian/dists/bookworm-fasttrack/InRelease  Reading from proxy failed - read (115: Operation now in progress) [IP: 127.0.0.1 8082]
E: Failed to fetch tor+https://deb.kicksecure.com/dists/bookworm-developers/InRelease  Reading from proxy failed - read (115: Operation now in progress) [IP: 127.0.0.1 8082]
E: Failed to fetch tor+https://deb.whonix.org/dists/bookworm-developers/InRelease  Reading from proxy failed - read (115: Operation now in progress) [IP: 127.0.0.1 8082]
E: Failed to fetch https://contrib.qubes-os.org/deb/r4.2/vm/dists/bookworm/InRelease  Reading from proxy failed - read (115: Operation now in progress) [IP: 127.0.0.1 8082]
E: Failed to fetch https://deb.qubes-os.org/r4.2/vm/dists/bookworm/InRelease  Reading from proxy failed - read (115: Operation now in progress) [IP: 127.0.0.1 8082]
E: Some index files failed to download. They have been ignored, or old ones used instead.
zsh: exit 100   upgrade-nonroot

Haven’t messed with policies. All of them work for other qubes.

tempmail · October 5, 2024, 9:49am

I also tried with the stock whonix-gw-17 template, downloaded just to test this, and it’s the same result.

apparatus · October 5, 2024, 10:32am

Try to create a new sys-whonix-test qube (not clone of sys-whonix but a freshly created one) and set it as Whonix update proxy.

tempmail · October 5, 2024, 11:06am

I will, although I don’t see how cacher would “see” existing sys-whonix, while templates don’t…

apparatus · October 5, 2024, 11:10am

You can also try to set sys-whonix as update proxy instead of a cacher qube and check this:

tempmail · October 5, 2024, 11:52am

Nope. Will try with new sys-whonix later.

tempmail · October 5, 2024, 11:57am

Job for qubes-whonix-torified-updates-proxy-check.service failed because the control process exited with error code.

Can someone confirm after apt(-get) update, updating works?

In a dvm-template, this service is active and works flawlessly?!

apparatus · October 5, 2024, 12:07pm

It works for me in fully updated whonix-workstation-17.
What’s the output of this command in whonix-workstation-17?

sudo systemctl status qubes-whonix-torified-updates-proxy-check | cat

tempmail · October 5, 2024, 12:11pm

× qubes-whonix-torified-updates-proxy-check.service - Qubes Whonix Torified Updates Proxy Check
Loaded: loaded (/lib/systemd/system/qubes-whonix-torified-updates-proxy-check.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sat 2024-10-05 12:08:40 UTC; 1min 33s ago
Docs: GitHub - Whonix/qubes-whonix
Process: 706 ExecStart=/usr/lib/qubes-whonix/init/torified-updates-proxy-check (code=exited, status=1/FAILURE)
Main PID: 706 (code=exited, status=1/FAILURE)
CPU: 24ms
Oct 05 12:08:40 host torified-updates-proxy-check[706]: href=“Donate”>Donate! | <a
Oct 05 12:08:40 host torified-updates-proxy-check[706]: href=“Apt-Cacher NG - Software Package Download Proxy”>Apt-Cacher NG homepage
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host systemd[1]: qubes-whonix-torified-updates-proxy-check.service: Failed with result ‘exit-code’.
Oct 05 12:08:40 host systemd[1]: Failed to start qubes-whonix-torified-updates-proxy-check.service - Qubes Whonix Torified Updates Proxy Check.

Should apt-cacher be mentioned here at all (not to say paypal)?

apparatus · October 5, 2024, 12:15pm

Run this command to show the full log:

sudo journalctl -b -u qubes-whonix-torified-updates-proxy-check | cat

apparatus · October 5, 2024, 12:17pm

Did you change Whonix update proxy from sys-whonix to cacher?

What’s the output of this command in dom0?

grep -r "qubes.UpdatesProxy" /etc/qubes/policy.d/ | grep whonix

tempmail · October 5, 2024, 12:19pm

Oct 05 12:08:40 host systemd[1]: Starting qubes-whonix-torified-updates-proxy-check.service - Qubes Whonix Torified Updates Proxy Check…
Oct 05 12:08:40 host torified-updates-proxy-check[706]: /usr/lib/qubes-whonix/init/torified-updates-proxy-check: ERROR: PROXY_SERVER reachable but does not contain PROXY_META.
Oct 05 12:08:40 host torified-updates-proxy-check[706]: /usr/lib/qubes-whonix/init/torified-updates-proxy-check: Debugging information:
Oct 05 12:08:40 host torified-updates-proxy-check[706]: PROXY_SERVER: http://127.0.0.1:8082/
Oct 05 12:08:40 host torified-updates-proxy-check[706]: PROXY_META:
Oct 05 12:08:40 host torified-updates-proxy-check[706]: curl_output:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]: Not Found or APT Reconfiguration required
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Apt-Cacher NG Usage Information

Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]: You attempted to browse the contents of a virtual HTTP repository.
Oct 05 12:08:40 host torified-updates-proxy-check[706]: However, the intended way of use is the configuration of APT and
Oct 05 12:08:40 host torified-updates-proxy-check[706]: related package management systems to retrieve the software packages
Oct 05 12:08:40 host torified-updates-proxy-check[706]: through this service.
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
To configure APT for use of Apt-Cacher NG you need to…
Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]: EITHER: Configure APT to use a HTTP proxy by specifying
Oct 05 12:08:40 host torified-updates-proxy-check[706]: it in apt.conf or related configuration files, see
Oct 05 12:08:40 host torified-updates-proxy-check[706]: apt.conf manual page for details. Server and Port need to match
Oct 05 12:08:40 host torified-updates-proxy-check[706]: the values used to visit this page. For example,
Oct 05 12:08:40 host torified-updates-proxy-check[706]: edit /etc/apt/apt.conf (or create a new file called like /etc/apt/apt.conf.d/00aptproxy) and add the line:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Acquire::http::Proxy “http://127.0.0.1:8082”;

Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]: OR:
Oct 05 12:08:40 host torified-updates-proxy-check[706]: Edit the /etc/apt/sources.list file and edit the source lines
Oct 05 12:08:40 host torified-updates-proxy-check[706]: therein, replacing the mirror hostname with the hostname of this
Oct 05 12:08:40 host torified-updates-proxy-check[706]: server machine and the port with 8082 (adding a port if none
Oct 05 12:08:40 host torified-updates-proxy-check[706]: specified). For example:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]: deb Index of /debian stable main contrib non-free

Oct 05 12:08:40 host torified-updates-proxy-check[706]: deb-src Index of /debian stable main contrib non-free

Oct 05 12:08:40 host torified-updates-proxy-check[706]: deb https://get.docker.com/ubuntu docker main

Oct 05 12:08:40 host torified-updates-proxy-check[706]: becomes:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:
deb http://127.0.0.1:8082/ftp.debian.org/debian stable main contrib non-free

Oct 05 12:08:40 host torified-updates-proxy-check[706]: deb-src http://127.0.0.1:8082/ftp.debian.org/debian stable main contrib non-free

Oct 05 12:08:40 host torified-updates-proxy-check[706]: deb http://127.0.0.1:8082/HTTPS///get.docker.com/ubuntu docker main

Oct 05 12:08:40 host torified-updates-proxy-check[706]: Depending on the configuration, it might be possible to use a shortcut
Oct 05 12:08:40 host torified-updates-proxy-check[706]: for the base URLs without knowing the mirror, for example:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:
deb http://127.0.0.1:8082/debian stable main contrib non-free

Oct 05 12:08:40 host torified-updates-proxy-check[706]: Ask your system administrator for details.
Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Related links

Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Statistics report and configuration page for this Apt-Cacher NG installation. Also see Notes below.

Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Project Homepage
Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Notes

Oct 05 12:08:40 host systemd[1]: qubes-whonix-torified-updates-proxy-check.service: Main process exited, code=exited, status=1/FAILURE
Oct 05 12:08:40 host torified-updates-proxy-check[706]: This page is a pre-installed template not customized by the system
Oct 05 12:08:40 host torified-updates-proxy-check[706]: administrator. The links given above may contain default or guessed (and
Oct 05 12:08:40 host torified-updates-proxy-check[706]: therefore incorrect) components. The system administrator could adapt the
Oct 05 12:08:40 host torified-updates-proxy-check[706]: file userinfo.html in
Oct 05 12:08:40 host torified-updates-proxy-check[706]: Apt-Cacher NG’s configuration directory to set the correct contents.
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Server: Apt-Cacher-NG/3.7.4  |  <a
Oct 05 12:08:40 host torified-updates-proxy-check[706]: href=“/”>Usage Information  |  <a
Oct 05 12:08:40 host torified-updates-proxy-check[706]: href=“Donate”>Donate!  |  <a
Oct 05 12:08:40 host torified-updates-proxy-check[706]: href=“Apt-Cacher NG - Software Package Download Proxy”>Apt-Cacher NG homepage
Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:

Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host torified-updates-proxy-check[706]:
Oct 05 12:08:40 host systemd[1]: qubes-whonix-torified-updates-proxy-check.service: Failed with result ‘exit-code’.
Oct 05 12:08:40 host systemd[1]: Failed to start qubes-whonix-torified-updates-proxy-check.service - Qubes Whonix Torified Updates Proxy Check.

tempmail · October 5, 2024, 12:32pm

It would be too much to reveal, but this is what might interest you

/etc/qubes/policy.d/50-config-updates.policy:qubes.UpdatesProxy      *   @tag:whonix-updatevm    @default    allow target=sys-whonix
/etc/qubes/policy.d/50-config-updates.policy:qubes.UpdatesProxy      *   @tag:whonix-updatevm    @anyvm      deny
/etc/qubes/policy.d/50-config-updates.policy:qubes.UpdatesProxy	*	@type:TemplateVM	@default	allow target=cacher

tempmail · October 5, 2024, 12:36pm

It looks like somehow template messes up with cacher, although no policy relates cacher and whonix…

apparatus · October 5, 2024, 12:45pm

What’s the output of this command in dom0?

qvm-tags whonix-workstation-17

Do you have whonix-updatevm tag there?

tempmail · October 5, 2024, 12:47pm

Yes, I’m testing with yhou on a stock whonix-gateway-17. Just checked before you asked it.

apparatus · October 5, 2024, 12:51pm

What’s the output of these commands in sys-whonix and in whonix-workstation-17?

curl http://127.0.0.1:8082
ss -tulnp

tempmail · October 5, 2024, 3:14pm

It’s apt-cacher ng home page, I posted above

[template gateway user ~]% ss -tulnp
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
tcp LISTEN 0 4096 127.0.0.1:9050 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1%lo:8082 0.0.0.0:*

apparatus · October 5, 2024, 3:22pm

Is it the same for sys-whonix?
What’s the process that is using the port 8082 in sys-whonix? E.g.:

[gateway user ~]% sudo ss -tulnp | grep 8082
tcp   LISTEN 0      1024         0.0.0.0:8082       0.0.0.0:*    users:(("tinyproxy",pid=X,fd=X))   
tcp   LISTEN 0      1024            [::]:8082          [::]:*    users:(("tinyproxy",pid=X,fd=X))

tempmail · October 5, 2024, 3:43pm

Sorry!
sys-whonix

apt-cacher ng home page and

Summary

user@host:~$ ss -tulnp
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
udp UNCONN 0 0 127.0.0.1:5400 0.0.0.0:*
udp UNCONN 0 0 10.137.0.104:5300 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9154 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9155 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9152 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9153 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9158 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9159 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9156 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9157 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9162 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9163 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9160 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9161 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9166 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9167 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9164 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9165 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9170 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9171 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9168 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9169 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9174 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9175 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9041 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9172 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9173 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9178 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9179 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9176 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9052 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9177 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9182 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9183 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9050 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9180 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9181 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9186 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9187 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9184 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9185 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9190 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9191 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9188 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9189 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9194 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9195 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9192 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9193 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9198 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9199 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9196 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9197 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9202 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9203 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9200 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9201 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9206 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9207 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9204 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9205 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9210 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9211 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9208 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9209 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9214 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9215 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9212 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9213 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9223 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9222 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9221 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9220 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9219 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9218 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9217 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9216 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9229 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9228 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9227 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9102 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9226 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9103 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9225 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9100 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9224 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9101 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9106 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9107 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9104 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9105 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9110 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9111 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9108 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9109 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9114 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9115 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9118 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9117 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9122 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9123 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9124 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9125 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9150 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9040 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9050 0.0.0.0:*
tcp LISTEN 0 5 10.137.0.104:9051 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9191 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9190 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9199 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9198 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9197 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9196 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9195 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9194 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9193 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9192 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9207 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9206 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9205 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9204 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9203 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9202 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9201 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9200 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9215 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9214 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9213 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9212 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9211 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9210 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9209 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9208 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9218 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9219 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9216 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9217 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9222 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9223 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9220 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9221 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9226 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9103 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9227 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9102 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9224 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9101 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9225 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9100 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9228 0.0.0.0:*
tcp LISTEN 0 4096 10.137.0.104:9229 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9111 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9110 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9109 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9108 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9107 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9106 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1%lo:8082 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9105 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9104 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9118 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9117 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9115 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9114 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9125 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9124 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9123 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9122 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:9150 0.0.0.0:*

user@host:~$ sudo ss -tulnp | grep 8082
tcp LISTEN 0 4096 127.0.0.1%lo:8082 0.0.0.0:* users:((“systemd”,pid=1,fd=64))

In whonix-gateway-17:

[template gateway user ~]% ss -tulnp
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
tcp LISTEN 0 4096 127.0.0.1:9050 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1%lo:8082 0.0.0.0:*
[template gateway user ~]% curl http://127.0.0.1:8082
curl: (52) Empty reply from server
zsh: exit 52 curl http://127.0.0.1:8082