# Admin page shows FTL Offline | Unable to start, cannot access dhcp.leases

**URL:** <https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129>\
**Category:** Help\
**Created:** [November 1, 2018, 7:29am UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129 "2018-11-01T07:29:26Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![onyxblack](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/o/f19dbf/32.png) [@onyxblack](https://discourse.pi-hole.net/u/onyxblack)\
**Post date:** [November 1, 2018, 7:29am UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/1 "2018-11-01T07:29:26Z")

</div>

#### Please follow the below template, it will help us to help you!

## Expected Behaviour:

When running SSH `sudo service pihole-FTL restart`  
the FTL should show as 'FTL Active' or 'FTL Online' in the admin dashboard

## Actual Behaviour:

When running SSH `sudo service pihole-FTL restart`  
SSH shows:  
Stopped  
chown: cannot access '/etc/pihole/dhcp.lease' : No such file or directory  
FTL Started!  
Admin page shows 'FTL Offline'

Running on LG G7 via 'Linux Deploy' & Debian

## Debug Token:

vdadklt48x

---

<div class="post-metadata">

**Author:** ![Tntdruid](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/tntdruid/32/773_2.png) [@Tntdruid](https://discourse.pi-hole.net/u/Tntdruid)\
**Post date:** [November 1, 2018, 8:09am UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/2 "2018-11-01T08:09:39Z")

</div>

sudo touch etc/pihole/dhcp.lease  
sudo service pihole~FTL restart

---

<div class="post-metadata">

**Author:** ![onyxblack](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/o/f19dbf/32.png) [@onyxblack](https://discourse.pi-hole.net/u/onyxblack)\
**Post date:** [November 1, 2018, 1:11pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/3 "2018-11-01T13:11:01Z")

</div>

No luck

@localhost:~$ sudo touch etc/pihole/dhcp.lease  
touch: cannot touch 'etc/pihole/dhcp.lease': No such file or directory

Found a post stating that it needs a manual install; so used the following  
wget -O basic-install.sh [https://install.pi-hole.net](https://install.pi-hole.net)  
sudo bash basic-install.sh

Now doing a 'sudo service pihole-FTL restart'  
shows:  
Stopped  
FTL started!

however the admin page still shows that it is offline?

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [November 1, 2018, 4:50pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/5 "2018-11-01T16:50:06Z")

</div>

What is the output of these commands from the Pi-Hole host terminal?

`pihole status`

`echo ">stats" | nc localhost 4711`

---

<div class="post-metadata">

**Author:** ![onyxblack](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/o/f19dbf/32.png) [@onyxblack](https://discourse.pi-hole.net/u/onyxblack)\
**Post date:** [November 1, 2018, 5:06pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/6 "2018-11-01T17:06:28Z")

</div>

See below for output - looks like even though its showing offline in the admin portal - it appears to be running?

```
@localhost:~$ pihole status
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled

@localhost:~$ echo ">stats" | nc localhost 4711
domains_being_blocked 126334
dns_queries_today 464
ads_blocked_today 215
ads_percentage_today 46.336208
unique_domains 105
queries_forwarded 157
queries_cached 92
clients_ever_seen 4
unique_clients 4
dns_queries_all_types 685
reply_NODATA 9
reply_NXDOMAIN 68
reply_CNAME 69
reply_IP 274
status enabled
---EOM---

```

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [November 1, 2018, 5:14pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/7 "2018-11-01T17:14:38Z")

</div>

> [@onyxblack](#):
>
> even though its showing offline in the admin portal - it appears to be running?

Yes. Pi-Hole appears to be running and resolving DNS. When you do an internet request on a connected client (I assume there is more than one), are you seeing traffic from that client in the query log?

---

<div class="post-metadata">

**Author:** ![onyxblack](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/o/f19dbf/32.png) [@onyxblack](https://discourse.pi-hole.net/u/onyxblack)\
**Post date:** [November 1, 2018, 5:22pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/8 "2018-11-01T17:22:10Z")

</div>

thats the thing, query log appears to be stuck at 'Processing...' and I'm getting just loading symbols on the main dashboard... appears the web interface isn't able to pull the info...

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [November 1, 2018, 6:44pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/10 "2018-11-01T18:44:36Z")

</div>

Did you try refresh the browser with CTRL-F5 ?

Clear browser cache ?

Tried another browser ?

---

<div class="post-metadata">

**Author:** ![onyxblack](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/o/f19dbf/32.png) [@onyxblack](https://discourse.pi-hole.net/u/onyxblack)\
**Post date:** [November 1, 2018, 7:16pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/11 "2018-11-01T19:16:07Z")

</div>

Cleared cache, different browser, no effect.

Appears to have something to do with dnsmasq...

"Service dnsmasq status"

returns  
"-bash: service: command not found"

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [November 1, 2018, 7:18pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/12 "2018-11-01T19:18:15Z")

</div>

Firewall active ?

`sudo iptables -L -n`

EDIT: Ohw and try run repair:

`pihole -r`

Ohw 2, open another bash window and tail the logs with:

`tailf /var/log/pihole.log`

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [November 1, 2018, 7:23pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/13 "2018-11-01T19:23:20Z")

</div>

> [@onyxblack](#):
>
> “Service dnsmasq status”
> 
> returns  
> “-bash: service: command not found”

This is normal with Pi-Hole V4. The code for dnsmasq is included in pihole-FTL and dnsmasq no longer runs as a separate process.

> **[DNS resolver - Pi-hole documentation](https://docs.pi-hole.net/ftldns/dns-resolver/)**

---

<div class="post-metadata">

**Author:** ![onyxblack](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/o/f19dbf/32.png) [@onyxblack](https://discourse.pi-hole.net/u/onyxblack)\
**Post date:** [November 1, 2018, 7:25pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/14 "2018-11-01T19:25:22Z")

</div>

kk, thank you, sorry just getting into this and old posts and v's are confusing me lol

made me think dnsmasq also because this happend on install  
[https://imgur.com/jXHCiBZ](https://imgur.com/jXHCiBZ)

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [November 1, 2018, 7:29pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/15 "2018-11-01T19:29:26Z")

</div>

`sudo grep -v '#\|^$' -R /etc/dnsmasq.*`

?

Might need to edit out personal details!

---

<div class="post-metadata">

**Author:** ![onyxblack](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/o/f19dbf/32.png) [@onyxblack](https://discourse.pi-hole.net/u/onyxblack)\
**Post date:** [November 1, 2018, 7:33pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/16 "2018-11-01T19:33:26Z")

</div>

```
@localhost:/var/run/pihole$ sudo grep -v '#\|^$' -R /etc/dnsmasq.*
/etc/dnsmasq.conf:conf-dir=/etc/dnsmasq.d
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/gravity.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/black.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/local.list
/etc/dnsmasq.d/01-pihole.conf:localise-queries
/etc/dnsmasq.d/01-pihole.conf:no-resolv
/etc/dnsmasq.d/01-pihole.conf:cache-size=10000
/etc/dnsmasq.d/01-pihole.conf:log-queries=extra
/etc/dnsmasq.d/01-pihole.conf:log-facility=/var/log/pihole.log
/etc/dnsmasq.d/01-pihole.conf:local-ttl=2
/etc/dnsmasq.d/01-pihole.conf:log-async
/etc/dnsmasq.d/01-pihole.conf:server=8.8.8.8
/etc/dnsmasq.d/01-pihole.conf:server=8.8.4.4
/etc/dnsmasq.d/01-pihole.conf:interface=wlan0

```

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [November 1, 2018, 7:35pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/17 "2018-11-01T19:35:04Z")

</div>

Looks good.

Did you check firewall and tried running repair ?

> [@deHakkelaar](#):
>
> Firewall active ?
> 
> `sudo iptables -L -n`
> 
> EDIT: Ohw and try run repair:
> 
> `pihole -r`
> 
> Ohw 2, open another bash window and tail the logs with:
> 
> `tailf /var/log/pihole.log`

---

<div class="post-metadata">

**Author:** ![onyxblack](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/o/f19dbf/32.png) [@onyxblack](https://discourse.pi-hole.net/u/onyxblack)\
**Post date:** [November 1, 2018, 7:52pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/18 "2018-11-01T19:52:45Z")

</div>

sudo iptables -L -n

```
@localhost:/var/run/pihole$ sudo iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination
bw_INPUT all -- 0.0.0.0/0 0.0.0.0/0
fw_INPUT all -- 0.0.0.0/0 0.0.0.0/0

Chain FORWARD (policy ACCEPT)
target prot opt source destination
oem_fwd all -- 0.0.0.0/0 0.0.0.0/0
fw_FORWARD all -- 0.0.0.0/0 0.0.0.0/0
bw_FORWARD all -- 0.0.0.0/0 0.0.0.0/0
natctrl_FORWARD all -- 0.0.0.0/0 0.0.0.0/0

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
mark all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
voice_protection all -- 0.0.0.0/0 0.0.0.0/0
oem_out all -- 0.0.0.0/0 0.0.0.0/0
fw_OUTPUT all -- 0.0.0.0/0 0.0.0.0/0
bw_OUTPUT all -- 0.0.0.0/0 0.0.0.0/0
st_filter_OUTPUT all -- 0.0.0.0/0 0.0.0.0/0

Chain bw_FORWARD (1 references)
target prot opt source destination

Chain bw_INPUT (1 references)
target prot opt source destination
           all -- 0.0.0.0/0 0.0.0.0/0 UNKNOWN match `quota2'
           all -- 0.0.0.0/0 0.0.0.0/0 owner socket exists

Chain bw_OUTPUT (1 references)
target prot opt source destination
           all -- 0.0.0.0/0 0.0.0.0/0 UNKNOWN match `quota2'
           all -- 0.0.0.0/0 0.0.0.0/0 owner socket exists

Chain bw_costly_shared (0 references)
target prot opt source destination
bw_penalty_box all -- 0.0.0.0/0 0.0.0.0/0

Chain bw_happy_box (0 references)
target prot opt source destination

Chain bw_penalty_box (1 references)
target prot opt source destination

Chain fail (0 references)
target prot opt source destination
REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-unreachable

Chain firewall (1 references)
target prot opt source destination
mobile all -- 0.0.0.0/0 0.0.0.0/0
mobile all -- 0.0.0.0/0 0.0.0.0/0
mobile all -- 0.0.0.0/0 0.0.0.0/0
mobile all -- 0.0.0.0/0 0.0.0.0/0
mobile all -- 0.0.0.0/0 0.0.0.0/0
mobile all -- 0.0.0.0/0 0.0.0.0/0
mobile all -- 0.0.0.0/0 0.0.0.0/0
mobile all -- 0.0.0.0/0 0.0.0.0/0
mobile all -- 0.0.0.0/0 0.0.0.0/0
mobile all -- 0.0.0.0/0 0.0.0.0/0
wifi all -- 0.0.0.0/0 0.0.0.0/0
wifi all -- 0.0.0.0/0 0.0.0.0/0
wifi all -- 0.0.0.0/0 0.0.0.0/0
wifi all -- 0.0.0.0/0 0.0.0.0/0
wifi all -- 0.0.0.0/0 0.0.0.0/0
wifi all -- 0.0.0.0/0 0.0.0.0/0

Chain fw_FORWARD (1 references)
target prot opt source destination

Chain fw_INPUT (1 references)
target prot opt source destination

Chain fw_OUTPUT (1 references)
target prot opt source destination

Chain host (1 references)
target prot opt source destination
firewall all -- 0.0.0.0/0 0.0.0.0/0

Chain mark (1 references)
target prot opt source destination
host all -- 0.0.0.0/0 0.0.0.0/0

Chain mobile (10 references)
target prot opt source destination

Chain natctrl_FORWARD (1 references)
target prot opt source destination
DROP all -- 0.0.0.0/0 0.0.0.0/0

Chain natctrl_tether_counters (0 references)
target prot opt source destination

Chain oem_fwd (1 references)
target prot opt source destination

Chain oem_out (1 references)
target prot opt source destination

Chain st_filter_OUTPUT (1 references)
target prot opt source destination

Chain voice_protection (1 references)
target prot opt source destination

Chain wifi (6 references)
target prot opt source destination

```

piehole -r

```
@localhost:/var/run/pihole$ pihole -r

  [✓] Root user check

        .;;,.
        .ccccc:,.
         :cccclll:. ..,,
          :ccccclll. ;ooodc
           'ccll:;ll .oooodc
             .;cll.;;looo:.
                 .. ','.
                .',,,,,,'.
              .',,,,,,,,,,.
            .',,,,,,,,,,,,....
          ....''',,,,,,,'.......
        ......... .... .........
        .......... ..........
        .......... ..........
        ......... .... .........
          ........,,,,,,,'......
            ....',,,,,,,,,,,,.
               .',,,,,,,,,'.
                .',,,,,,'.
                  ..'''.

  [i] Existing PHP installation detected : PHP version 7.0.30-0+deb9u1
  [i] Repair option selected
  [✓] Disk space check

  [✓] Update local cache of available packages

  [✗] Checking apt-get for upgraded packages
        Kernel update detected. If the install fails, please reboot and try again

  [i] Installer Dependency checks...
  [✓] Checking for apt-utils
  [✓] Checking for dialog
  [✓] Checking for debconf
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail

  [i] Performing reconfiguration, skipping download of local repos
  [✓] Resetting repository within /etc/.pihole...
  [✓] Resetting repository within /var/www/html/admin...
  [i] Main Dependency checks...
  [✓] Checking for bc
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] Checking for dnsutils
  [✓] Checking for iputils-ping
  [✓] Checking for lsof
  [✓] Checking for netcat
  [✓] Checking for psmisc
  [✓] Checking for sudo
  [✓] Checking for unzip
  [✓] Checking for wget
  [✓] Checking for idn2
  [✓] Checking for sqlite3
  [✓] Checking for libcap2-bin
  [✓] Checking for dns-root-data
  [✓] Checking for resolvconf
  [✓] Checking for lighttpd
  [✓] Checking for php7.0-common
  [✓] Checking for php7.0-cgi
  [✓] Checking for php7.0-sqlite3

  [✓] Enabling lighttpd service to start on reboot
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Installing blocking page...
  [✓] Creating directory for blocking page, and copying files
  [✗] Backing up index.lighttpd.html
        No default index.lighttpd.html file found... not backing up

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script

  [i] FTL Checks...
  [✓] Detected ARM-hf architecture (armv7+)
  [i] Checking for existing FTL binary...
  [i] Latest FTL Binary already installed (v4.0). Confirming Checksum...
  [i] Checksum correct. No need to download!

  [✓] man pages installed and database updated
  [i] Systemd-resolved is not enabled
  [✓] Starting lighttpd service
  [✓] Enabling lighttpd service to start on reboot
  [i] Restarting services...
  [✓] Starting pihole-FTL service
  [✓] Enabling pihole-FTL service to start on reboot
  [✓] Deleting existing list cache
  [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [i] Target: raw.githubusercontent.com (hosts)
  [✓] Status: Retrieval successful

  [i] Target: mirror1.malwaredomains.com (justdomains)
  [✓] Status: Retrieval successful

  [i] Target: sysctl.org (hosts)
  [✓] Status: Retrieval successful

  [i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_tracking.txt)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_ad.txt)
  [✓] Status: Retrieval successful

  [i] Target: hosts-file.net (ad_servers.txt)
  [✓] Status: Retrieval successful

  [✓] Consolidating blocklists
  [✓] Extracting domains from blocklists
  [i] Number of domains being pulled in by gravity: 149252
  [✓] Removing duplicate domains
  [i] Number of unique domains trapped in the Event Horizon: 126334
  [i] Nothing to whitelist!
  [i] Number of regex filters: 0
  [✓] Parsing domains into hosts format
  [✓] Cleaning up stray matter

  [✓] Force-reloading DNS service
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled

  [i] The install log is located at: /etc/pihole/install.log
    Update Complete!

  Current Pi-hole version is v4.0
  Current AdminLTE version is v4.0
  Current FTL version is v4.0

```

Looks like my wife is on her phone  
[https://imgur.com/kytBTUt](https://imgur.com/kytBTUt)

Thank you for helping me out I'm completely lost at the moment lol

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [November 1, 2018, 7:58pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/19 "2018-11-01T19:58:54Z")

</div>

Can you disable the firewall for diagnosing ?  
Am not that proficient with iptables.

EDIT: it used to be simple before with 'service iptables stop' but now it seems you need something like below to do it from bash:

[https://www.linuxquestions.org/questions/debian-26/debian-stretch-iptables-and-iptables-persistent-service-start-and-stop-actions-no-longer-supported-4175622528/#post5817141](https://www.linuxquestions.org/questions/debian-26/debian-stretch-iptables-and-iptables-persistent-service-start-and-stop-actions-no-longer-supported-4175622528/#post5817141)

---

<div class="post-metadata">

**Author:** ![onyxblack](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/o/f19dbf/32.png) [@onyxblack](https://discourse.pi-hole.net/u/onyxblack)\
**Post date:** [November 1, 2018, 7:59pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/20 "2018-11-01T19:59:32Z")

</div>

Sure... but... uhhh... how?

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [November 1, 2018, 8:04pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/21 "2018-11-01T20:04:37Z")

</div>

Below ones seems to do the trick:

```
sudo iptables -F
sudo iptables -X
sudo iptables -t nat -F
sudo iptables -t nat -X
sudo iptables -t nat -L -n -v
sudo iptables -t mangle -F
sudo iptables -t mangle -X
sudo iptables -P INPUT ACCEPT
sudo iptables -P OUTPUT ACCEPT
sudo iptables -P FORWARD ACCEPT

```

Check afterwards with:

```
pi@noads:~ $ sudo iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

```

To restore `iptables`, just reboot.

---

<div class="post-metadata">

**Author:** ![onyxblack](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/o/f19dbf/32.png) [@onyxblack](https://discourse.pi-hole.net/u/onyxblack)\
**Post date:** [November 1, 2018, 8:10pm UTC](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/22 "2018-11-01T20:10:24Z")

</div>

Done; however no change, am still getting no data on the web admin page

```
@localhost:~$ sudo iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

```

[Next page](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129.md?page=2)