FleetDM - Server IP address changed but Fleet is not recognizing it

[Nolan-Mcfly]

The issue I am having with Fleet is that I originally installed Security Onion with the IP address of 192.168.0.167, but I changed my IP to 192.168.0.19 as a static address. .167 was not a static IP for the server at the beginning of the installation. Everything is working, as I ran so-ip-update, but Fleet is not showing any host names online besides the server. I have checked a few different config files, but I cannot find anything that would point to Fleet not working with 192.168.0.19, in fact the web page for Fleet is loading at the .19 address. I have rebooted, restarted Fleet with so-fleet-restart --force and when I run that command, I get this among the output:

---

      ID: fleetdb
Function: mysql_database.present
    Name: fleet
  Result: False
 Comment: MySQL Error 1130: Host '192.168.0.19' is not allowed to connect to this MySQL server
 Started: 10:34:47.740950
Duration: 202.909 ms
 Changes:   

---

      ID: fleetdbuser
Function: mysql_user.present
  Result: False
 Comment: One or more requisite failed: fleet.fleetdb
 Started: 10:34:47.946236
Duration: 0.009 ms
 Changes:   

---

      ID: fleetdbpriv
Function: mysql_grants.present
  Result: False
 Comment: One or more requisite failed: fleet.fleetdb
 Started: 10:34:47.947889
Duration: 0.009 ms
 Changes:   

---

I am not sure how to go about fixing this, aside from just using 192.168.0.167 as my static IP. Any and all thoughts or suggestions are welcome, thank you.

[defensivedepth]

@Nolan-Mcfly Can you please post the output from the following (sanitizing as needed)?

sudo salt-call pillar.get global

[defensivedepth]

Didnt get a notification that you had replied!

Are you still having issues with it?

[Nolan-Mcfly]

@defensivedepth No problem, I should have followed up again but I'm sure you are very busy. Yes, it is still an issue. I tried a few other things like editing the conf file on a couple of the machines that are connected to Fleet because they still had the old Server IP and that didn't seem to fix the issue. Basically where I am at right now with this is that everything is working besides the hosts showing as online in Fleet, every host shows offline besides the Fleet server (host machine). I'm wondering if there's a way to get a new flag file and enroll secret if those two things are necessary to begin working again?

Thanks,

Nolan

[defensivedepth]

I think it might be a cert issue.

Can you review the logs in the Application eventlog channel on one of the Windows systems, looking for Launcher logs? Best thing to do would be to restart the launcher service, which will force it to try and connect, and you should see connection error logs in the Application channel.

[mckinleyc]

I am currently having the same issue with all nodes showing offline. I cannot get any agent to connect and even the manager is showing offline. The cert is different between what is on the server and what is downloaded from the web interface. Could this be an issue?

[defensivedepth]

@mckinleyc Please open a new Discussion following these Guidelines - #1720

Thanks