I have been using freedome on my iPhone 5s and on my iPad mini (first generation). Both on latest SW versions. on ipad this works like a dream but on iPhone it has issues almost all the time to establish connection. Either it does not start automaticly and then when opening the freedom app it checks for a long time, sometimes (but seldom) giving an error that no access to VPN, in most cases no error message or anything, the service just doesn't start and I can't browse the internet until I turn it off, sometimes not even then.
Any tips and tricks here?
Which iOS version are you running on your iPhone?
Also do these connection issues occur on every location or a specific one?
Finally, you can refer to this article dealing with similar kind of problem.
I have the same problem. Since moving to IOS8 (IOS8.1.3) the VPN does'nt connect properly. I have reinstalled Fsecure and VPN several times. Nothing works except shutting IOS and reopen it. Terrible. If no solution is provided rapidly I sould disconnect Fsecure. I am in switzerland my provider is swisscom.
for me the reinstallation improved the situation, but every now and then still the solution kind of "freezes" and restart of phone is needed to enable freedome to work (or even have any network connectivity from iPhone)
have to say that I have exactly the same troubles with freezing Freedome and the problem seems to get even more frequent. My iPhone 6plus needs to be restarted on daily basis. It is not acceptable.
Furthermore ( maybe belongs to another discussion ), I simply can not connect to foreign web-pages, e.g. Netflix US or any other country, I am always redirected to local version. What could be the reason ?
There is an underlying bug in the iOS 8 operating system which causes this network disconnection when there is a VPN app like Freedome running on the device. We have hoped that Apple would fix this quickly but at least with the latest iOS releases the problem is still there.
We cannot directly affect this in any way, as the bug is in the VPN functionality in iOS 8, but we are trying now again to create a workaround so that this bug would not get triggered, or at least the effects of it wouldn't be this severe. We have some ideas how it possibly could be done but as of now, we don't yet have an estimate when we'd have this workaround ready.
This topic has been closed due to inactivity. If you would like to discuss this topic further, please start a new post.
You can reference this topic in your post by adding this link:
Visit the Community
Check our Forums or How-to & FAQs for advice or answers
View User Guides
Refer to our getting started guides and product manuals
Talk to our Support agents and get answers to your questions