Solved.
Not sure if it was relevant but since the most recent Whonix updates this has
gone back to normal.
Thanks to all.
--
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
I would ask on the Whonix Forum. https://forums.whonix.org/
--
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
Yeh, the anon-whonix app vm is routed through sys-whonix properly. I haven't
changed that from default.
I do route most non-whonix app vms through a vpn in a proxy vm but that all
works as it should.
Both systems have worked independently and as expected for months.
Checking today some IP
On Sat, January 27, 2018 11:46 am, code9n wrote:
> Running the WhonixCheck from the default anon-whonix app vm in the Qubes
> manager list; the fail warning basically says:
>
> SocksPort test [fails]. ... (curl exit code: [7] - [failed to connect to
> host])
>
> The browser - anon-whonix app vm
Running the WhonixCheck from the default anon-whonix app vm in the Qubes
manager list; the fail warning basically says:
SocksPort test [fails]. ... (curl exit code: [7] - [failed to connect to host])
The browser - anon-whonix app vm (default)/Tor browser - opens like normal to
the Whonix page