See prior discussion here.

HTTPS is fine, HTTP can cause issue with some local firewalls/AV (!).

@hawk223 said in Hardware Health Monitoring: @john-c I have access to configure myself as an email recipient however, I don’t recall the reason I never did that. There is some complication with doing so. If I recall it needs a hack to configure an email server. I will investigate. I have also been looking into something like nagios or zabbix. But then that’s something extra required. I would prefer a simple solution that doesn’t require a lot of effort and hacking. Most modern BMC include a web interface for access, so you can navigate to it and log in via its form. From there it's fairly simple to then setup, though the account for sending the email maybe a challenge as some implementations require the sending account to not have a password! The exact host name depends on the configuration of the IP address and/or FQDN of the BMC in your network system.

@Octive Make sure you follow the doc at https://github.com/vatesfr/xen-orchestra/blob/master/%40xen-orchestra/mixins/docs/SslCertificate.md To be able to get a Let's Encrypt certificate, your XOA must be publicly reachable on both HTTP and HTTPS. You do not need to manually create the file nor do you need to restart xo-server. Also, if your web browser trust Let's Encrypt CA (most of them do), your certificate should be recognized automatically.

It's very likely the configuration of either your OpenID provider or in your XO plugin config. See our example with Keycloak: https://xen-orchestra.com/blog/xen-orchestra-5-80/#-openid-connect-support

And we are blown away by our wonderful community! Thank you very much, and happy to help you!

There are just many locations for the logs and the seem to have to be handled quite different: Audit-Logs: Can be exported and so can be sent to syslog, but: I did not find a way to do that efficient, as "xo-cli get-Records" seems not to be able to use filters like "after/before". Pool-Log: Is only visible in the GUI. Did not find a way to send it to syslog, or to export it periodically. XOA-Log: /var/log/syslog can be exported, but is using quite nasty "multi-line-logs". Task-Log: As Audit-Logs: Can be fetched by: "xo-cli rest get tasks", but did not get filters working, yet. It would be perfect to have options to send directly to syslog, but a workaround through a periodically running script could be good, too.

I wonder when XenCenter stores this name since there's no XAPI field for it

Nice! Let us know if you want it to be added on the REST API

If this specific VM is causing issue, you can fallback on Clonezilla or something similar

Different brand? Can be the controller too. But reading what I'm seeing on the screen, it's very likely to be a disk issue.

@itiojoe You're welcome ! Have fun with Xen Orchestra !

@olivierlambert Bug has been filed. https://github.com/vatesfr/xen-orchestra/issues/7193 ajpri created this issue in vatesfr/xen-orchestra closed Can't Remove PIF #7193

Hi! The first reflex when you have an issue is to check: Pre-requisites: https://xen-orchestra.com/docs/installation.html#packages-and-pre-requisites Being up to date In your case, it was 1 Note: Node 20 compatibility will come soon but it doesn't mean 1 & 2 should be done before anything else Also, nice catch @Danp

Issue is now fixed on master branch. A patch release for XOA Latest will come at some point

Okay, glad to know it works! Good luck for the rest of your operations!

OK then I will wait. The icons are not an important feature for survival anyway.

FWIW, I just ran into this same issue with Node 20.9.0, which is the current LTS version. Reverting to Node 18.18.2 resolved the issue for me.