On Sunday, February 12, 2017 at 3:01:23 AM UTC-5, Andrew David Wong wrote:
...
> No. I explain the procedure in the first post of that thread.
> Please try reading it again.
...
Done, works exactly as advertised ! And both vm(s) actually work !
Thank you!
--
You received this message because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2017-02-11 21:46, elsiebuck...@gmail.com wrote:
> On Saturday, February 11, 2017 at 9:08:56 PM UTC-5, Andrew David
> Wong wrote:
>>
>> You should try to the method I described here:
>>
>>
On Saturday, February 11, 2017 at 9:08:56 PM UTC-5, Andrew David Wong wrote:
>
> You should try to the method I described here:
>
> https://groups.google.com/d/topic/qubes-users/fSiFkQeoqGE/discussion
>
The difference being instead of google.com use 74.125.192.113, 74.125.192.100,
I tried tinyproxy, I'm fairly certain proxies in general willNOT work with
https.
Am I right about this? Or have I not done something right?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving
Well I hate to beat a dead horse...
Nether vm(s) will connect without refreshing several multiple times. This isn't
acceptable. I prefer dnsmasq rather than some firefox addon. Actually, I'm
pretty sure dnsmasq won't do in this case. Some other solution...
--
You received this message because
Don't know what I did exactly, but both vm(s) (email and banking) are now
working. Which didn't make sense why neither would connect.
In the end, I made two proxyvm(s) where I "denied all but..." and added the
domains as they didn't connect until they did.
My original problem was, after
