nblom
commented
4 years ago You can check the access logs in the NetSUS /var/log/apache2/access.log Does your clients make successful requests and are the catalogs found?
Open gtdragon980 opened 4 years ago
nblom
commented
4 years ago You can check the access logs in the NetSUS /var/log/apache2/access.log Does your clients make successful requests and are the catalogs found?
We setup a new NetSUS instance on a RHEL box and are in the process of troubleshooting why we cannot see any available updates on our endpoints. We setup a "Test" branch for our internal testing group to ensure that updates are being delivered, but during our testing we found that it would return "No new software avaiable" when checking for updates. The branch has all updates selected and applied, I am able to reach the content folder when navigating to it using a web browser, yet our Macs can't see any updates. I have tried variations of the URL, all of which return "Can't connect..." except for our main URL that I copied from the branch in NetSUS. This setup is nearly identical to our old NetSUS and I our endpoints to connect to it using a configuration profile and they can see updates just fine from that one. However on our new box, they machines can't see anything. Any idea as to why the machines cannot see the enabled updates?