XOA web deploy stuck at "Deploying XOA..." No error
-
I tried downloading the xoa_unified.xva file from https://xen-orchestra.com/#!/member/products via Chrome web browser but got the same extremely slow download results. Again, doesn’t seem to be my slow 7 Mbps WISP connection that is the problem. I’m still having no issue downloading very large files from other sites. Using an alternative wireless internet connection I was able to download the .xva in just a few minutes. I’ll SCP it over to the XCP-ng server and try the manual install process.
Thanks for your help with this issue. -
So it's clearly a peering issue between your landline provider and where the file is hosted (in Europe).
I'm not 100% surprised, some US providers got very bad peering with Europe.
-
yeah so ive been jerked around by this for 3 hours now,
this definitely needs to be more public?
whats the solution?
im suprised you dont have a torrent link
-
Not everyone is affected, and not everytime either. Otherwise, we would already have done something. As you can see, it's pretty calm here since 6 months.
That's why it went down in our backlog. For our next XOA release (a fresh new virtual appliance with everything already updated) will be likely released with a US based mirror.
-
@olivierlambert I'm having this issue based in USA Midwest any good guides to a fix/ work around here in 2025?
-
Hi @RawbDeeni
I'm not aware of such recent issues in here, you are the first to come here since 2022. One can assume there's some variation on peering capabilities, it's not bad enough so we had to prioritize. What's your symptoms?
-
@olivierlambert I have 5gig fiber to my house with a static ip and my server doesn't deploy xoa like in this thread. I went into the host itself and can confirm they get created but fail to run but I was able to force start one but didn't do anything
-
@RawbDeeni
Can your XCP host ping xoa.io? -
@Davidj-0 ping xoa.io aPING xoa.io (185.78.159.93) 56(84) bytes of data.
64 bytes from 185.78.159.93: icmp_seq=2 ttl=50 time=220 ms
64 bytes from 185.78.159.93: icmp_seq=3 ttl=50 time=187 ms
64 bytes from 185.78.159.93: icmp_seq=4 ttl=50 time=195 ms
64 bytes from 185.78.159.93: icmp_seq=7 ttl=50 time=187 ms
64 bytes from 185.78.159.93: icmp_seq=8 ttl=50 time=193 ms
64 bytes from 185.78.159.93: icmp_seq=9 ttl=50 time=199 ms
64 bytes from 185.78.159.93: icmp_seq=10 ttl=50 time=202 ms
64 bytes from 185.78.159.93: icmp_seq=11 ttl=50 time=199 ms
64 bytes from 185.78.159.93: icmp_seq=14 ttl=50 time=205 ms
64 bytes from 185.78.159.93: icmp_seq=15 ttl=50 time=205 ms
64 bytes from 185.78.159.93: icmp_seq=16 ttl=50 time=205 ms
64 bytes from 185.78.159.93: icmp_seq=17 ttl=50 time=182 ms
64 bytes from 185.78.159.93: icmp_seq=18 ttl=50 time=207 ms
64 bytes from 185.78.159.93: icmp_seq=20 ttl=50 time=193 ms
64 bytes from 185.78.159.93: icmp_seq=21 ttl=50 time=207 ms
64 bytes from 185.78.159.93: icmp_seq=22 ttl=50 time=196 ms
^C
--- xoa.io ping statistics ---
23 packets transmitted, 16 received, 30% packet loss, time 28927ms -
@RawbDeeni also what is zen center for windows the link seems to be broken
-
@olivierlambert I finally got some more time to try working on this, 8.3 worked out of the box and fixed the issues I was having on 8.2
-
That's weird, likely unrelated eg peering unstuck after a bit and worked later
Anyway, happy it works for you, thanks for the mirror reminder, I will try to prioritize this in the next months
-
@RawbDeeni Thank you! I had the same problem using 8.2 lts. I ended up formatting and using 8.3, and I didn't have any issues after that. I'm glad I found a better alternative to use this hypervision from a vmware end user for over 10 years until Broadcom killed it.
