• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

MacOS can't reach udate server anymore

U

uOpt

2[H]4U
Joined
Mar 29, 2006
Messages
2,857
I have a Mac Mini M4 under 26.5.1. It cannot reach its update server anymore to retrieve the list of available updates:

Code: 
% softwareupdate -l
Software Update Tool

Finding available software
Didnât get a response from the Apple Software Update server.

Prior to this the machine was using `softwareupdate -l` extensively via a monitoring cronjob. I guess I have been disabled due to hammering the server, but I can't figure out how. I tried various Google results to no avail.

  • The machine still has full internet connectivity otherwise
  • Reboot doesn't help
  • The GUI in settings shows the same timeout as the commandline
  • It is not an IP address level block. Other Macs on the same residential address show updates normally.

I would really hate to have to reinstall the OS from scratch to fix this.

Any bright ideas?
 
download and install them manually or ignore it and see if it eventually goes back to normal
 
pendragon1 said:
download and install them manually or ignore it and see if it eventually goes back to normal
Click to expand...

I thought the updates are not directly downloadable anymore since a few versions back?

I have waited for a week after stopping the cronjob, I don't think it will reset itself.
 
That doesn't work either for the *.pkg, because it wants to "personalize" the update, which it does through the update server, which it can't reach.

However, I found what was causing it. I noticed that although I could ping www.google.com I could not reach it in a web browser. http and https traffic were broken, not anything else.

From there is was a short path to discover a broken global proxy setting. How and why that was introduced on a home machine while I was on vacation is a different question.
 
You must log in or register to reply here.
Back
Top