Ask the Community
Groups
Kaseya Application Firewall Service has to be restarted after server reboot - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>Problem:</strong></p> <p>After a reboot of the kaseya server, agents do not check-in until the Kaseya Application Firewall service is restarted.</p> <p> </p> <p><strong>Cause:</strong></p> <p>When the KAF service starts, it looks to the Kaseya Server service to find out what ports to start on.</p> <p>If the Kaseya Server service has not fully initialised at the time that the KAF service starts, then it will look to its config file for the defaults.</p> <p>If you are not running on one of these defaults - 80, 443, or 5721, the agents will not be able to check in.</p> <p> </p> <p><strong>Resolution:</strong></p> <p>Edit \kaseya\services\Kaseya.ApplicationFirewall.config (version 7)</p> <p>\kaseya\services\KaseyaEdgeServices.config (version 8)</p> <p>Change the default ports to those that you want to use as defaults, save the file and restart the Kaseya Application Firewall</p> <p>Upon future reboots, KAF will start on the ports that you have specified.</p> </article> </main>