# \[SOLVED\] No connections possible after restart

**URL:** <https://discuss.freedombox.org/t/solved-no-connections-possible-after-restart/284>\
**Category:** Hardware Owners Support\
**Created:** [July 26, 2019, 2:36pm UTC](https://discuss.freedombox.org/t/solved-no-connections-possible-after-restart/284 "2019-07-26T14:36:53Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![badom](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/b/ba9def/32.png) [@badom](https://discuss.freedombox.org/u/badom)\
**Post date:** [July 26, 2019, 2:36pm UTC](https://discuss.freedombox.org/t/solved-no-connections-possible-after-restart/284/1 "2019-07-26T14:36:53Z")

</div>

I have a new freedombox (Pioneer kit). I have mostly only installed/configured the prepackaged stuff and has been working fine. After a system restart via the web UI, freedombox cannot be reached via web ui or ssh over the local network, via any address ( `10.10.10.101` , where I can see the network knows it is, or `freedombox.local` , etc). For ssh, I get “ssh: Could not resolve hostname freedombox.local: Name or service not known”. Hard reboots do not solve this. The only thing I’ve done other than install standard packages via the web UI is run `apt update && apt upgrade -y` . I am not a complete Linux n00b but since I’ve never had a Linux server in the room with me, I think there’s always been someone else dealing with it not coming back online heh. The device is properly connected and had been working fine immediately prior to restart.

---

<div class="post-metadata">

**Author:** ![badom](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/b/ba9def/32.png) [@badom](https://discuss.freedombox.org/u/badom)\
**Post date:** [July 26, 2019, 3:57pm UTC](https://discuss.freedombox.org/t/solved-no-connections-possible-after-restart/284/2 "2019-07-26T15:57:32Z")

</div>

I can now add that when connecting a keyboard & monitor to Freedombox, I am able to login as my local user. If I run the prompted `systemctrl` command to “activate the web console”, I get an authentication prompt at `org.freedombox.systemd1.manage-unit-files`.

---

<div class="post-metadata">

**Author:** ![jvalleroy](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/jvalleroy/32/331_2.png) [@jvalleroy](https://discuss.freedombox.org/u/jvalleroy)\
**Post date:** [August 6, 2019, 12:18am UTC](https://discuss.freedombox.org/t/solved-no-connections-possible-after-restart/284/3 "2019-08-06T00:18:04Z")

</div>

@badom Just a note, “activate the web console” refers to Cockpit, not to the FreedomBox web interface. And the command listed is not correct for enabling Cockpit on FreedomBox.

If you run “ip a s”, do you see an (inet) IP address listed under eth0?

---

<div class="post-metadata">

**Author:** ![badom](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/b/ba9def/32.png) [@badom](https://discuss.freedombox.org/u/badom)\
**Post date:** [August 6, 2019, 12:27am UTC](https://discuss.freedombox.org/t/solved-no-connections-possible-after-restart/284/4 "2019-08-06T00:27:42Z")

</div>

I see `inet 10.10.10.101/24 brd 10.10.10.255 scope global dynamic noprefixroute`,

---

<div class="post-metadata">

**Author:** ![Sunil](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/sunil/32/8_2.png) [@Sunil](https://discuss.freedombox.org/u/Sunil)\
**Post date:** [August 6, 2019, 5:49am UTC](https://discuss.freedombox.org/t/solved-no-connections-possible-after-restart/284/5 "2019-08-06T05:49:12Z")

</div>

You probably getting the authentication prompt because you are not root user. You can use `sudo su -` to login as root and then run `systemctl`and other commands.

It would be nice if you could check the following:

Checking for network connectivity (assuming 10.10.10.1 is your router’s IP address)

```auto
$ ping 10.10.10.1
$ ping 1.1.1.1

```

On a machine that is not FreedomBox but in the same network:

```auto
$ ping 10.10.10.101

```

On FreedomBox check that services are running fine:

```auto
$ systemctl status firewalld
$ ss -nlpt | grep 443
$ ss -nlpt | grep 22

```

Provide us the output of firewall status (recently there was an upgrade in firewalld package although this should not have affected you):

```auto
$ firewall-cmd --list-all-zones

```

See if disabling firewall works:

```auto
$ systemctl stop firewalld

```

Re-enable after

```auto
$ systemctl start firewalld

```

Verify that firewalld has proper configuration

```auto
DefaultZone=external

```

in `/etc/firewalld/firewall.conf`.

Check that web server is running

```auto
$ systemctl status apache2
$ curl -v http://localhost/

```

Try this from outside FreedomBox

```auto
$ curl -v http://10.10.10.101/

```

---

<div class="post-metadata">

**Author:** ![badom](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/b/ba9def/32.png) [@badom](https://discuss.freedombox.org/u/badom)\
**Post date:** [August 6, 2019, 7:43pm UTC](https://discuss.freedombox.org/t/solved-no-connections-possible-after-restart/284/6 "2019-08-06T19:43:58Z")

</div>

Okay, making progress! Thanks Sunil!

Freedombox cannot be pinged from elsewhere on the network.

I can ping outside connections from Freedombox.

```
$ systemctl status firewalld

```

 ![16%20PM](https://discuss.freedombox.org/uploads/default/original/1X/e0dd519868992c4c1b3399e1acd3abeac860417f.jpeg)

Disabling firewall works! I can ping and reach Plinth from remote with firewall disabled.

Restarting firewall gets me back to the original problem.

Verified `DefaultZone=external`.

Apache2 is running, localhost is running (headers returned), but no connections to Freedombox from outside.

---

<div class="post-metadata">

**Author:** ![Sunil](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/sunil/32/8_2.png) [@Sunil](https://discuss.freedombox.org/u/Sunil)\
**Post date:** [August 6, 2019, 9:49pm UTC](https://discuss.freedombox.org/t/solved-no-connections-possible-after-restart/284/7 "2019-08-06T21:49:12Z")

</div>

It appears that you facing a bug that was [fixed](https://salsa.debian.org/freedombox-team/plinth/issues/1457). However, we had issues with making the fixes available to stable release users. We hope that these fixes will be available [soon](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933856). Meanwhile, you can run the following commands to fix the issue.

```auto
firewall-cmd --zone=internal --remove-interface=tun+ --permanent
firewall-cmd --zone=internal --remove-interface=tun+
systemctl restart firewalld
(probably restart the machine here)
firewall-cmd --zone=internal --add-interface=tun0 --permanent
firewall-cmd --zone=internal --add-interface=tun0

```

---

<div class="post-metadata">

**Author:** ![badom](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/b/ba9def/32.png) [@badom](https://discuss.freedombox.org/u/badom)\
**Post date:** [August 8, 2019, 4:41pm UTC](https://discuss.freedombox.org/t/solved-no-connections-possible-after-restart/284/8 "2019-08-08T16:41:08Z")

</div>

Awesome! This worked. I did have to restart firewalld one more time at the end, but hooray!

---

<div class="post-metadata">

**Author:** ![Sunil](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/sunil/32/8_2.png) [@Sunil](https://discuss.freedombox.org/u/Sunil)\
**Post date:** [August 8, 2019, 5:27pm UTC](https://discuss.freedombox.org/t/solved-no-connections-possible-after-restart/284/9 "2019-08-08T17:27:11Z")

</div>

We also have freedombox 19.13 on it’s way to all users. It would have fixed the problem too 🙂 Thanks for reporting back.
