An OpenVPN certificate change is happening on July 20th (5pm UTC time) within the network of our VPN provider partner Windscribe. This reason for this change is documented in this article.
What this means is that the same change is happening for our InvizBox VPN and Windscribe users (as we use the Windscribe infrastructure to provide our service).
Mitigation in place
In order to minimise the impact of this change (prevent downtime on InvizBox devices), we kept all our OpenVPN configurations up to date with the latest ones from Windscribe.
We also pushed some patches to all the latest firmware to make sure these OpenVPN configuration files with new certificates were switched in to replace the previously running ones.
The patches were pushed on the following versions:
- InvizBox Go running 4.0.13 (latest - released June 17th 2020)
- InvizBox 2 running 0.1.7 (latest - released June 4th 2020 - labelled 0.1.8 for ProtonVPN users)
Similarly, as the final certificate change occurs and subsequently a change in encryption (early August), we will keep updating the OpenVPN configuration files to match the servers settings and push patches to force the InvizBox device to switch to these new configurations.
Why is my InvizBox not connecting
There are multiple reasons why the mitigation listed above may not have reached your InvizBox device. Here are some of them:
- You are using OpenVPN configuration downloaded from our support articles
- Your device is an InvizBox original which doesn't have automatic patching
- It was not connected during the transition period and failed to get the updates on time (still running a now obsolete configuration which can't connect)
- It was connected during the transition but is running an older firmware which wasn't patched
What do I do to get connected again
What is important here is to get the latest OpenVPN configuration in use on your device.
If you are using an InvizBox router
This is what needs to be done:
- Make sure you device got the latest VPN configuration by either leaving it connected to the Internet for an hour (or trigger an update from the Administration Interface)
- Switch VPN location as this takes the latest OpenVPN configuration when doing so (you can then return to your previous location)
If you are using OpenVPN configuration from our support articles
You need to download the latest configuration and swap them in to replace the older ones with an expired certificate.
You can find there in this section of the support site
Finally, if the above fails or you are unsure how to proceed, don't hesitate to contact us in support using the "Submit a Request" button at the top of this page or emailing us at firstname.lastname@example.org.
Note: If you are running an older firmware, we would strongly suggest that you update using the banner in your Administration Interface. That is however not necessary to get you re-connected.