SOLVED: I being a noob, did a trivial mistake of selecting no logging and hence no data was displayed in dashboard. Selected everything under Privacy tab of Settings. Issue solved. So, OpenVPN through 443 and pihole together working great. Thanks RamSet.
cat /etc/dhcpcd.conf
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel
# Inform the DHCP server of our hostname for DDNS.
hostname
# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
duid
# Persist interface configuration when dhcpcd exits.
persistent
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
interface tun0
static ip_address=10.8.0.1/24
static routers=XX.XXX.XX.3
static domain_name_servers=127.0.0.1
This is wrong ; it should be XX.XXX.XX.3 ; this is my vps ip.
The setup is pi-hole and openvpn running on a ubuntu vps.
Kindly advise.
UPDATE:
I have activated DHCP server on pihole and the page for Block Ads! ; says adblocking activated. Although the dashboard page says 0 queries and the Network Overview has two entries for XX.XXX.XX.1 instead of XX.XXX.XX.3
MORE INFO:
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:XX:XX:20:04:Xb brd ff:ff:ff:ff:ff:ff
inet XX.XXXXX.3/26 brd XX.XXX.XX.63 scope global eth0
valid_lft forever preferred_lft forever
inet6 2a01:9723:1:ff45::9aXc/64 scope global
valid_lft forever preferred_lft forever
inet6 fe8a::9e5b:617f:baca:d8X9/64 scope link
valid_lft forever preferred_lft forever
4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 100
link/none
inet 10.8.0.1/24 brd 10.8.0.255 scope global tun0
valid_lft forever preferred_lft forever
inet6 fe80::aae9:c9f4:bf98:9412/64 scope link stable-privacy
valid_lft forever preferred_lft forever
You should start seeing clients in the dashboard as Devicename.vpn or the VPN IP ...
Try hitting a known ad server domain like http://flurry.com ... that should show up in the dashoboard (and not load on your device).
Jun 4 23:06:20 dnsmasq[645]: query[A] flurry.com from 10.8.0.2
Jun 4 23:06:20 dnsmasq[645]: /etc/pihole/gravity.list flurry.com is 0.0.0.0
Jun 4 23:06:20 dnsmasq[645]: query[A] flurry.com from 10.8.0.2
Jun 4 23:06:20 dnsmasq[645]: /etc/pihole/gravity.list flurry.com is 0.0.0.0
Jun 4 23:06:20 dnsmasq[645]: query[A] flurry.com from 10.8.0.2
Jun 4 23:06:20 dnsmasq[645]: /etc/pihole/gravity.list flurry.com is 0.0.0.0
Does not load on device, but also not shown on dashboard. Query log is also empty.
Openvpn is connected for more than 24 hrs and browsing was done, but no joy on dashboard.
The FTL logs are empty whereas the pihole logs are being written. Understand that since FTL logs are empty , hence dashboard is empty.
Solved: I being a noob, did a trivial mistake of selecting no logging and hence no data was displayed in dashboard. Issue solved. So, OpenVPN through 443 and pihole together working great. Thanks RamSet.
but it's not gonna work ...