Skip to content

firewall: Closing http/https ports?

I was running functional tests in testing container, and I observed that after some point all the tests were failing, and I cannot access FreedomBox interface in the web browser. These are the last logs from plinth:

    INFO plinth.actions       # users get-user-groups tester
    INFO plinth.actions       # service disable bind9
    INFO plinth.modules.firewall.components Firewall ports closed - BIND, ['dns']
Unit bind9.service could not be found.
    INFO plinth.modules.firewall.components Firewall ports opened - BIND, ['dns']
    INFO plinth.actions       # service enable bind9
    INFO plinth.actions       # service enable named
    INFO plinth.actions       # bind configure --forwarders '1.1.1.1 1.0.0.1' --dnssec enable
    INFO plinth.actions       # bind configure --forwarders '1.1.1.1 1.0.0.1' --dnssec disable
    INFO plinth.actions       # bind configure --forwarders '1.1.1.1 1.0.0.1' --dnssec enable
    INFO plinth.actions       # bind configure --forwarders '1.1.1.1 1.0.0.1' --dnssec disable
    INFO plinth.actions       # bind configure --forwarders 1.1.1.1 --dnssec disable
    INFO plinth.actions       # backups list-repo --path /var/lib/freedombox/borgbackup
    INFO plinth.actions       # service stop bind9
    INFO plinth.modules.backups.api Running backup_pre hooks
    INFO plinth.actions       # backups create-archive --path /var/lib/freedombox/borgbackup::test_bind --paths /etc/bind/named.conf.options /var/lib/plinth/backups-manifests/varlibfreedomboxborgbackuptest_bind.json
    INFO plinth.modules.backups.api Running backup_post hooks
    INFO plinth.actions       # service start bind9
    INFO plinth.actions       # backups list-repo --path /var/lib/freedombox/borgbackup
    INFO plinth.actions       # bind configure --forwarders 1.0.0.1 --dnssec disable
    INFO plinth.actions       # bind configure --forwarders 1.0.0.1 --dnssec enable
    INFO plinth.actions       # backups list-repo --path /var/lib/freedombox/borgbackup
    INFO plinth.actions       # backups get-archive-apps --path /var/lib/freedombox/borgbackup::test_bind
    INFO plinth.actions       # backups get-archive-apps --path /var/lib/freedombox/borgbackup::test_bind
    INFO plinth.setup         Running setup for modules, essential - True, selected modules - None
    INFO plinth.actions       # service stop bind9
    INFO plinth.modules.backups.api Running restore_pre hooks
    INFO plinth.actions       # backups restore-archive --path /var/lib/freedombox/borgbackup::test_bind --destination /
    INFO plinth.modules.backups.api Running restore_post hooks
    INFO plinth.actions       # service start bind9
    INFO plinth.actions       # backups list-repo --path /var/lib/freedombox/borgbackup
    INFO plinth.actions       # service disable bind9
    INFO plinth.modules.firewall.components Firewall ports closed - BIND, ['dns']
Unit bind9.service could not be found.
    INFO plinth.actions       # service disable cockpit.socket
    INFO plinth.actions       # apache disable --name cockpit-freedombox --kind config
    INFO plinth.modules.firewall.components Firewall ports closed - Cockpit, ['http', 'https']
    INFO plinth.actions       # storage usage-info
    INFO plinth.actions       # upgrades activate-backports --develop
    INFO plinth.actions       # storage usage-info
    INFO plinth.actions       # upgrades activate-backports --develop
    INFO plinth.actions       # storage usage-info
    INFO plinth.actions       # upgrades activate-backports --develop
    INFO plinth.actions       # storage usage-info
    INFO plinth.actions       # upgrades activate-backports --develop
    INFO plinth.actions       # storage usage-info
    INFO plinth.actions       # upgrades activate-backports --develop
    INFO plinth.actions       # storage usage-info
    INFO plinth.actions       # upgrades activate-backports --develop
    INFO plinth.actions       # storage usage-info
    INFO plinth.actions       # upgrades activate-backports --develop

It looks like when Cockpit was disabled, the http/https ports were disabled in firewall.

# firewall-cmd --zone=internal --list-services
dhcp dhcpv6-client mdns samba-client ssh