Did you happen to take a snapshot before performing the update? If so, restoring from that is probably your safest bet.

There was a recent commit that is likely causing this and other issues. I suggest that you try with XOA or else build your XO VM from an earlier point-in-time.

@olivierlambert Do you agree?

FWIW, I just tried updating and did run into an issue. However, I suspect yours is caused by an incorrect Node version.

If node -v returns something other than 8.16.0, then you should try switching to that version with the command n 8.16

In my case, I get a spinning cursor after logging in. Checked the logs and found the following --

Jun 07 20:26:58 ubuntutest xo-server[3780]: 2019-06-07T20:26:58.702Z - xo:api - [WARN] dan@mydomain.com | xo.getAllObjects(...) [4ms] =!> XoError: invalid parameters

More details please. I'm assuming that you are building from source. What method did you use to update your XO VM? What OS? Node version?