Offline
@anik I believe that you have some of the names backwards.
XO Lite is available by default on XCP-ng 8.3. See the documentation for how to access it on XCP-ng 8.2.1.
The newer XO 6 interface is accessible from XOA by using /v6. It may need to be explicitly enabled to use it on XO from sources.
@coolsport00 Export the VM as an OVA file, then import this on the XCP-ng side.
@webminster The XOA dev team will need to verify that everything still works correctly before Netbox 4.3 will be officially supported. As explained in the documentation, you can force it to attempt to work with newer versions by editing your xo-server configuration like so:
[netbox]
checkNetboxVersion = false
Note the warning from the documentation --
Please be aware that by doing this, a Netbox update might make XO delete some of your data in Netbox.
@ferrao Prior to the latest release, the trial worked without actually activating the license on the XOA > Licenses tab. Double check that the license is activated (should look like this) --
This is what it will look like if the license hasn't been activated --
@ferrao Make sure that you've activated the trial license under the XOA > Licenses tab.
Hi @ferrao,
This is with XOA Free, correct? Have you tried switching to the Stable release channel?
Dan
Hi,
I'm pretty sure this is planned to be addressed in XO6.
Dan
Thinking about this further, it may be that way for you because you are using XOA Free, which I think they reverted to v5.105.0 because of the upgrade issue.
With a trial license in place, I get 5.105 with the Stable channel and 5.106 with the Latest channel.
@Lhoust said in XOA fails after update to 5.106.0:
For me Today, 5.105 is still what is available on the latest channel...
Are you sure? 
Please try pressing Ctrl+F5 to force reload the page.
@Lhoust Thanks for the feedback. The developers will fix the issue with XOA Free ASAP.
Although switching the channel from latest to stable dropped XOA Free down to 5.105, XOA Free remained Expired License LOCKED. Yesterday Quick Deploy was Blocked, therefore I used the Source Code Version to restore my XOA Free 5.105 Backup, which worked normally.
What do you mean by blocked? Was the site down?
Today my Restored XOA Free 5.105 shows 5.105 is the "Current" Version, XOA 5.106.1 is NO longer available as an upgrade.
This is accurate if you are on the Stable release channel. v5.106.1 is still available on the Latest release channel.
@Andrew Thanks for confirming that it is now working. Yes, it should have worked this way all along, and recent updates were made to enforce it.
@Andrew Could you double check that you have activated the license on the XOA > Licenses tab?
@Andrew Please open a support ticket and provide access via the support tunnel so that we can investigate.
Please try updating to XOA 5.106.1 and let us know if that corrects the issue for you.
Hi,
This is the expected behavior. The oldest backup will always be a full (key) backup, and newer incremental backups will be merged into this backup as you exceed the retention schedule. When you take the full backup on Saturdays, that doesn't eliminate the need for this prior full backup. Thus you end up with two full backups for a period of time.
@Nevering Have you check here? https://docs.xcp-ng.org/project/ecosystem/#-hosting
@MW6 You may be able to copy the VDI to another location so that you can access it via another VM.
Have you searched the internet for similar issues? Here's one that I found that may help you.
@coolsport00 Please stick with the documented method to be safe. 
@coolsport00 These are two different features. The XCP one involves renaming the physical NICs. Any changes you make in XO doesn't rename the physical NIC.