@djingo
My syslog stopped working (I think after one o the updates) and this bug still exists. If you trying removing it form the Pool or individual hosts in the Pool via XO it will not let you have it as blank. If you ssh in and use xsconsole you can remove the syslog server and but it will not let you specify a port. But once it has been removed from xsconsole you can go back into XO and add in the syslogserver along with a non-default port such as

and it will work.

@pdonias said in Xen Orchestra & XO Lite PWA Manifest:

Thank you @john-c! We need to make a few changes first, we'll take care of your PR right after that 🙂

As a result of taking such a long time to get around to reviewing and merging my PR. The base for my contribution got really out of sync so I had to discard the changes and rebase. This meant the PR got closed a new one was needed. The Old PR with branch was really out of sync and with several lots of conflicts.

https://github.com/vatesfr/xen-orchestra/pull/7445

So please do this new one during today or tomorrow so that the rebasing isn't needed again!

i found this lines of code (ex. mint) in the other topic (https://xcp-ng.org/forum/topic/4583/adding-os-logos/14?_=1709647941739)
on the right side my version as ex.

NAME="Linux Mint"
VERSION="20.1 (Ulyssa)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 20.1"
VERSION_ID="20.1"

NAME="Scientific Linux"
VERSION="7.2 (Nitrogen)"
ID=scientificlinux
ID_LIKE=redhat
PRETTY_NAME="Scientific Linux 7.2"
VERSION_ID="7.2"

do i forgot to add some more lines like those (up) for e.x. ?

@stormi

Thanks for your answer.

I'll give a try later, bypassing the PFBlocker module of the router.

Github is not currently on any blacklist, but I block Digital Ocean and some others who host many attackers.

@Mathieu said in Problem importing ANY ESXi VMDK into Xen Orchestra CE:

Just experienced the same issue with a few VMs I imported from VMware.

I think it's a Windows issue, from what I can tell.

The network adapter type changes after the import in xcp-ng (from VMXNet to XenServer PV), that's normal.

Windows do not allow the same IP address to be used automatically for a different type of network adapter, so that's why it reverts to DHCP with the new adapter.

You can see that by setting the previous static IP address in the new adapter, it will warn you that the address was used with a previous adapter and asks for confirmation.

https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/error-message-when-you-set-ip-address

No idea if there's a way to avoid that.

Yeah same, we're also using VMXNET.
When trying to do this manually there's a popup which you have to accept to "force" having the same IP on multiple interfaces. Im sure the IP's are save in registry so deleting the post as part of the process would probably resolve it.

@Danp Aww. see that box. Let me look into this problem a bit more. Learning some new things here.

@julien-f Agreed... I will add (just for future reference) that I did confirm that I was on the very latest versions of xo-server at the time... in fact, I made sure to apply all updates and reboot the Xen server before submitting the ticket.

Nothing seemed to work... even multiple reboots, etc. Once @Danp made mention of the Nodejs version and I updated from v18.18.2 to v18.19.1 everything immediately started working. I made no other changes after applying the Nodejs update.

So while that may not have been the cause, it somehow fixed whatever was ailing me. I have no explanation either, other than the fact that making that change is what took me from the feature not working to the feature working. 🤷

@jedimarcus yarn dev start only the watcher(s)
you can start the server by using cd packages/xo-server and then yarn start

you can use nodemon instead of node if you want autoreload

@Danp Yes.

I have 3 VMs on this host plus the XOA. All using the same eth1.

I'm able to reach https://xen-orchestra.com/ from the network and other VMs.

Although in the Internet connectivity: Error: above it is being directed to non SSL connection.

Could it be that the registration cannot handle redirects?

JB

@Danp Interesting.

Now I have to try it! 🙂

Thanks,

JB

I'll be looking to setup webhooks to push backup logs to our SOC audit platform (tugboat), ideally on the weekly jobs.

Confirmed working with the new version.

@AtaxyaNetwork

Sorry, user error. I wasn't clicking and selecting the SR that was created for the ISO

🍾

Thanks for your feedback!

@olivierlambert said in After update xen orchestra web gui is not working:

ean you can't open a

okkkk thank you 😄

@DustinB Those are the correct tools. As I know that you are already aware 😉 , Windows can be temperamental at times. I generally take a snapshot before ever attempting to install them so that I can restore and try again if the first attempt fails.

You may need to remove them on the problematic VMs and try again.

@JeffBerntsen it's now fixed!

Even with a sfc and cleanup, manually reinstalling the package caused the same behavior. I've got backups of this system and will build a template from the working backup for if it goes sideways.

I've got other stuff to handle.

Well, that worked and the VM booted.... Windows joins domain, and.... /something went wrong, redeployment required/. No desktop, no apparent way to check for errors. We're beyond the scope of this thread. Thank you!

Serendipitously, someone from Netwrix called me soon after that. I told him I know the big two commercial virtualization names are supported, but all this /can/ be imported here... I also gave him a quick elevator pitch on XCP-ng, for as much good as that might do with a kinda new sales guy. From here on out, if their engineers can't help, I'm off to find something else. 🙂

@DustinB said in SR as a C drive of a VM:

"Build a VM > Attach this Disk and then detach the original 32GB disk"

exactly ""Build a VM > Attach this Disk and then detach the original 32GB disk"