Hi,
My timezone is Switzerland(my correct timezone) set on setup but had lots of issues with connection. I usually just change local time to correct and would fix this issue. This issue got worse, so I manage to fix my first correcting local time, then change to the universal time(Which is 2 hours incorrect behind) then it will connect and fix the time itself after an hour eish. Now, no matter what I cannot connect.
I have checked BIOS and time is correct to my local time.
Hi,
What is the problem exactly? How does it prevent connecting to the VPN?
Do you have the correct time in the qubes, using Switzerland timezone?
My time zone is Switzerland and is set to that, and my BIOS is my correct time, when I go into qubes Dom0 is adding +2 hours and such via qubes time reflects the same in my other Qubes. I used to just change local time to correct and then I connect to my VPN, after a while this stopped working and did a wierd trick of going back and forth with universal and local time to try and connect, that no longer works and so I cant change local time without effecting universal and my understand that ntp doesnt work in dom0 and I prefer it remains inactive.
I could change my time zone so that it doesnt add the +/- time offset but still also not ideal.
What I could possiibly do as well is enable ntp service within the vpn Qube but that would require to disable kill switch which also pref dont want to do.
What timezone do you have set in dom0? UTC I assume. Why not change that
in dom0 and qubes to UTC-2?
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
in past i’ve had similar problem. it was fixed by:
adding a ntp package or similar to the qube/template that was the clock sync (usually sys-net) and set it up.
go on sys-net and check services see if it has clocksync enabled.