@olivierlambert I would agree... one of those odd glitches that occurred during the build process that corrected itself on a second run.

Thanks for everyone's help... please go ahead and close this out!

@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. 🤷

@Andrew Thank you Andrew... sorry it took me a while to get back to you. It seems every time I have to go and update Node they change the method you need to do so and it takes me forever to figure out what I'm supposed to do.

I still haven't figured that out, but that's on me. However, restarting the toolstack did not fix the issue, but restarting the XO Ubuntu host server did.

I've not seen anything like that before, where I've had to reboot the entire host server after applying commits... but if it works, I shall not argue!

Thank you again for all of your help. I hope you have a wonderful weekend and a fantastic holiday season.

So that makes sense then 🙂 Closing here 🙂

No problem, happy to help!

That happens to me about once every six weeks on one of the XO installs. For what its worth, if I just kill the XO vm and let it reboot, as long as its not out of disk space, it always works the second time.

Thanks for sharing 🙂