@olivierlambert I can do it pretty easily, but there may be a good reason for XAPI to throw this error instead.

There’s usually little to no reasons to expose any mgmt systems to internet in actual production environments. Especially if it’s strictly for internal mgmt purposes. XO is no exception. Not because the system would be unsecure, but you simply want to make any attack surface as small as possible. It’s just a best a practice.

I think it's "because" we fixed it upstream and then Fedora packaged the fix in their latest update 🙂

Try to disable/enable autostart in Advanced section of your VM. That might do the trick.

@olivierlambert Thanks for your patience. I have no idea how I missed it as I reread the blog post twice.

Yep

Ah thanks, always happy to have feedback from "outside", it's really reassuring 🚀

@olivierlambert Re: SSH keys in XO
Great, thanks for your explanation!

Great! Your team proves just how legendary it is once again! Thank you!