No diagram attached.
I don't understand how you may have set this up with custom firewall rules. The way I would have set it up with just 2 NICs is to put PiHole on the LAN with a static IP. Then in ClearOS you have a couple of choices:
1 - In the ClearOS DHCP server settings put the DNS as PiHole. You could also do a custom redirect rule on the INPUT chain redirecting TCP:53 and UDP:53 to PiHole
2 - In the IP Settings screen set a manual DNS of PiHole. If you do this, PiHole must not use ClearOS as its upstream resolver. It must go directly to the internet.
I'd possibly prefer 2 as you can still then use the ClearOS DNS screen to set local names.
This setup would work as well with 3 NICs with the third one being set as a LAN NIC as well. The two LAN NICs have to be on different subnets and PiHole muse be configured with a static IP on its subnet.
There is now another update to the Attack Detector app which adds an option to whitelist your LANs. This can be useful when, for example, setting up e-mail packages which often assume the full e-mail address is the username and you get banned when trying to set the user up. Or if you are doing some testing on your LAN.
As before, you can upgrade with:Note this will not be released next week as I'll be on holiday.
If enabled, if you are in gateway mode, any LAN (so not HotLAN or DMZ) will be whitelisted as will any subnet covered by static routes using the EXTRALANS parameter in /etc/clearos/network.conf.
Do the logs show anything? You can turn on the webconfig debug log:The trigger the error. Then turn off the webconfig debug log by deleting or renaming /var/log/webconfig/debug.log.
After that, have a look in /var/log/webconfig/debug.log for any obvious error. There are always a few but something may jump out. Don't leave debugging enabled as it will generate huge logs.
It should not make any difference which version you are using> Community have received a fix and the faulty update was never released to paid customers. Check that you have disabled the clearos-updates, clearos-centos, clearos-centos-updates and something like clearos-epel as these are community repos.
When the bar is going across the screen, if you hit the right arrow (and possibly all sorts of other keys) it will switch to a text display scrolling by. You may then be able to capture the issue. It may also appear in your boot log and/or messages log under /var/log.
To restore the backup just use the System > Backup > Configuration Backup and Restore menu. It will try to reinstall all your apps and your users. It will be better to register the system first as an Upgrade/Reinstall first or it won't be able to load NC or any other paid app.
Be careful of the firewall settings. If you go to a new machine, they may not be directly convertible. Please see the first blue box and second pink box at https://documentation.clearos.com/content:en_us:7_ug_configuration_backup.
Nextcloud data is under /var/clearos/nextcloud/data, but you can't sensibly restore the NC database. That will need setting up again.
You will need a USB or CD to go into recovery mode.
If your system crashed between Jun 30th and about July 2nd and you have ClearOS Community, it is possible that you had a bad update to grub2 which will make your machine unbootable. Please see the workaround in this thread.
You won't find 3.8 mentioned on the Software Collections site but it does exist. Their documentation is not good but rh-python38 is directly installable from the command line using your current repositories. To use it, just translate 36 -> 38 from the link I gave.