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.
-
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...
-
@acebmxer Did you activate your License?
Click on XOA then Licenses (at the top). Make sure you seeThis license is active on this XOA -
said in XOA fails after update to 5.106.0:
@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!!!
Today I also saw there were Updates Available, which also left my Web Interface unusable and therefore I was unable to provide a Support Tunnel ID from the Web Interface. I finally figured out the "Correct" Syntax for the CLI and Yannick was able to fix both the non-Functional Web Interface and yesterday's "Locked" in "Enterprise" Mode! I do NOT know how those were corrected??
Today I tried upgrading a second XOA Free from V5.108.1 to V5.109 and this Instance did NOT fall into the same "Enterprise" Lock as yesterday's Upgrade???
-
@Andrew said in XOA fails after update to 5.106.0:
@acebmxer Did you activate your License?
Click on XOA then Licenses (at the top). Make sure you seeThis license is active on this XOAYes in 5.105.0 (fresh install) it worked. When i upgrated to 5.108.1 it stoped. I tried v5.109 and failed. same as @Lhoust
Using XO from sources for the moment.
-
Forgot to add:
According to Yannick there will be a Release Next Week, to Fix this Issue!
-
A acebmxer referenced this topic
-
said in XOA fails after update to 5.106.0:
Forgot to add:
According to Yannick there will be a Release Next Week, to Fix this Issue!
Today I upgraded XOA Free to 5.109.1 and found it was functioning "Normally"!
-
Excellent! Thanks for the feedback
Making this thread as "solved"!
edit: already done in fact
-
I don't think it's the same issue. Originally, you ended on a white page with "Cannot get /". It seems unrelated here, right?
-
@olivierlambert said in XOA fails after update to 5.106.0:
I don't think it's the same issue. Originally, you ended on a white page with "Cannot get /". It seems unrelated here, right?
Yeah i think i have moved passed the original issue onto this issue. That is why I stated you can move this to its own thread if need be. Or I can open a support ticket now that is usable.
-
I will create a new thread from your message
