Before dealing with the topic, i want you to know that i regret the friction we had during our last encounter. On this forum you are - as far as i'm concerned - the boss and i therefore seriously intend to stick to the 2 rules shown below.
Both on my iPhone and my iPad i tried to use Mobile in conjunction with my FRITZ!Box 7590 and the app OpenVPN, version 3.2.3. Tests stipulated an OK
But when switching 'eBlockerMobile' in Settings ON, importing the exported .ovpn-files in the OpenVPN-app on iPad and iPhone, i get the message
Would appreciate your advice.
Rob
@robfranssen-fr I'm glad you are back, Rob! Seriously!! But calling me the boss is a little exaggerated. I just try to share my knowledge to help everyone to more online privacy. 😎
Now with your issue: I see from your screenshot you are connected to your home network (WLAN). This is not the intended use case for eBlocker Mobile as it's expected you to connect from outside your home network (when you are mobile).💡
Have you tried to connect when you are not connected to WLAN but rather use the mobile network (say 4G/5G/LTE)?
If the issue persists on 4G/5G, please share the OpenVPN logfile (click on the "script roll" icon in the upper right corner of the iOS client).
THX!
I just try to share my knowledge to help
Got the message Boss 🙂 (please consider it a honorary title given the amount of time you spend)
As long as i'm not fooling around with eBlocker Mobile, ALL checkes are green (Status, HTTP support, Function test and Doctor) on ALL my iDevices; Doctor only warns for automatic network mode)
In the past i have tried eBlocker Mobile as well and it always worked, whether on WiFi or on mobile network. And yes, i know it doesn't make sense to use eBlocker Mobile on WiFi; but still. In the past the OpenVPN-app never gave an error-message what-so-ever, but i'm sure the 'Device is monitored' in the Function test showed an exclamation mark when connected to WiFi.
So, back to your response. On my iPhone i checked again that all Function tests were green, switched OFF WiFi to connect to 4G (works because i can visit internet using 4G), opened the OpenVPN-app (with the eBlocker-ovpn-file) and tried to connect. Result: "There was an error attempting etc.". Of course i can't check the Function test on my iPhone because the eBlocker is not connected (by the OpenVPN-connection). As soon as i restore WiFi, all Function tests are shining green again and as bright as can be 😉
Good ideas are welcome. Rob
@robfranssen-fr Honestly I don't care about a title, but I always appreciate if the one who is seeking help, is just answering the questions I've asked. No more, no less. That speeds up the solution progress tremendously and makes everyone happier - including myself 😉
So I try again:
If the issue persists on 4G/5G, please share the OpenVPN logfile (click on the "script roll" icon in the upper right corner of the iOS client).
THX!
As you will appreciate, i have no intention to start on the wrong footing again. And i really do apologise for not answering your question before; i simply overlooked it!
Rob
@robfranssen-fr Thanks for the logs!🙏
To me this looks good so far, but it seems it is only the first part of the story. 🤔
Is this the whole file - or maybe just a copy/pase of the first part/screen?
Best is to save the file (envelope icon upper right once you open the logfile) an then share this file here.
THX!
Disabled WiFi, emptied logfile of OpenVPN-app, tried to connect and shared the new logfile by mail. Then copied and pasted below:
2022-01-15 05:42:27 ----- OpenVPN Start -----
OpenVPN core 3.git::58b92569 ios arm64 64-bit
2022-01-15 05:42:27 OpenVPN core 3.git::58b92569 ios arm64 64-bit
2022-01-15 05:42:27 Frame=512/2048/512 mssfix-ctrl=1250
2022-01-15 05:42:27 UNUSED OPTIONS
4 [resolv-retry] [infinite]
5 [nobind]
6 [persist-key]
11 [tls-cipher] [DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-G...]
12 [verb] [1]
14 [script-security] [2]
15 [down] [/etc/openvpn/update-resolv-conf]
16 [up] [/etc/openvpn/update-resolv-conf]
2022-01-15 05:42:27 EVENT: RESOLVE
2022-01-15 05:42:27 Contacting [45.88.8.122]:1194/UDP via UDP
2022-01-15 05:42:27 EVENT: WAIT
2022-01-15 05:42:27 Connecting to [45.88.8.122]:1194 (45.88.8.122) via UDPv4
2022-01-15 05:42:27 EVENT: CONNECTING
2022-01-15 05:42:27 Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client
2022-01-15 05:42:27 Creds: UsernameEmpty/PasswordEmpty
2022-01-15 05:42:27 Peer Info:
IV_VER=3.git::58b92569
IV_PLAT=ios
IV_NCP=2
IV_TCPNL=1
IV_PROTO=2
IV_AUTO_SESS=1
IV_GUI_VER=net.openvpn.connect.ios_3.2.3-3760
IV_SSO=openurl
2022-01-15 05:42:27 VERIFY OK: depth=1, /O=eBlocker Open Source/CN=eBlocker Mobile CA
2022-01-15 05:42:27 VERIFY OK: depth=0, /CN=eBlocker Mobile Server
2022-01-15 05:42:33 Session invalidated: KEEPALIVE_TIMEOUT
2022-01-15 05:42:33 Client terminated, restarting in 2000 ms...
2022-01-15 05:42:35 EVENT: RECONNECTING
2022-01-15 05:42:35 EVENT: RESOLVE
2022-01-15 05:42:35 Contacting [45.88.8.122]:1194/UDP via UDP
2022-01-15 05:42:35 EVENT: WAIT
2022-01-15 05:42:35 Connecting to [45.88.8.122]:1194 (45.88.8.122) via UDPv4
2022-01-15 05:42:35 EVENT: CONNECTING
2022-01-15 05:42:35 Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client
2022-01-15 05:42:35 Creds: UsernameEmpty/PasswordEmpty
2022-01-15 05:42:35 Peer Info:
IV_VER=3.git::58b92569
IV_PLAT=ios
IV_NCP=2
IV_TCPNL=1
IV_PROTO=2
IV_AUTO_SESS=1
IV_GUI_VER=net.openvpn.connect.ios_3.2.3-3760
IV_SSO=openurl
2022-01-15 05:42:35 VERIFY OK: depth=1, /O=eBlocker Open Source/CN=eBlocker Mobile CA
2022-01-15 05:42:35 VERIFY OK: depth=0, /CN=eBlocker Mobile Server
2022-01-15 05:42:40 Session invalidated: KEEPALIVE_TIMEOUT
2022-01-15 05:42:40 Client terminated, restarting in 2000 ms...
… [edited log to keep the thread compact, Random] …
@robfranssen-fr Thanks, Rob.The connection times out and does not get established („Session invalidated: KEEPALIVE_TIMEOUT / CONNECTION_TIMEOUT [ERR]“)🤔
Just to make sure, please
- „Kill“ OpenVPN app on iOS („double click“ and then swipe app to top)
- Reboot iOS (hold on/off button to switch off)
- Reboot eBlocker (Settings > System > Reboot)
- Check eBlocker Mobile is enabled (Settings > eBlocker Mobile)
- Re-install the eBlocker Mobile config in iOS OpenVPN app (Settings > Devices > „select mobile device“ - Choose tab „Mobile“ and download file. Open in OpenVPN app and add)
- Retry to connect
- Post OpenVPN log if unsuccessful
Please keep the order and execute each step carefully, not skipping anything 😉
Maybe a helpful hint: if you make changes to the eBlocker Mobile settings you need to download the config and re-install it anew - always!
THX!
Please keep the order and execute each step carefully
Followed instructions exactly on my iPhone, only adding
1a. Remove old ovpn-configfile in OpenVPN app
1b. Empty log of OpenVPN app
5a. Disable WiFi
Unfortunately, i get the same error message.
2022-01-15 09:41:18 ----- OpenVPN Start -----
OpenVPN core 3.git::58b92569 ios arm64 64-bit
2022-01-15 09:41:18 OpenVPN core 3.git::58b92569 ios arm64 64-bit
2022-01-15 09:41:18 Frame=512/2048/512 mssfix-ctrl=1250
2022-01-15 09:41:18 UNUSED OPTIONS
4 [resolv-retry] [infinite]
5 [nobind]
6 [persist-key]
11 [tls-cipher] [DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-G...]
12 [verb] [1]
14 [script-security] [2]
15 [down] [/etc/openvpn/update-resolv-conf]
16 [up] [/etc/openvpn/update-resolv-conf]
2022-01-15 09:41:18 EVENT: RESOLVE
2022-01-15 09:41:18 Contacting [45.88.8.122]:1194/UDP via UDP
2022-01-15 09:41:18 EVENT: WAIT
2022-01-15 09:41:18 Connecting to [45.88.8.122]:1194 (45.88.8.122) via UDPv4
2022-01-15 09:41:18 EVENT: CONNECTING
2022-01-15 09:41:18 Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client
2022-01-15 09:41:18 Creds: UsernameEmpty/PasswordEmpty
2022-01-15 09:41:18 Peer Info:
IV_VER=3.git::58b92569
IV_PLAT=ios
IV_NCP=2
IV_TCPNL=1
IV_PROTO=2
IV_AUTO_SESS=1
IV_GUI_VER=net.openvpn.connect.ios_3.2.3-3760
IV_SSO=openurl
2022-01-15 09:41:18 VERIFY OK: depth=1, /O=eBlocker Open Source/CN=eBlocker Mobile CA
2022-01-15 09:41:18 VERIFY OK: depth=0, /CN=eBlocker Mobile Server
2022-01-15 09:41:23 Session invalidated: KEEPALIVE_TIMEOUT
2022-01-15 09:41:23 Client terminated, restarting in 2000 ms...
2022-01-15 09:41:25 EVENT: RECONNECTING
2022-01-15 09:41:25 EVENT: RESOLVE
2022-01-15 09:41:25 Contacting [45.88.8.122]:1194/UDP via UDP
2022-01-15 09:41:25 EVENT: WAIT
2022-01-15 09:41:25 Connecting to [45.88.8.122]:1194 (45.88.8.122) via UDPv4
2022-01-15 09:41:25 EVENT: CONNECTING
2022-01-15 09:41:25 Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client
2022-01-15 09:41:25 Creds: UsernameEmpty/PasswordEmpty
2022-01-15 09:41:25 Peer Info:
IV_VER=3.git::58b92569
IV_PLAT=ios
IV_NCP=2
IV_TCPNL=1
IV_PROTO=2
IV_AUTO_SESS=1
IV_GUI_VER=net.openvpn.connect.ios_3.2.3-3760
IV_SSO=openurl
2022-01-15 09:41:25 VERIFY OK: depth=1, /O=eBlocker Open Source/CN=eBlocker Mobile CA
2022-01-15 09:41:25 VERIFY OK: depth=0, /CN=eBlocker Mobile Server
2022-01-15 09:41:31 Session invalidated: KEEPALIVE_TIMEOUT
2022-01-15 09:41:31 Client terminated, restarting in 2000 ms...
2022-01-15 09:41:33 EVENT: RECONNECTING
2022-01-15 09:41:33 EVENT: RESOLVE
2022-01-15 09:41:33 Contacting [45.88.8.122]:1194/UDP via UDP
2022-01-15 09:41:33 EVENT: WAIT
2022-01-15 09:41:33 Connecting to [45.88.8.122]:1194 (45.88.8.122) via UDPv4
2022-01-15 09:41:33 EVENT: CONNECTING
2022-01-15 09:41:33 Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client
2022-01-15 09:41:33 Creds: UsernameEmpty/PasswordEmpty
2022-01-15 09:41:33 Peer Info:
IV_VER=3.git::58b92569
IV_PLAT=ios
IV_NCP=2
IV_TCPNL=1
IV_PROTO=2
IV_AUTO_SESS=1
IV_GUI_VER=net.openvpn.connect.ios_3.2.3-3760
IV_SSO=openurl
2022-01-15 09:41:33 VERIFY OK: depth=1, /O=eBlocker Open Source/CN=eBlocker Mobile CA
2022-01-15 09:41:33 VERIFY OK: depth=0, /CN=eBlocker Mobile Server
2022-01-15 09:41:38 Session invalidated: KEEPALIVE_TIMEOUT
2022-01-15 09:41:38 Client terminated, restarting in 2000 ms...
2022-01-15 09:41:40 EVENT: RECONNECTING
2022-01-15 09:41:40 EVENT: RESOLVE
2022-01-15 09:41:40 Contacting [45.88.8.122]:1194/UDP via UDP
2022-01-15 09:41:40 EVENT: WAIT
2022-01-15 09:41:40 Connecting to [45.88.8.122]:1194 (45.88.8.122) via UDPv4
2022-01-15 09:41:40 EVENT: CONNECTING
2022-01-15 09:41:40 Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client
2022-01-15 09:41:40 Creds: UsernameEmpty/PasswordEmpty
2022-01-15 09:41:40 Peer Info:
IV_VER=3.git::58b92569
IV_PLAT=ios
IV_NCP=2
IV_TCPNL=1
IV_PROTO=2
IV_AUTO_SESS=1
IV_GUI_VER=net.openvpn.connect.ios_3.2.3-3760
IV_SSO=openurl
2022-01-15 09:41:40 VERIFY OK: depth=1, /O=eBlocker Open Source/CN=eBlocker Mobile CA
2022-01-15 09:41:40 VERIFY OK: depth=0, /CN=eBlocker Mobile Server
2022-01-15 09:41:45 Session invalidated: KEEPALIVE_TIMEOUT
2022-01-15 09:41:45 Client terminated, restarting in 2000 ms...
2022-01-15 09:41:47 EVENT: RECONNECTING
2022-01-15 09:41:47 EVENT: RESOLVE
2022-01-15 09:41:47 Contacting [45.88.8.122]:1194/UDP via UDP
2022-01-15 09:41:47 EVENT: WAIT
2022-01-15 09:41:47 Connecting to [45.88.8.122]:1194 (45.88.8.122) via UDPv4
2022-01-15 09:41:47 EVENT: CONNECTING
2022-01-15 09:41:47 Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client
2022-01-15 09:41:47 Creds: UsernameEmpty/PasswordEmpty
2022-01-15 09:41:47 Peer Info:
IV_VER=3.git::58b92569
IV_PLAT=ios
IV_NCP=2
IV_TCPNL=1
IV_PROTO=2
IV_AUTO_SESS=1
IV_GUI_VER=net.openvpn.connect.ios_3.2.3-3760
IV_SSO=openurl
2022-01-15 09:41:47 VERIFY OK: depth=1, /O=eBlocker Open Source/CN=eBlocker Mobile CA
2022-01-15 09:41:47 VERIFY OK: depth=0, /CN=eBlocker Mobile Server
2022-01-15 09:41:52 Session invalidated: KEEPALIVE_TIMEOUT
2022-01-15 09:41:52 Client terminated, restarting in 2000 ms...
2022-01-15 09:41:55 EVENT: RECONNECTING
2022-01-15 09:41:55 EVENT: RESOLVE
2022-01-15 09:41:55 Contacting [45.88.8.122]:1194/UDP via UDP
2022-01-15 09:41:55 EVENT: WAIT
2022-01-15 09:41:55 Connecting to [45.88.8.122]:1194 (45.88.8.122) via UDPv4
2022-01-15 09:41:55 EVENT: CONNECTING
2022-01-15 09:41:55 Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client
2022-01-15 09:41:55 Creds: UsernameEmpty/PasswordEmpty
2022-01-15 09:41:55 Peer Info:
IV_VER=3.git::58b92569
IV_PLAT=ios
IV_NCP=2
IV_TCPNL=1
IV_PROTO=2
IV_AUTO_SESS=1
IV_GUI_VER=net.openvpn.connect.ios_3.2.3-3760
IV_SSO=openurl
2022-01-15 09:41:55 VERIFY OK: depth=1, /O=eBlocker Open Source/CN=eBlocker Mobile CA
2022-01-15 09:41:55 VERIFY OK: depth=0, /CN=eBlocker Mobile Server
2022-01-15 09:42:00 Session invalidated: KEEPALIVE_TIMEOUT
2022-01-15 09:42:00 Client terminated, restarting in 2000 ms...
2022-01-15 09:42:02 EVENT: RECONNECTING
2022-01-15 09:42:02 EVENT: RESOLVE
2022-01-15 09:42:02 Contacting [45.88.8.122]:1194/UDP via UDP
2022-01-15 09:42:02 EVENT: WAIT
2022-01-15 09:42:02 Connecting to [45.88.8.122]:1194 (45.88.8.122) via UDPv4
2022-01-15 09:42:02 EVENT: CONNECTING
2022-01-15 09:42:02 Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client
2022-01-15 09:42:02 Creds: UsernameEmpty/PasswordEmpty
2022-01-15 09:42:02 Peer Info:
IV_VER=3.git::58b92569
IV_PLAT=ios
IV_NCP=2
IV_TCPNL=1
IV_PROTO=2
IV_AUTO_SESS=1
IV_GUI_VER=net.openvpn.connect.ios_3.2.3-3760
IV_SSO=openurl
2022-01-15 09:42:02 VERIFY OK: depth=1, /O=eBlocker Open Source/CN=eBlocker Mobile CA
2022-01-15 09:42:02 VERIFY OK: depth=0, /CN=eBlocker Mobile Server
2022-01-15 09:42:07 Session invalidated: KEEPALIVE_TIMEOUT
2022-01-15 09:42:07 Client terminated, restarting in 2000 ms...
2022-01-15 09:42:09 EVENT: RECONNECTING
2022-01-15 09:42:09 EVENT: RESOLVE
2022-01-15 09:42:09 Contacting [45.88.8.122]:1194/UDP via UDP
2022-01-15 09:42:09 EVENT: WAIT
2022-01-15 09:42:09 Connecting to [45.88.8.122]:1194 (45.88.8.122) via UDPv4
2022-01-15 09:42:10 EVENT: CONNECTING
2022-01-15 09:42:10 Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client
2022-01-15 09:42:10 Creds: UsernameEmpty/PasswordEmpty
2022-01-15 09:42:10 Peer Info:
IV_VER=3.git::58b92569
IV_PLAT=ios
IV_NCP=2
IV_TCPNL=1
IV_PROTO=2
IV_AUTO_SESS=1
IV_GUI_VER=net.openvpn.connect.ios_3.2.3-3760
IV_SSO=openurl
2022-01-15 09:42:10 VERIFY OK: depth=1, /O=eBlocker Open Source/CN=eBlocker Mobile CA
2022-01-15 09:42:10 VERIFY OK: depth=0, /CN=eBlocker Mobile Server
2022-01-15 09:42:15 Session invalidated: KEEPALIVE_TIMEOUT
2022-01-15 09:42:15 Client terminated, restarting in 2000 ms...
2022-01-15 09:42:17 EVENT: RECONNECTING
2022-01-15 09:42:17 EVENT: RESOLVE
2022-01-15 09:42:17 Contacting [45.88.8.122]:1194/UDP via UDP
2022-01-15 09:42:17 EVENT: WAIT
2022-01-15 09:42:17 Connecting to [45.88.8.122]:1194 (45.88.8.122) via UDPv4
2022-01-15 09:42:17 EVENT: CONNECTING
2022-01-15 09:42:17 Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client
2022-01-15 09:42:17 Creds: UsernameEmpty/PasswordEmpty
2022-01-15 09:42:17 Peer Info:
IV_VER=3.git::58b92569
IV_PLAT=ios
IV_NCP=2
IV_TCPNL=1
IV_PROTO=2
IV_AUTO_SESS=1
IV_GUI_VER=net.openvpn.connect.ios_3.2.3-3760
IV_SSO=openurl
2022-01-15 09:42:17 VERIFY OK: depth=1, /O=eBlocker Open Source/CN=eBlocker Mobile CA
2022-01-15 09:42:17 VERIFY OK: depth=0, /CN=eBlocker Mobile Server
2022-01-15 09:42:18 EVENT: CONNECTION_TIMEOUT [ERR]
2022-01-15 09:42:18 Raw stats on disconnect:
BYTES_IN : 24894
BYTES_OUT : 78981
PACKETS_IN : 45
PACKETS_OUT : 118
KEEPALIVE_TIMEOUT : 8
CONNECTION_TIMEOUT : 1
N_RECONNECT : 8
2022-01-15 09:42:18 Performance stats on disconnect:
CPU usage (microseconds): 167811
Network bytes per CPU second: 618999
Tunnel bytes per CPU second: 0
2022-01-15 09:42:18 EVENT: DISCONNECTED
2022-01-15 09:42:18 Raw stats on disconnect:
BYTES_IN : 24894
BYTES_OUT : 78981
PACKETS_IN : 45
PACKETS_OUT : 118
KEEPALIVE_TIMEOUT : 8
CONNECTION_TIMEOUT : 1
N_RECONNECT : 8
2022-01-15 09:42:18 Performance stats on disconnect:
CPU usage (microseconds): 177254
Network bytes per CPU second: 586023
Tunnel bytes per CPU second: 0
@robfranssen-fr 🤔 I‘m clueless, honestly.
Last thing to double check, that eBlocker shows eBlocker Mobile OK (still). Settings > eBlocker Mobile - switch off, check connection test.
It would also be great if you could verify your external IP. Please use a client connected to Wifi and click the Privacy Check button in the upper right of our website. Post IP address shown on page.
Please send Settings > System > Diagnosis report file to support at eBlocker.org. Some more talented supporter needs to look at it - but this might take a while.
THX for you patience!
Hello @robfranssen-fr,
I tested the latest version 3.2.3 (3760) of the OpenVPN app on iOS with eBlockerOS 2.8.2 and it worked.
Have you changed any settings in the app from the defaults? When I open the hamburger menu in the upper left corner and tap on settings I get:
- Battery Saver: disabled
- Seamless Tunnel: disabled
- VPN Protocol: adaptive
- IPv6: no preference
- Connection timeout: 30 sec
- Allow compression (insecure): no
- AES-CBC Cipher Algorithm: enabled
- Minimum TLS Version: profile default
- DNS fallback: enabled
- Connect via: any network
- Layer 2 Reachability: enabled
Do you have the same settings in your app?
and it worked.
In my case it didn't Boris.
2 different settings compared with yours: timeout 1 min (so what) now changed to 30 sec and AES/CBC was disabled but i changed it to enabled now. It's s the first time i've seen this settings-menu ever.
On my iPhone i checked eBlocker/Settings/eBlocker Mobile/Connection test: Success and switched Mobile back on.
Deleted eBlocker-profile in the OpenVPN app and created and imported a new one from my iPhone-dashboard; just to make sure.
Disabled WiFi to get to 4G
Tried to connect by means of profile in OpenVPN app. Result: "There was an error..."
Rob
@robfranssen-fr
Thank you for your diagnostics report. The good news is that there are no relevant error messages in the log files. The bad news is that there are no successful connection attempts in the openvpn.log. The last entry is "Initialization Sequence Completed". That means that the server is ready for incoming connections.
When I look at my own server openvpn.log I see some log messages each time I connect, e.g. "VERIFY OK", "peer info", etc.
So I can only assume that the connection attempts from your iOS app don't really come through to eBlocker's OpenVPN server. In the past sometimes it helped on my Fritzbox to delete the port forwarding and set it up again.
@bpr Rebooted iPhone, eBlocker and FRITZ!Box 7590, but to no avail.
Removed and reinitiated port sharing for FRITZ!Box 7590 and checked through eBlocker/Settings/eBlocker Mobile/Connection test. Result: success
Switches eBlocker Mobile to ON again and tried to connect my iPhone through 4G again; same result: "There was an error..."
Enabled hotspot on my iPhone and connected my iPad's WiFi to this hotspot. Then tried to connect with the OpenVPN-app on my iPad. Result: "There was an error..." Which conclusion can be drawn from this?
Probably not relevant, but in the past i could connect with the OpenVPN-app using the WiFi-connection to my FRITZ!Box. I know this doesn't make sense, but i wanted to mention this anyhow.
Hope you have a few other ideas 'up your sleeve'.
@robfranssen-fr As @bpr pointed out: The problem must be "somewhere" in the port forwarding because the eBlocker Mobile requests do not reach your eBlocker at all.
Things I'd try:
- Make sure eBlocker is directly connected to your router to a regular port (not to the Guest Network port, not to a switch or such).
- Also forward TCP (so not just UDP) with the same port to eBlocker.
- Set up a different mobile device (preferably not Apple based) to see whether the issue is correlated to iOS.
Good luck!
@benne
eBlocker is - and always has been - on LAN 2 and on address 192.168.178.2
Added TCP to port forwarding, but that didn't bring any change
Have Macs and iDevices. Windows PC's are over 20 years old. No great help 😉
Point is, in the past (somewhere mid of last year) eBlocker Mobile worked!
So, for the time being i refuse to give up although i don't know how yet.
Will continue to play/fool around with the White Cube. When i discover something i'll yell.
Thank you all for your efforts!
Rob
Will continue to play/fool around with the White Cube.
I would strongly recommend to refrain from this idea! This will rather turn things worse - as many many times in the past, dear Rob.
Back to the facts: Your eBlocker is not receiving the eBlocker Mobile requests (=TCP/IP packages) as @bpr found out. So the source of issue must be somewhere else.
Real world example: Imagine you are expecting a package by postal mail. Would you look at home („fooling around“ everywhere) if the package does not arrive and the postal service even did not ring the door? Probably not, as it makes no sense. Same in the IT world…
So, either the package never got send (=problem with the OpenVPN app and/or settings in iOS) or the package got blocked in transit (at the provider, at the router, at some spot in the LAN). That‘s the analytical way to follow to find the package/issue - but certainly not „fooling around“!
Unfortunately it‘s technically not that easy (or I have no idea for an easy analysis) to follow the package - especially with little tech knowledge and lacking tools on the analysis side. All I can think of (like a wireshark LAN package sniffing) is very complex and not made for regular users.
Maybe someone else has an idea? Switching to a different device, as @benne suggested, could eliminate or proof an iOS issue, for instance. Maybe invite a friend with a Windows device?
But honestly, Rob, I pledge you not to change anything on the eBlocker. This will not help solving the issue but rather result in lot‘s of time spend in support for debugging misconfigurations again. We had this experience many times already.
THX!
This will rather turn things worse
The worst-case scenario would be that i remove my White Cube from my network.
1. Instead of using words like "fooling around", i should have expressed myself more precise. What i will do is experiment with the network-components i have within the playing field of my limited knowledge and knowing that i would be 'walking on thin ice'.
2. I have received the best possible support anyone can hope for where hard- or software is concerned. Again, thank you for that support. But for the topic at hand, i will not claim more of your time unless it is to let you know the issue is solved.
3. When i exceed the borders of the 'playing field' i run the risk of messing things up. In such a situation i will not try to get help on this forum as well; to bad for me that i took that risk. And although it might be 'cursing in the church' on this forum, i always have the option to unplug the eBlocker and try to live without it. Hard as that may be 😏
So, as i don't want to stretch your patience with me again, i propose to close this topic at least for the time being. Thanks again.
Rob
Beleef it or not; fortune favors the foolish.
Removed PortSharingSettings from FRITZ!Box and added new settings for UDP only. Testing by eBlocker resulted in Success. Removed profile in OpenVPN app, made new profile for iPad (iOS) and imported it in OpenVPN app. Maybe touched something somewhere without knowing/realizing, but...
eBlocker Mobile works on the iPad, via FRITZ!Box's WiFi (i know, i know) and via iPhone's G4.
Until now i can't repeat the same 'trick' for my iPhone, but i'll keep trying 🤨
Rob
@robfranssen-fr
do you have set any filter for UDP in your FritzBox?
Have your clients and eBlocker full access to the internet?
Your VPN config ist with IP not with an Hostname?
regards
PIO78
@pio78 Thank you for sharing your ideas about this topic.
Frankly, i never have seen an option to set UDP-filters in my FRITZ!Box 7590. I only opened the port 1194 as shown below.
I am the only user of all the network-gadgets with full Admin-access.
To my knowledge, the VPN-config is provided by eBlocker and can't be changed by me; or did i get your question wrong.
In the meantime, not only my iPad works when connected by WiFi to the hotspot of my iPhone SE (1st version), but an old iPhone 4S works fine (but slow) in the same way.
I still didn't manage to connect the iPhone SE with the internet using it's own 4G capabilities and while using the OpenVPN app.
Rob
In the meantime, not only my iPad works when connected by WiFi to the hotspot of my iPhone SE (1st version), but an old iPhone 4S works fine (but slow) in the same way.
I‘m not sure if I‘m on the same page.🤔
Are you saying eBlocker Mobile is working (connecting to VPN properly) on iPad when connected to Wifi?
THX!
@random My iPad is WiFi only and my iPhone 4S has an old SIM card without data contract. But in both cases i can connect their WiFi with the hotspot of my iPhone SE and connect to internet using the OpenVPN app. In both these cases i do not only see the eBlocker ControlBar in opened webpages, but also the lines with "SSL Handshake" and "Session is ACTIVE" in the log of OpenVPN.
I therefore tend to believe eBlocker Mobile works correct when connected to the hotspot of my SE instead of being connected to the FRITZ!Box.
At the same time i said that i can establish a VPN connection with the OpenVPN app WHILE BEING CONNECTED to the FRITZ!Box-router. Although such a VPN doesn't make sense, it is possible and also in this case i can find the lines with "SSL Handshake" and "Session is ACTIVE" in the log of OpenVPN.
Rob
@robfranssen-fr Sorry, I‘m still mixed up. Here is what I understand:
eBlocker Mobile works ✅ if setup iOS Device -> WLAN -> Mobile Phone Thethering Hotspot ->4G/5G/LTE Internet-> Fritzbox -> eBlocker at Home
eBlocker Mobile does not work ❌ if setup iOS Device -> 4G/5G/LTE
And I understand these are not the same devices. Right?
Have you checked if the ❌ device is enabled for eBlocker Mobil at all: Settings > Devices > „Select Device“ - enable eBlocker Mobile (maybe also disable and re-enable again)
One thought regarding your fritzbox: Make sure all FritzVPN services (to access your LAN from the Internet) are disabled. This might interfere with eBlocker Mobile.
To sum up: eBlocker Mobile works in some case. So your eBlocker Mobile setup is generally correct. However the normal use case via 4G does not work. Therefore I can only conclude your 4G mobile carrier might not be passing VPN traffic (anymore). Have you changed carriers or plans recently?
THX!
I‘m still mixed up.
That makes two of us! 😏
iPad's WiFi -> OpenVPN + eBlocker's Profile (VPN) -> iPhone SE's Personal Hotspot (WiFi) -> iPhone SE's 4G -> Internet. Works fine
iPhone 4S's WiFi -> OpenVPN + eBlocker's Profile (VPN) -> iPhone SE's Personal Hotspot (WiFi) -> iPhone SE's 4G -> Internet. Works fine
iPhone's 4G -> OpenVPN + eBlocker's Profile (VPN) -> Internet (normal situation). Does not work 😡
On the large screen of my iMac i opened 2 sessions of eBlocker Settings (1x iPad and 1x iPhone) and compared all settings of both devices, including the ones you showed in you last post. Couldn't find a difference. Ran trough settings of iPhone SE 'a million times', couldn't find anything. Removed and reinstalled eBlocker's profile and OpenVPN app several times.
Didn't change ISP since nov. 2020 and used the same router ever since. Never had any problem setting up a VPN with other VPN-services such as Private Internet Access (from which i use the .ovpn-files in eBlocker/Settings/IP-Anonymization/VPN NETWORK).
I must assume that it is some 'stupid' setting i made myself, not necessarily in the eBlocker. Driving me nuts 🙃
Can you please let me know what you mean by "Make sure all FritzVPN services"?
Rob
Can you please let me know what you mean by "Make sure all FritzVPN services"?
As two devices are working, this shows the fritzbox is working properly too. So my thought with the fritzboxVPN not relevant/obsolet. Never mind.
The cause must be somehow connected to the device that‘s not working. Different iOS version maybe - with some strange settings, some other VPN or Apple Private Relay etc?
I remember last time some „issues with eBlocker“ started you had „changed nothing“, but updated all the device‘s OSs to the latest versions (which is a major change btw.😉).
THX!
Never mind.
I don't 🙂
iPad = iPadOS 15.2.1, iPhone SE = iOS 15.2.1, iPhone 4S = iOS 9.3.6
Apple Private Relay: iPad = OFF, iPhone SE = OFF, iPhone 4S = non-existent
All VPNs used in the past removed from iPhone SE (no remains visible anywhere)
In cases like this i tend to believe in miracles. So, sooner or later one will happen 🤨
Thanks for your (moral) support.
Rob
@random Solved; no miracle though.
Rebooted the eBlocker; the iPhone-Rob (SE) was still (lower down) in the device-list of the eBlocker and was shown as Enabled (green switch). However at the top of the device-list there was a new Apple-device, also (!) shown as being Enabled. Verification of it's IP-address showed that this was the same iPhone-Rob (SE). REFRESHing the device-list didn't bring any change.
Then EDITed the device-list and removed the original device shown as iPhone-Rob. I then renamed the device on top of the list from Apple-something (don't remember the exact name) into iPhone-Rob.
After this exercise the iPhone-Rob (AKA iPhone SE) had no problem connection to the 4G-grid using the OpenVPN-app. In the screenshot of the iPhone SE below you see the NRC-site and on top of it the 4G-sign, the VPN-logo and, last but not least, the eBlocker ControllBar.
Error iPhone? Error eBlocker? Don't know. What i can add to this however is the following: Before i executed above exercise, i saw an exclamation mark more often and until the exercise for 'DNS Firewall' in the Dashboard's Function test. EMPTYing DNS CACHE in eBlocker's Settings and emptying Safari's cache didn't help. After the exercise however, ALL lights are green again in the Function test. (unfortunately i can't tell WHEN the above exclamation mark started appearing)
Rob
the iPhone-Rob (SE) was still (lower down) in the device-list of the eBlocker and was shown as Enabled (green switch). However at the top of the device-list there was a new Apple-device, also (!) shown as being Enabled.
So I understand the same devices was shown twice at eBlocker Settings -> Devices, right?
This can occur only if the MAC address (network‘s adapter address) of the devices has changed. Apple probably reset it’s MAC address changing feature after an iOS update (see https://eblocker.org/community/announcements/ios-14-important-configuation-necessary/#post-2004 ).
REFRESHing the device-list didn't bring any change.
Did you also rescan/rediscover the devices (see screenshot) or just hit Refresh-Button (in Settings->Devices)?
Then you removed the device shown to be inactive (greyed out) but not the one on top with the Star icon (btw. the star indicates your current device being used to access the Settings), right?
Then you just renamed the „star“ device, not making any other changes?
Do you say that eBlocker Mobile was enabled already for the „star“ devices and you did not change this either?
Last question: Which eBlocker Mobile OpenVPN profile has been installed on the „star“ device? Could it be, that the profile of the „greyed out“ (later removed) device was taken for installation and not the profile from the active (star) device?
If you made screenshots of the „double devices“ detail view (where the MAC address is shown) this would be really helpful - same as other screenshot you might have made (say from the device overview showing the „same devices“ etc). No matter if you find an old screenshot. Please share.
THX!
the same devices was shown twice
Correct
Apple probably reset it’s MAC address changing feature after an iOS update
Does the Easy fix "Disable the option "Private Address"" also/still apply for iOS 15?
or just hit Refresh-Button (in Settings->Devices)?
That's the one
Then you removed the device shown to be inactive (greyed out) but not the one on top with the Star icon (btw. the star indicates your current device being used to access the Settings), right?
None of the devices shown was greyed out; the old iPhone-Rob and the new 'Apple-something' were both shown as active with the switch at the very left side of the Devices-screen toggled to the ON-position (colored green)
I removed the one with the (old) name iPhone-Rob. I kept the one on top of the list, starred to show the current device, showing the name 'Apple-something' and apparently the 'new' device discovered by eBlocker. I then renamed this device on top of the list from 'Apple-something' to iPhone-Rob to 'restore' the familiar picture of the device list. Made no other changes.
Do you say that eBlocker Mobile was enabled already for the „star“
After renaming the 'newly-found' to iPhone-Rob, i simply disabled WiFi on the iPhone-Rob and connected to 4G using the OpenVPN app strait away. No further changes or fuss. Bang, the connection worked!
Which eBlocker Mobile OpenVPN profile has been installed on the „star“ device?
I was so anxious to know, that i completely forgot about the profile. So the connection was made with the profile of the 'old' iPhone-Rob
If you made screenshots
This should read "If you had made screenshots". I know, i should have made more screenshots during the process. But as i mentioned before, this 'thing' was driving me nuts and maybe i was just a bit to eager to get it solved. Will try to do better next time. And as i try to clean up after moving around, there are only a very few pictures in Photos, none of them concerning eBlocker. 😞
I tried to answer your questions as good as possible from memory; hope they help for future cases.
Rob