Problems logging in to Apple services

[granada29]

I have installed Sierra Beta in a virtual machine running under El Capitan.

It is mostly working except I don't seem to be able to use Apple services such as Messages or downloading updates from the App Store.
When I enter my AppleID and password in Messages, nothing happens.
I am able to log into the App Store but downloads of available (Sierra) updates are not working.
I know its not specific to Sierra - I had the same problem when I first built the machine as El Capitan.

Is it possible that there is something wrong with the hardware identification as seen by Apple? The physical hardware is Mac-Mini (late 2012) and running El Capitan (10.11.6), with VirtualBox 5.1.2

Bryan

[socratis]

I am able to log into the App Store but downloads of available (Sierra) updates are not working.

You most certainly don't have to login to get the updates. I'm updating mine as I write this I just updated from 10.12b1 (16A238m) to 10.12b2 (16A254g). Hardware here is MBP, early 2011.

I know its not specific to Sierra - I had the same problem when I first built the machine as El Capitan.

And how did it get fixed? Did you change something in the VM recipe?

Is it possible that there is something wrong with the hardware identification as seen by Apple?

It could very well be, but only Apple could answer what they're looking for when doing the updates. Maybe they have a program where they don't allow updates from specific models, or they're artificially and randomly limiting who gets an update. It could very well be that your IP is already logged in from your El Capitan host and it doesn't allow two IPs concurrently. Or they're just messing with your head. Who knows?

There is one very light chance that you'd need to change something in your VM, the serial number of your VM. I'll test it and update the post. It doesn't matter from what is seems like it. But in any event, it doesn't hurt if you try it: viewtopic.php?f=8&t=75053 and viewtopic.php?f=8&t=61825 (under Modifications).

[granada29]

I initially installed El Capitan in the VM from an ISO.

The only tweaks to the VM from the VirtualBox defaults for an OSX guest were setup bridged networking, increase videoram to 128MB, Mem to 8192 MB and increase cpu count to 4.

I had previously downloaded the Sierra Beta installer (in the host OS), copied it to the El Capitan VM (vis scp) and then ran the installer. It installed fine but as I said, I can't download the updates from the Apple store.

[socratis]

setup bridged networking

Is that on a wireless network? If so, please try it with either a wired network or change the network mode to NAT and see if it changes the situation.

1. Start the VM. Not from a saved or suspended state. Clean start. Log in.
2. Shut down the VM. Not suspended, not paused. Shut down.
3. Right-click on the VM in the VirtualBox Manager. Select "Show Log..."
4. Save it (just the first log), ZIP it and attach it in your response (see the "Upload attachment" at the bottom of the form).

I'd also like to see the "recipe" of the VM, the ".vbox" file:

1. Right-click on the VM in the VirtualBox Manager. Select "Show in Finder".
2. ZIP the selected ".vbox" file and attach it in your response.

[granada29]

I have a wired network. The network appears to work fine. Web browser (Chrome) is working, WhatRoute is showing traffic, traceroute, ping etc. I will try with NAT to see if it makes a difference.

Log and config attached as requested.

Regards
Bryan

[granada29]

Using NAT makes no difference - still can't login to Messages

[socratis]

Just to take out of the equation the last thing I can think of; network configuration. Post the output of the following commands (in purple). For comparison, mine was (the grey is pretty much irrelevant, but include them nonetheless):

• ifconfig
  lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
  	options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
  	inet 127.0.0.1 netmask 0xff000000 
  	inet6 ::1 prefixlen 128 
  	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
  	nd6 options=201<PERFORMNUD,DAD>
  gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
  stf0: flags=0<> mtu 1280
  en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
  	options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>
  	ether 08:00:2789:0c 
  	inet6 fe80:c166:80b0:379f%en0 prefixlen 64 secured scopeid 0x4 
  	inet 10.0.0.106 netmask 0xffffff00 broadcast 10.0.0.255
  	nd6 options=201<PERFORMNUD,DAD>
  	media: autoselect (1000baseT <full-duplex>)
  	status: active
  utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
  	inet6 fe80::9829:b2b8:aa8e:c417%utun0 prefixlen 64 scopeid 0x5 
  	nd6 options=201<PERFORMNUD,DAD>
  
  networksetup -getdnsservers Bridged
  There aren't any DNS Servers set on Bridged.

Note that "Bridged" is the name of my network card in the Network Settings. Yes, I did rename it. Adjust for your case accordingly.

[granada29]

As requested.
DNS servers are assigned by DHCP. Not sure why networksetup doesn't realise that. Clearly DNS is working - I copied this data from the VM to the host OS in a text file using scp and dns.

sierra-vbox:~ bryan$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>
ether 08:00:27:8e:2d:9c
inet6 fe80:5b997749%en0 prefixlen 64 secured scopeid 0x4
inet6 2001:470:4a64:104283:77c4:107f prefixlen 64 autoconf secured
inet6 2001:470:4a64:10:8c67:9b40:77ff:4160 prefixlen 64 autoconf temporary
inet 10.64.1.209 netmask 0xffffff00 broadcast 10.64.1.255
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (1000baseT <full-duplex>)
status: active
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
inet6 fe80::9401:c94c86fd%utun0 prefixlen 64 scopeid 0x5
nd6 options=201<PERFORMNUD,DAD>
sierra-vbox:~ bryan$ networksetup -getdnsservers Ethernet
There aren't any DNS Servers set on Ethernet.

[socratis]

ether 08:00:2789:0c 
inet6 fe80:c166:80b0:379f%en0 prefixlen 64 secured scopeid 0x4
inet 10.0.0.106 netmask 0xffffff00 broadcast 10.0.0.255

ether 08:00:27:8e:2d:9c
inet6 fe80:5b997749%en0 prefixlen 64 secured scopeid 0x4
inet6 2001:470:4a64:104283:77c4:107f prefixlen 64 autoconf secured
inet6 2001:470:4a64:10:8c67:9b40:77ff:4160 prefixlen 64 autoconf temporary
inet 10.64.1.209 netmask 0xffffff00 broadcast 10.64.1.255

It seems that you're getting an IP6 from your router. Maybe it's trying to connect over IP6 and it's failing? Can you disable it and try it out?

[granada29]

Still the same result with ipv6 disabled.

[socratis]

OK, last stop; search...
I did a quick one for "10.12 cannot access updates" and this little gem popped up: https://forums.developer.apple.com/thread/48692 . See if it helps to look at it NOT as a VirtualBox issue, but as an OSX issue...

[granada29]

Thanks for the help. Resetting the login keychain didn't fix it. Still now downloads from App Sore and can't sign in to Messages.

I tried it about 4 times (I think Einstein had something to the say about the futility of repeating actions but oh well).

I'll try a clean install of Sierra (instead of an update from El Capitan) and see if that fixes things.

Regards
Bryan

[granada29]

After a clean install, App Store updates are working. I did NOT sign into my AppleID at point so far. I'll get all the updates installed and then try that.

I still suspect it is something to do with how Apple are identifying the virtual machine but I'll report back here after I have Beta 3 installed.

Regards
Bryan

[granada29]

After a clean install of Sierra Beta (1st developer release)
1. App Store updates are working and I successfully updated the OS to Sierra Beta 3.
2. Xcode 8 (beta) was able to register my developer account using AppleID.
3. Messages still refuses to let me login with AppleID (same ID as used for my developer account)

Conclusion - I don't really need Messages on the guest system. It works fine from the host system. Again - I suspect it is probably to do with the VM serial or UUID but if Messages is all that is affected then I can live with it.

Closed

Thanks for all the help
Bryan

[socratis]

If it works with older OSX clients (which it does), if it works with other apps (which it does), then I highly doubt it's a VirtualBox problem, but rather an OSX beta problem. Let it ripe enough (see: released) and if the problem persists, then we'll visit it again...