<li><ahref="#the-vpn-fails-with-auth-failed-or-immediately-disconnects-with-encryption-failed">The VPN fails with “Auth failed” or immediately disconnects with “Encryption failed”</a></li>
<li><ahref="#my-provider-returns-auth-failed-but-my-credentials-are-correct">My provider returns “Auth failed” but my credentials are correct</a></li>
<p>You should contact with your provider to double check if there is interest in being added to Passepartout. Beware that some may be concerned instead. Ultimately, you can submit your provider request for a viability review to <ahref="mailto:providers@passepartoutvpn.app">providers@passepartoutvpn.app</a>.</p>
<h3id="im-on-wi-fi-but-my-device-shows-im-connected-via-lte">I’m on Wi-Fi but my device shows I’m connected via LTE</h3>
<p>The Wi-Fi/LTE icon (replace LTE with any cellular signal) while on VPN has been broken since iOS 10 or the like. It’s something that Apple is unable to fix or doesn’t bother fixing.</p>
<p>You should do a simple test. Verify your data consumption with your LTE provider website, normally phone providers have that. Now, when on VPN and the LTE icon appears in spite of Wi-Fi, download a relevant chunk of data. You may then learn that the plan is unaffected, implying that you’re actually connected via Wi-Fi.</p>
<p>I haven’t found a workaround for this and it’s been there for almost two years. Yeah, it’s a shame.</p>
<h3id="im-unable-to-add-my-wi-fi-to-trusted-networks">I’m unable to add my Wi-Fi to trusted networks</h3>
<p>Starting from iOS 12 (or 13?), iOS has somewhat restricted what apps can learn about Wi-Fi networks. The effect of this is the inability to add the connected Wi-Fi network to trusted networks, be it with a bogus “Wi-Fi” or “WLAN” SSID name, or with the alert “You are not connected to any Wi-Fi network.”.</p>
<p>To work around this issue, you should trust the network while the VPN is enabled and connected through such network. I will try to restore former behavior in future versions of Passepartout, or at least add an informational footer below the “Trusted networks” section.</p>
<h3id="the-vpn-fails-with-auth-failed-or-immediately-disconnects-with-encryption-failed">The VPN fails with “Auth failed” or immediately disconnects with “Encryption failed”</h3>
<p>This may happen when you rely on default OpenVPN encryption, which is normally Blowfish (BF-CBC). The algorithm, besides being unsupported by Passepartout, is also weak and therefore discouraged. In order to fix this issue, you must switch to AES encryption. Passepartout only supports AES, be it in CBC or GCM mode.</p>
<p>Set encryption explicitly in the server configuration, e.g.:</p>
<p>and don’t forget to update the client .ovpn as well with the <strong>exact same parameters</strong>.</p>
<p>If you want to leverage newer AES-GCM encryption, you could just use:</p>
<divclass="highlighter-rouge"><divclass="highlight"><preclass="highlight"><code>ncp-ciphers AES-256-GCM # or AES-128-GCM
</code></pre></div></div>
<p>and the client wouldn’t need to change a thing, because the algorithm will be enforced by the server no matter what.</p>
<h3id="my-provider-returns-auth-failed-but-my-credentials-are-correct">My provider returns “Auth failed” but my credentials are correct</h3>
<p>Bear in mind that some providers require specific credentials for their direct OpenVPN servers. That’s why Passepartout, in those cases, has a convenient link in the bottom of the Account screen showing you where to find such credentials on your provider’s website.</p>
<h3id="the-configuration-file-contains-an-unsupported-option-external-file">The configuration file contains an unsupported option (external file)</h3>
<p>Due to easier interoperability, the app does not support external files in the .ovpn main configuration. That’s because more often than not, it may not make sense referring to relative paths in a mobile device environment. Think of the Mail app for example. The fix is straightforward though, say you have an external <codeclass="highlighter-rouge">ca</code> file:</p>
<p>The same applies to other settings like <codeclass="highlighter-rouge">cert</code>, <codeclass="highlighter-rouge">key</code>, <codeclass="highlighter-rouge">tls-auth</code> and <codeclass="highlighter-rouge">tls-crypt</code>.</p>
<h3id="why-dont-siri-shortcuts-execute-in-the-background">Why don’t Siri Shortcuts execute in the background?</h3>
<p>Unfortunately Apple is guilty of not fixing a related bug. I mean, it’s been there for years -since iOS 9 with my first bug report dating back to 2017- without them caring at all. No feedback and not even a proper response. And of course, no progress.</p>
<p>This is one of the several threads remarking the issue:</p>
<p>Now, due to this bug, App Extensions can’t control VPN using custom protocols -Siri Intents Extension in this case, in order to run shortcuts in the background. Only native VPN protocols work (IKEv2, IPsec etc.).</p>
<p>In short, there’s really <em>nothing</em> I can do about it.</p>
<p>Unless <codeclass="highlighter-rouge">redirect-gateway</code> is either:</p>
<ul>
<li>Explicitly added to the .ovpn configuration</li>
<li>Pushed from the server</li>
</ul>
<p>the default gateway is NOT changed. That is, your external IP won’t be the VPN’s IP. Double check the “Default gateway” entry in the “Configuration” page to see how your host profile looks like. On the other hand, the default gateway is always enforced for provider profiles.</p>
<p>This has been recently fixed in Passepartout 1.6.0 as it’s the standard OpenVPN behavior. Before 1.6.0, Passepartout erroneously assumed that all traffic should go through the VPN implicitly.</p>
<h3id="id-like-to-see-a-today-widget-in-the-notification-center">I’d like to see a Today Widget in the Notification Center</h3>
<p>The reason behind not providing a widget is exactly the same as Siri Shortcuts. A widget would still need to open the app, thus making it quite useless.</p>
<h3id="id-like-to-see-my-ip-address-in-the-app">I’d like to see my IP address in the app</h3>
<p>The reason why Passepartout does not present any personal information in app is <em>privacy</em>. Obtaining one’s IP address, regardless of being connected to a VPN or not, involves querying -and trusting- a third party service. Knowing such info is also of little use, given that most of the time you don’t want to share your VPN IP address and therefore link your identity to it. However, this feature might be introduced later as a diagnostic tool.</p>
<h3id="mullvad-ignores-my-custom-dns-settings">Mullvad ignores my custom DNS settings</h3>
<p>It looks like Mullvad “hijacks” DNS on default endpoints, making custom DNS settings irrelevant. In order to do custom DNS with Mullvad, make sure to explicitly pick the “Custom DNS” preset, which will let you connect to the UDP:1400 and TCP:1401 endpoints. These endpoints do support custom DNS servers instead.</p>
<p>Until version 1.7.0 for iOS, you will have to do a manual “Refresh infrastructure” in order to access the new preset.</p>
<p>Read the <ahref="https://github.com/passepartoutvpn/api-source-mullvad/issues/1">related report on GitHub</a>.</p>
Copyright (c) 2018 <ahref="https://davidederosa.com"title="The author website">Davide De Rosa</a><br/>
The logo is taken from the awesome <ahref="https://www.iconfinder.com/iconsets/circle-icons-1"title="Circle Icons">Circle Icons</a> set by <ahref="https://www.elegantthemes.com/"title="Elegant Themes">Nick Roach</a>
