Hello,
I am looking for help/hints as to solving the following issue:
Since some time last week (coinciding with 3.1 update?) I cannot reach local network resources any more while using eBlocker mobile. This worked flawlessly before.
The error message of the web browser is:
err_connection_refused
A ping to local network resources (e. g. 192.168.178.1) yields
destination port unreachable
Apart from accessing local network devices eBlocker mobile works.
Whereas when using Android’s builtin VPN functionality web browser connection and ping work as expected.
Settings option
Remote device may access resources in local network
is checked.
Best regards, jo
- eBlocker network mode: expert
- eBlocker network settings: IP: 192.168.178.77, mask: 255.255.255.0, gateway: 192.168.178.1
- Which devices runs DHCP server: eBlocker
- IPv6 disabled: yes
- eBlocker DNS firewall settings: use eBlocker as DNS server
- Client network settings: IP: e.g. 192.168.178.201, mask:255.255.255.0, DNS: 192.168.178.77, gateway: 192.168.178.77
- Whether eBlocker’s https integration is enabled for client: no
- Client browser and OS version: Vanadium 123.0.6312.80 on GrapheneOS, Android 14
- Additional non default Blockers enabled? (like DuckDuckGo, Consent-Blocker, custom lists etc.): ?
- HTTPS Auto Trust App enabled: yes
- Exact way or a link / screenshot to reproduce the issue: ?
- If VPN or Tor is enabled for the client in eBlocker (and which VPN provider you are using): no
- Are automatic updates enabled: yes
Hi @cerise,
I just tested eBlocker Mobile with my Android 14 device and it worked. I used the OpenVPN app.
I am not sure what you mean by "builtin VPN functionality":
Whereas when using Android’s builtin VPN functionality web browser connection and ping work as expected.
I assume this does not use OpenVPN and does not connect to eBlocker?
@bpr Thanks very much for checking. I didn't have the time for verification earlier. 😢
@cerise Now, I've just double checked: I can also access my internal resources using OpenVPN and eBlocker Mobile. So I doubt it's a general issue related to 3.1.
Next to the questions asked by @bpr: How are you accessing the internal resource? By it's IPv4 address or by domain name? If it's the latter: who serves as the DNS server for internal resources (or is this via /etc/hosts)?
In any case: please verify if you can reach the internal resource by it's IP address.
THX!
Just discovered:
When toggling the eBlocker settings switch 'Remote device may access resources in local network' I get the following error message: 'Error while setting access to local network'.
@cerise In that case: could you create a diagnostics report at Settings / System / Diagnostics and send at least the file "eblocker-system.log" to support(AT)eblocker.org?
Thanks!
OK, thanks for the log file. I am looking into it.
In the meantime: could you reboot the eBlocker and check, whether you can now toggle the switch "Remote device may access resources in local network"?
reboot the eBlocker
solved my issue!
Before the reboot I saw that 'Doctor diagnosis' didn’t show any results: '…is created…'
After rebooting 'Doctor diagnosis' works again and warns about system update being older than two days (2024-03-27). Does automatic update not work?
Toggling of the
switch "Remote device may access resources in local network"
works without error messages now.
And access to my local network via OpenVPN and eBlocker Mobile works, too.
Great, thank you!
@cerise Glad the reboot did the trick 👍 "Every boot does good" IT people say 😉
Does automatic update not work?
Automatic updates work very well and without any interruption in 2024.
If you are not getting auto updates please try to re-enter your license key under Settings> License & Update> Activate New License button. All your settings will stay in place - but a settings backup is always a good idea anyhow. 😉
THX!
Re-entered license key and automatically received an update this morning 👍
Thank you!