Skip to main content

hi to all... banging my head on this...



Netsus was working fine with all computers from 10.12 to 10.14. Now with 10.15, with HTTP catalog address not finding any updates...



So decided to change to HTTPS.



Now message on 10.15 Macs while looking for my Netsus server saying that certificate to access the server is not valid.



So I guess because the certificat by default on NETsus is self signed and not secure. So trying to create another on through GUI on Netsus webadmin console....



BANG... nothing works... having difficulties to create it. Ik have all the parts but at the end the console gives me the error :



Chain verify error 18 at 0 depth lookup:self signed certificate.



1- anybody with a solution without changing the cert in Netsus ?
2- anybody with detailed instruction for the Netsus cert replacement ?



anything else ?

Hello, with Catalina clients I use the specific catalog in NetSUS, setting the URL with a policy (File & Processes/Execute Command)



defaults write /Library/Preferences/com.apple.SoftwareUpdate CatalogURL http://yourNetSUS.domain.com/index-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog


You may also try with a different catalog



http://yourNetSUS.domain.com/content/catalogs/others/index-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1_SUS.sucatalog


If you paste the URL in a browser, you should see the XML with all the available updates



Also I have another policy with (File & Processes/Execute Command)



defaults write /Library/Preferences/com.apple.SoftwareUpdate SUDisableEVCheck -bool TRUE


You may try using a script putting the two commands together
Hope it helps
Ciao
Carlo

@jmercier

Does the SSL cert meets the Catalina requirements?



Requirements for trusted certificates in iOS 13 and macOS 10.15

Thanks to all... its all fixed... rebuild the Netsus server had problem on the DNS name on the appliance and change couple of things and started working after... thanks

@jmercier Im having the same problem here, could you let me know where did you change?

Terms & ConditionsCookie settings