Update vpn.md

[qubesfan35267]

I suggest to move line 291 to 288. For some reason the script was not establishing the vpn tunnel when left on 291.

[taradiddles]

Hi ! From what I see the notify-send line doesn't have any function other than telling the user what's happening. So if moving it earlier "fixes" the script, it would probably be because earlier instructions don't have enough time to complete, and notify-send is similiar to have a sleep command at that position. As a test, rather than switching the position, could you try to add - say - sleep 4 instead, and see what happens ?

That said, using sleep is fragile, there should be a loop exiting on the completion of the task (or on max tries / timeout) instead. The vpn instructions use sleep instructions here and there (as well as things that shouldn't be needed like sync) so it looks like it should be reworked (there's a longer discussion here about updating the instructions by the way).

[observinglynx]

I believe you've stumbled into the same issue 691be23 was trying to address. Short explanation of the problem, the notification daemon wasn't ready on time to accept the message coming from the script and always timed out. The solution was simply to move it lower as the VPN initialization takes some time therefore the notification daemon should be ready by the time the VPN connection gets established.

From your comment, it seems like your notification daemon is ready before the VPN script runs however the VPN fails to initialize. Please check whether the VPN does get an established connection and check for notification/vpn errors in journalctl.