XOA fails after update to 5.106.0
-
@olivierlambert so how can I unregister the 2nd one without loosing the VMs on host?
Do I have to remove the XOA VM and then re-install? Is there something command line that I need to do? etc..... -
If you simply update your second XOA, it should downgrade it to XOA Free (if I remember correctly)
-
@olivierlambert I tried upgrading downgrading the versions, stable to latest etc... it doesn't remove my registration on 2nd XOA which is what I am trying to do just to use free version.
-
I see, let me check internally why, you should (in theory) being able to use XOA Free on this second XOA.
In the meantime, can you try to deploy a fresh one, register and see if you can just have XOA Free?
-
@olivierlambert deploying fresh copy worked and registered under different email. Thank you for assistance
-
Similar Problem with Release 5.109.0 as we had with Release 5.106!
-
Please open a ticket so we can assist
-
@olivierlambert said in XOA fails after update to 5.106.0:
Please open a ticket so we can assist
This is XOA free which is failing once upgraded to 5.109, reporting as "Enterprise", but with an License Expiration Date of Dec 31, 1969!
Even if I am not paying for support, can I still file a Ticket?
-
This is XOA free which is failing once upgraded to 5.109, reporting as "Enterprise",
This one is really really weird. Yes, you can open a ticket with XOA Free, because we need the XO team to be able to track the problem and fix it.
-
@olivierlambert said in XOA fails after update to 5.106.0:
This is XOA free which is failing once upgraded to 5.109, reporting as "Enterprise",
This one is really really weird. Yes, you can open a ticket with XOA Free, because we need the XO team to be able to track the problem and fix it.
Unfortunately from the my XOA Free's Current State, I was informed from my Account I would be unable to file a Ticket without first contacting Vates, therefore I filed a Ticket via E-mail with support@vates.fr...
-
@Lhoust I checked but was unable to locate a new ticket from you. I recommend going to https://vates.tech/contact/ and submit your inquiry from there. Be sure to provide the support tunnel ID if possible.
-
@Lhoust This email is not monitored. But as Dan said, via the contact form you will be redirected.
-
FWIW, I've verified this bug on XOA Free when on the Latest release channel.
-
@Danp You mean going on Enterprise and beeing locked after?
-
@olivierlambert Correct, it switches to Enterprise and then locks up because there isn't a license attached. Switching to the Stable release channel resolves the issue so that it is again running a valid XOA Free.
-
haha that one is really weird. We'll make sure the XO team take a look at this tomorrow.
-
@Danp said in XOA fails after update to 5.106.0:
@olivierlambert Correct, it switches to Enterprise and then locks up because there isn't a license attached. Switching to the Stable release channel resolves the issue so that it is again running a valid XOA Free.
Correct switching back to the Stable Release or restoring V5.108.1 from a Backup works, although upgrading to V5.109 Locks in "Enterprise" Mode!
-
@Danp said in XOA fails after update to 5.106.0:
@Lhoust I checked but was unable to locate a new ticket from you. I recommend going to https://vates.tech/contact/ and submit your inquiry from there. Be sure to provide the support tunnel ID if possible.
Unfortunately I ONLY run XOA Free intermittently on my Main Desktop Computer and for some reason the Ticket I e-Mailed earlier ended up in my own INBOX???
Under these circumstances, I assume that I will be UNable to provide a Support Tunnel ID???
I have re-filed via the suggested Contact Form!!!
-
I just installed XOA at work and after updating to latest stable 5.108.1 i am facing the same error.
This is a fresh install in preparation to migrate from vpshere.
-
@olivierlambert Something Odd...
I am running XOA latest channel version: 5.109.0.... Today it asked me to allow an upgrade (not sure to what), so I did. The upgrade ran and disconnected me, as usual. Now all I see is
Cannot GET /after a damaged login page.So I SSH'd in to the OS and did a downgrade to the stable channel and then upgrade to the latest channel and it works again...
