@Tom-Elliott So I’ve copied my /opt/fog/snapins/ssl folder, and the ca-key in /etc/fog/pki/root/ca/ folders, then followed your advice above and re-ran the installer. The legacy agent still won’t communicate consistently it seems. Our existing agent seem to be communicating I think, but fresh installs of the legacy agent are having nothing but issues from what my team are telling me.

I just did a massive overhaul on our fog service, migrating directly into 1.6 by running a new server from scratch rather than a database migration (there were some Foreign Key check failures on the in-place upgrade), and for the most part everything seems to be working except reliable agent communication. Both on the old and new agent I’m having a bitch of a time with the CA communication.

When using the new agent from the GitHub, I get a 503 error, so referencing the apache error logs gives me a bit of insight:
Got error 'PHP message: FOG agent enroll: signing for host 387 from 10.1.60.40 failed: the issued certificate does not verify against /opt/fog/snapins/ssl/CA/.fogCA.pem'

In this instance, this was a fresh agent install, so I’m not sure what cert is being compared to what. I’m assuming until told otherwise that my FOG Generated PKI is foobar for production use, but I’m unsure of the steps to even take in this instance.

@jj-fullmer Can you clarify a bit more on your file structure and the placement of the ModelList.txt file? I’m trying to duplicate your success but I’m having a little trouble with the remotedriverpath variable.