@vilhelm That's fixed: https://github.com/vatesfr/xen-orchestra/pull/6328. Thanks again for the report

pdonias created this issue in vatesfr/xen-orchestra

closed fix(xo-server/xapi-object-to-xo): handle guest metrics reporting empty IP field #6328

Hi @bnerickson, indeed, the configurations are correctly imported but plugins aren't automatically "configured" when you import a config. We'll improve that, thanks for the report

Hi @theaeon, this should already be fixed, could you check the full log for that error in Settings > Logs? It should give you more details.

Hi! We introduced a bug in commit 59e6868 causing "Page not found"s and fixed it in commit 6e52794.

@mjtbrady Yes, there was an issue on our side but it's fixed, now. Thanks for the feedback and let us know if you have other issues

@vilhelm This isn't the intended behavior, it should indeed pick the /24 prefix. I tested it with your values and it properly chooses the /24 prefix. Is the Netbox plugin up-to-date and re-built? It should work since commit 0966efb7f29758a3a179237e97e641f6288b6040 (XO 5.63.1, xo-server-netbox 0.3.1).

@vilhelm Thanks for testing, we'll fix it in master

This is simple enough so we'll implement it in XO 5. Thanks for the feedback!

@d1rtym0nk3y Thanks for the feedback! This is actually something that we had in mind. It will probably have to wait for the next major version of XO, though.

I already opened one: https://github.com/vatesfr/xen-orchestra/issues/4882.

pdonias created this issue in vatesfr/xen-orchestra

closed [VM] Network: show IP addresses in front of their VIFs #4882

@AtaxyaNetwork No worries! Glad it's working now

Hi @AtaxyaNetwork, are you sure you created the ACL on the pool and not on the host? If the ACL is on the pool, he should indeed be able to see the SR and network.

I took a look but I'm not able to reproduce We do have a known issue with the select component but not that one specifically. The non-breakable space wouldn't work between the icon and the text but maybe there's something else we can do if we can ever reproduce it. In any case, this will be fixed in the next major version of XO as we won't use that component at all any more.

@olivierlambert Yes, we'll store it in a cookie eventually. In the meantime, I'm changing the default language to English as it was probably a mistake to set it to French in the first place

@mjtbrady Did you accept the self-signed certificates by navigating to https://10.42.27.25/ and clicking on Accept? It's important to accept them for all the slave hosts, not only for the master host.

@mjtbrady Could you open your browser console (F12 > Console tab) and check if there's an error message when you open a VM console?

@redy Thanks for the feedback, we've added a "coming soon" message on pages that aren't implemented yet, to avoid confusion.

@bogdantomasciuc This is probably due to the browser rejecting self-signed SSL certificates when it tries to connect to the console (the console connections go directly to the slave hosts instead of going through the master). To fix that, go to each of your slave hosts' landing pages with HTTPS (https://<slave host IP>/). The browser should ask you if you want to accept self-signed certificates. Click on Accept. Once you've done that for all your hosts, go back to XO Lite, refresh and the consoles should work.

In the next releases, XO Lite will be able to detect when the self-signed certificates haven't been accepted and give clear instructions on what to do

@mjtbrady Yes, there was an issue on our side but it's fixed, now. Thanks for the feedback and let us know if you have other issues

Hi @mjtbrady, if you get the login screen, it means it's working. Are you sure you entered the right password for your host? You can check if there's been an error by opening the browser console with F12, then "Console" tab. If there's a SESSION_AUTHENTICATION_FAILED, it means you entered the wrong password (proper feedback on failed authentication will come soon ). If there's a different error message instead, could you post it here, please?