How I «fixed» TrustConnect by installing and using another and similar application…
All URL's shown below are clickable and open the link in a new browser tab or in a separate window dependent on your browser configuration.
As I at this point weren't sure if this application would suit the purposes, I selected an initial subscription for one month (US$ 6) only.
Why I downloaded the OpenVPN GUI instead of the PT client, is because the PT client (from informations found on other sites) is an about 30 MB download that will install 50–80 MB of programs and data dependent on the OS and selected options, while the OpenVPN GUI is a 1.8 MB download that will install less than 5 MB of programs and data, while still doing the job of establishing a fully secure connection through PT servers.
In short: Why install more than you actually need?
You can download user profiles for as many access servers you want.
When more than one *.ovpn file is found in the config folder, the context menu for OpenVPN GUI (when you right-click the OpenVPN GUI icon in the task bar tray) automatically change to directly give you the option to select which server you want to connect to (not as in TrustConnect where server selection is done through a separate settings window).
NOTE: | From informations found on other sites, after the initial PT account registration, and although OpenVPN GUI instantly make a successful connection to PT servers, it may still take some time (usually less than one hour) before the new account registration is validated and propagated to all worldwide PT servers and you can connect to the Internet. In my case, I noticed that I couldn't access web sites, use FTP, etc. for the first about 10 minutes after OpenVPN GUI had made the first connection to the PT server. |
Why I have to use services like TrustConnect, and now OpenVPN, is because I have home Internet connection through a local open (unencrypted) network.
In addition, that network do also have restricted port access, so without an external VPN service or similar, I can for example not use FTP (e.g. to be able to upload this page).
In total, I currently own seven different domains, wherof some of these also have multiple subdomains, and where I have some quite large websites, for example https://trafikksiden.motocross.io that now contain 1,000+ subpages with traffic regulations and other informations.
Although I've only have used Privatetunnel for some days so far, here are some of my experiences and comparisions with Privatetunnel (with OpenVPN GUI) vs. COMODO TrustConnect:
Privatetunnel (with OpenVPN GUI) | COMODO TrustConnect | |
OpenVPN version used (latest available download of the application per June 2017) | 2.3.17 Build date Jun 20 2017 | 2.1.1 Build date Dec 11 2009 |
Access server connection protocols | TCP and UDP | TCP only |
Remote TCP/IP endpoints opened while connecting | 1 | 3 |
Remote TCP/IP endpoints open when connected | 1 | 2 |
Behaviour when access server connection somehow is dropped or lost, e.g. due to poor WiFi-hotspot signal strength | Attempting to reconnect automatically without any popup error messages or other dialog boxes shown | Usually disconnect and terminate connection with a popup error message, and where you have to reconnect manually by clicking «Connect» in the «User Authentication» dialog window |
Can access servers using UDP ports, e.g. when using time synchronization servers and other services commonly using UDP only | YES | NO |
GUI system memory usage | Approx. 3.6 MB | Approx. 5.2 MB |