What can I do? Today, as often before, I wanted to establish with OpenVPN app on iOS an eBlocker mobile connection to my eBlocker at home. But the connection has not being established. Now I am back at home. How can I find, what ist the reason for this problem. And how can I solve it?
@facebita In case you are using eBlocker‘s DynDNS demo server, you might have been affected by a downtime we had yesterday (see https://eblocker.org/community/main-forum/eblocker-mobile-stopped-working/ )
If you rely on eBlocker Mobile I‘d suggest to use a commercial DynDNS service as eBlocker‘s service is for demo/testing purposes only.
THX!
I assess, the downtime is not the reason for my problem, due it persists since at least sunday. Is there anywhere a logfile or some other way in order to check, where it stucks. My eBlocker itself at selfcheck finds no problems.
@facebita Please share the OpenVPN logfile from your IOS client: In the upper right corner of the official OpenVPN app there is an icon which looks like a text roll with "< >" in the center.
THX!
Here it is (see below). I've anonymized tls-cipher and the subdomain in .home.eblocker.com. Thanks in advance for your support!
2021-12-01 10:54:16 ----- OpenVPN Start -----
OpenVPN core 3.git::58b92569 ios arm64 64-bit
2021-12-01 10:54:16 OpenVPN core 3.git::58b92569 ios arm64 64-bit
2021-12-01 10:54:16 Frame=512/2048/512 mssfix-ctrl=1250
2021-12-01 10:54:16 UNUSED OPTIONS
4 [resolv-retry] [infinite]
5 [nobind]
6 [persist-key]
11 [tls-cipher] [XXX]
13 [verb] [1]
15 [script-security] [2]
16 [down] [/etc/openvpn/update-resolv-conf]
17 [up] [/etc/openvpn/update-resolv-conf]
2021-12-01 10:54:16 EVENT: RESOLVE
2021-12-01 10:54:16 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:16 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:19 EVENT: RECONNECTING
2021-12-01 10:54:19 EVENT: RESOLVE
2021-12-01 10:54:19 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:19 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:21 EVENT: RECONNECTING
2021-12-01 10:54:21 EVENT: RESOLVE
2021-12-01 10:54:21 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:21 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:23 EVENT: RECONNECTING
2021-12-01 10:54:23 EVENT: RESOLVE
2021-12-01 10:54:23 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:23 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:25 EVENT: RECONNECTING
2021-12-01 10:54:25 EVENT: RESOLVE
2021-12-01 10:54:25 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:25 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:27 EVENT: RECONNECTING
2021-12-01 10:54:27 EVENT: RESOLVE
2021-12-01 10:54:27 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:27 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:29 EVENT: RECONNECTING
2021-12-01 10:54:29 EVENT: RESOLVE
2021-12-01 10:54:29 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:29 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:31 EVENT: RECONNECTING
2021-12-01 10:54:31 EVENT: RESOLVE
2021-12-01 10:54:31 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:31 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:33 EVENT: RECONNECTING
2021-12-01 10:54:33 EVENT: RESOLVE
2021-12-01 10:54:33 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:33 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:35 EVENT: RECONNECTING
2021-12-01 10:54:35 EVENT: RESOLVE
2021-12-01 10:54:35 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:35 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:37 EVENT: RECONNECTING
2021-12-01 10:54:37 EVENT: RESOLVE
2021-12-01 10:54:37 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:37 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:39 EVENT: RECONNECTING
2021-12-01 10:54:39 EVENT: RESOLVE
2021-12-01 10:54:39 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:39 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:42 EVENT: RECONNECTING
2021-12-01 10:54:42 EVENT: RESOLVE
2021-12-01 10:54:42 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:42 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:44 EVENT: RECONNECTING
2021-12-01 10:54:44 EVENT: RESOLVE
2021-12-01 10:54:44 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:44 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:46 EVENT: RECONNECTING
2021-12-01 10:54:46 EVENT: RESOLVE
2021-12-01 10:54:46 Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
2021-12-01 10:54:46 Client terminated, restarting in 2000 ms...
2021-12-01 10:54:48 EVENT: CONNECTION_TIMEOUT [ERR]
2021-12-01 10:54:48 Raw stats on disconnect:
RESOLVE_ERROR : 15
CONNECTION_TIMEOUT : 1
N_RECONNECT : 14
2021-12-01 10:54:48 Performance stats on disconnect:
CPU usage (microseconds): 80490
Network bytes per CPU second: 0
Tunnel bytes per CPU second: 0
2021-12-01 10:54:48 EVENT: DISCONNECTED
2021-12-01 10:54:48 Raw stats on disconnect:
RESOLVE_ERROR : 15
CONNECTION_TIMEOUT : 1
N_RECONNECT : 14
2021-12-01 10:54:48 Performance stats on disconnect:
CPU usage (microseconds): 91638
Network bytes per CPU second: 0
Tunnel bytes per CPU second: 0
Transport Error: DNS resolve error on 'xxx.home.eblocker.com' for UDP session: DNS/RRset does not exist
The problem is clear: DnyDNS is not resolving. Are you sure this has worked recently?
Background: I wonder about the domain name you are using. To my knowledge all eblocker.com addresses have been phased out over a year ago 🤔
To solve, either use a commercial DynDNS service or reset eBlocker Mobile and start all over (re-installing the OpenVPN config in your client). This will set a domain name that resolves properly.
THX!
Are you sure this has worked recently?
Yes. It had been worked properly for approximately one year and until approximately midth of last week. I have used eBlocker only in times of eblocker.org (UG), but never in times of former bankrupted GmbH.
@facebita I just checked back - and you are right: home.eblocker.com addresses are still in use for eBlocker Mobile. I was wrong in this case.
To move forward two suggestions:
- Disable eBlocker Mobile (via the eBlocker Settings) and re-enable it. This will force your current IP-address to be sent to the eBlocker Demo server. Maybe this solves the issue already.
- As I suggested you could try to generate a new OpenVPN file by running the eBlocker Mobile Wizard again - and re-installing the config in your client.
If none of the suggestions work, please share the full domain name (not just xxx) so we can look it up in the DNS server to see what might be going wrong.
In case you are relying on eBlocker Mobile I highly suggest using a commercial DnyDNS and not the eBlocker server meant for demonstration purposes only.
THX!
I did step 1 and step 2 as suggested. No success.
I think there is something wrong with the interaction between eBlocker and Fritzbox 7490, FritzOS 7.29. I have Fritzbox configured as described here: https://eblocker.github.io/help/de/360007395294.html
As mentioned before on myeblockers_ip_address/settings/#!/mobile I can run the test. And eBlocker confirms the test as being passed.
But, as already said, no connection can being established.
Here is the full address of the domain whereunder my VPN should can be connected:
http://b5q9dcok9evngn3560vlhk76o9fvmekn30pjbg2b9vllj53k3it0.home.eblocker.com/
I could find a log entry on the server that shows your dynamic hostname was added yesterday at 21:08.
The eBlocker should update the hostname every 5 minutes, otherwise it expires after 4 hours.
So I assume the process on your eBlocker that updates the hostname has crashed or the eBlocker has problems connecting to our server.
Have you tried restarting the eBlocker?
If that does not help, please send a diagnostics report (Settings>System>Diagnosis) to "support at eBlocker.org".
"support at eBlocker.org"
I did it. But I received an automated respond, that the team would not answer my email - unless »in other cases«. So, I will hope, my case is an »other case«.
Thank you for the diagnostics report. Unfortunately, everything seems to be OK in the eBlocker log files, so I can't find a reason for the missing IP address updates.
In the server's logs the updates for your hostname stopped at 29th November 18:52. Since there are no corresponding error messages in eBlocker's logs, I can only assume that the eBlocker Mobile configuration is somehow broken.
Could you try the following:
- Go to Settings / eBlocker Mobile
- Switch eBlocker Mobile off
- Click the "Edit Settings" button
- Click through the wizard, keeping all settings the same
- (You have to check the box "I have mapped the ports on my router")
- Do the connection test during the wizard (should be successful)
- At the end eBlocker Mobile should be enabled again
Maybe it helps that the configuration has now been written to the database again.
Thanks!
And today obviously the same - or at least a very similar - problem has accured again. Neither my iPhone nor my Mac are being able to establish a VPN connection to my eBlocker. Unfortunately I am away from home, so that I am unable to follow your instructions given at December, 12th.
So, hopefully somebody at home can plug off my eBlocker and plug it in then again. And hopefully this will urge the eBlocker to provide again a performing eBlocker mobile function.
@facebita Well, based on facts we love to hear where to improve. Today we have no hard evidence that eBlocker Mobile is causing any issues…
Maybe your home Internet connection is down, your DynDNS provider has issues or such.
We are happy to check your OpenVPN log for evidence whats going on. But please understand that constantly blaming eBlocker with no reason will have exactly one effect: we just ignore your posts… At least that‘s my personal conclusion.
THX!
You maybe need to consider that eBlocker is run by volunteers only. Volunteers are highly motivated to listen and improve, if the user is polite, answers the questions asked and brings in facts that can be verified to drill down the cause of error.
For example, I'm still waiting for your answer to drill down: https://eblocker.org/community/bugs-features/eblocker-mobile-has-stopped-working-properly/#post-5557
Actually, I'm not sure what you are trying to achieve with sentences like "hopefully this will urge the eBlocker to provide again a performing eBlocker mobile function." without bringing any facts to the table.
Personally I fear with this kind of communication you are loosing the support of everyone in the volunteer team - including myself. So you might want to rethink your communication strategy if you are looking for help or want to contribute to improve eBlocker.
Last: Based on facts you are currently the only user who has issues with eBlocker Mobile - among hundreds of daily users. And I'm sure we can find the cause of your individual issues if you are motivating the team with facts rather than assaulting it...
Appologies taken 🤝👍
Please understand that the more info you share, the easier we can investigate. To get an idea about the info we need to help efficiently, you maybe find this useful: https://eblocker.org/community/announcements/before-posting-here-please-read/#post-117
Of course some issues can be solved by question & answer as well, but this takes much more time and is less motivating for everyone… That‘s why a brief „eBlocker Mobile is not working“ is not quite the best to motivation 😉
Nevertheless we appreciate any feedback to constantly learn and improve!
Thanks much for your feedback and for using eBlocker 🙏
@facebita If you share your OpenVPN log, I‘m happy to look into it to check what‘s going on.
THX!
My troubles persist. I have set up the eBlocker mobile configuration of my eBlocker from the scratch. Beforehand, I checked that all the settings on the Fritzbox were correct.
At last step of the configuration procedure on eBlocker I have ran the eBlocker mobile test. eBlocker told me everything would be fine: eBlocker mobile could being connected from internet.
So, then I have deleted the old certificate in OpenVPN on my iPhone (iOS 15.4), have deinstalled OpenVPN, have rebooted the iPhone, have reinstalled OpenVPN and via eBlocker dashboard performed the installation procedure for the certificate. Then I have rebooted the iPhone again, switched off WLAN an have connected via cellular network. At last I have tried to switch on the VPN. But it failed. The logfile of OpenVPN is here:
https://www.glombit.de/index.php/s/SQY5pGy8of7DKoX
Same procedure at macOS, there as well I have reinstalled the VPN client in Tunnelblick.app from the scratch. But no data is transferred, and no connection will being established.
I have also made a diagnostic report of the eBlocker which you can download here:
https://www.glombit.de/index.php/s/N5frL4ejKrMqsip
And here are some additional information:
- Hardware you use for running eBlockerOS: Raspberry Pi 4 8 GB
- eBlockerOS version as well as filter lists version: 2.8.2, current filter lists
- eBlocker network mode (auto, individual or expert): individual
- eBlocker network settings (IP, mask, gateway): Don't know exactly. I followed the configuration recommendations for an eBlocker that is operated on a Fritzbox 7490.
- Which devices runs DHCP server? Router/external, eBlocker or client fixed IP?: eBlocker
- IPv6 disabled for client/network?: Yes
- eBlocker DNS firewall settings: I think, I did not have changed the default settings.
- Client network settings (IP, mask, DNS, gateway)
- Whether eBlocker’s https integration is enabled for client: Yes
- Client browser and OS version (i.e. FireFox 80.1 running on macOS 13.4): iOS 15.4, macOS 11.6.5, latest version of Firefox
- Additional non default Blockers enabled? (like DuckDuckGo, Consent-Blocker, custom lists etc.)
- HTTPS Auto Trust App enabled?: Nothing
- Exact way or a link / screenshot to reproduce the issue: see above
- If VPN or Tor is enabled for the client in eBlocker (and which VPN provider you are using): eBocler mobile is enabled, Tor isn't
- Are automatic updates enabled?: Yes
- Please use a meaningful title & description other users with same issue would enter as search term: hopefully I did
@facebita Thanks for the info. The link above to the Openvpn log results in:
Actually we do not recommend to share the Diagnosis Report publicly as it might contain private data (see the README). If we need the Report, we will ask for it. For now, the OpenVPN log and the info above (thanks very much for it) is sufficient.
One additional question: Are you trying to connect to your home eBlocker from a company‘s LAN? If so, this might be the reason for your issues as company admins sometimes block OpenVPN. You should rather try to connect via a fully open Internet connection (say via your 4G/5G provider).
THX!
@facebita Thanks for the info. The link above to the Openvpn log results in:
Sorry. There was an update. But now it should work again.
If we need the Report, we will ask for it.
Okay. I have inactivated the link.
Are you trying to connect to your home eBlocker from a company‘s LAN?
I have tried to connect via company WLAN. Now, with macOS, it has failed. But in the past this has worked properly.
You should rather try to connect via a fully open Internet connection (say via your 4G/5G provider).
Yes. This is the approach when I am trying to establish a connection with my iPhone to the eBlocker VPN. And this, as well, has worked in the past, but no longer for now.
Since yesterday there are problems with eBlocker Mobile on my eBlocker. I can‘t connect with eBlocker with all my devices. Without eBlocker mobile in the Home Network everything is all fine. I‘ve made no changes on the setting.
the OVPN App Protocol on iphone says this:
2022-03-25 15:48:48 1
2022-03-25 15:48:48 ----- OpenVPN Start -----
OpenVPN core 3.git::58b92569 ios arm64 64-bit
2022-03-25 15:48:48 OpenVPN core 3.git::58b92569 ios arm64 64-bit
2022-03-25 15:48:48 Frame=512/2048/512 mssfix-ctrl=1250
2022-03-25 15:48:48 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-03-25 15:48:48 EVENT: RESOLVE
2022-03-25 15:48:48 Transport Error: DNS resolve error on 'vqm39ep56n13d2d47evkk7j6m7opuicrk0voosgb3usva5k8onsg.home.eblocker.com' for UDP session: DNS/RRset does not exist
2022-03-25 15:48:48 Client terminated, restarting in 2000 ms...
2022-03-25 15:48:50 EVENT: RECONNECTING
2022-03-25 15:48:50 EVENT: RESOLVE
2022-03-25 15:48:50 Transport Error: DNS resolve error on 'vqm39ep56n13d2d47evkk7j6m7opuicrk0voosgb3usva5k8onsg.home.eblocker.com' for UDP session: DNS/RRset does not exist
2022-03-25 15:48:50 Client terminated, restarting in 2000 ms...
2022-03-25 15:48:52 EVENT: RECONNECTING
2022-03-25 15:48:52 EVENT: RESOLVE
2022-03-25 15:48:53 Transport Error: DNS resolve error on 'vqm39ep56n13d2d47evkk7j6m7opuicrk0voosgb3usva5k8onsg.home.eblocker.com' for UDP session: DNS/RRset does not exist
2022-03-25 15:48:53 Client terminated, restarting in 2000 ms...
2022-03-25 15:48:55 EVENT: RECONNECTING
2022-03-25 15:48:55 EVENT: RESOLVE
2022-03-25 15:48:55 Transport Error: DNS resolve error on 'vqm39ep56n13d2d47evkk7j6m7opuicrk0voosgb3usva5k8onsg.home.eblocker.com' for UDP session: DNS/RRset does not exist
2022-03-25 15:48:55 Client terminated, restarting in 2000 ms...
2022-03-25 15:48:57 EVENT: RECONNECTING
2022-03-25 15:48:57 EVENT: RESOLVE
2022-03-25 15:48:57 Transport Error: DNS resolve error on 'vqm39ep56n13d2d47evkk7j6m7opuicrk0voosgb3usva5k8onsg.home.eblocker.com' for UDP session: DNS/RRset does not exist
2022-03-25 15:48:57 Client terminated, restarting in 2000 ms...
2022-03-25 15:48:59 EVENT: RECONNECTING
2022-03-25 15:48:59 EVENT: RESOLVE
2022-03-25 15:48:59 Transport Error: DNS resolve error on 'vqm39ep56n13d2d47evkk7j6m7opuicrk0voosgb3usva5k8onsg.home.eblocker.com' for UDP session: DNS/RRset does not exist
2022-03-25 15:48:59 Client terminated, restarting in 2000 ms...
2022-03-25 15:49:01 EVENT: RECONNECTING
2022-03-25 15:49:01 EVENT: RESOLVE
2022-03-25 15:49:01 Transport Error: DNS resolve error on 'vqm39ep56n13d2d47evkk7j6m7opuicrk0voosgb3usva5k8onsg.home.eblocker.com' for UDP session: DNS/RRset does not exist
2022-03-25 15:49:01 Client terminated, restarting in 2000 ms...
2022-03-25 15:49:03 EVENT: RECONNECTING
2022-03-25 15:49:03 EVENT: RESOLVE
2022-03-25 15:49:03 Transport Error: DNS resolve error on 'vqm39ep56n13d2d47evkk7j6m7opuicrk0voosgb3usva5k8onsg.home.eblocker.com' for UDP session: DNS/RRset does not exist
2022-03-25 15:49:03 Client terminated, restarting in 2000 ms...
2022-03-25 15:49:05 EVENT: DISCONNECTED
2022-03-25 15:49:05 Raw stats on disconnect:
RESOLVE_ERROR : 8
N_RECONNECT : 7
2022-03-25 15:49:05 Performance stats on disconnect:
CPU usage (microseconds): 46109
Network bytes per CPU second: 0
Tunnel bytes per CPU second: 0
@simon I've joined your post as it's the same issue.
@facebita @simon It seems the eBlocker DNS test server has issues resolving. This is beyond my scope but @bpr will probably take care of it asap.
Again I repeat of what has been said many times (see above):
If you rely on eBlocker Mobile I‘d suggest to use a commercial DynDNS service as eBlocker‘s service is for demo/testing purposes only.
If you don't follow the recommendation, you need to live with occasional outages/downtimes!
THX!