I would be very grateful if anyone would be able to test 8.0 on the following CPUs:

E5520, E5540 and E5649

I unfortunatly dont have access to a test environment and is not able to do it myself..

So if anyone has any experiences with XCP 8.0 on these CPUs, I very interested in hearing your feedback

@pavelhr SSH to it and input the commands that way?

I can provide updates from my side

As of now http works for me and https dosent.

On mobile/iPad:

Https:

Http:

On my Macbook:

Https:
https://drive.google.com/file/d/1c4baU0OsZ3d22yGdjxogO5S7_jAQg9jg/view?usp=sharing

For some reason I cant upload the image for the https, so heres a google link for it

Http:

Maybe its a cert issue?

I have tried on both latest and stable.. xo plugin still fails

But now I can see all my SR

I have done that now.. How to I move my license to the new install?

It says its bound to another XOA

Yeah.. I cant do that

EDIT: I created the ticket

I also cant do the "XOA check" on the support page.. getting "method not found: xoa.check"

XOA, im on the latest channel

I updated before trying again.. same issue.. However I cant seem to load the xo plugin.. It throws this error:

Xo#requestResource is already defined

Dunno if that is affecting anything..

Theres no output in console when I try and access the affected SR, I just hangs again

I have a wierd problem..

I have 5 SR connected to 2 pools (SR 1+2 on pool 1 and SR 3-5 on pool 2)..

I cant access one of the SR from XOA.. The browser just freezes and locks completely.. Only way to get i working again is to close the tab and open a new one..

This has been testes on Chrome, Edge and Firefox on both http and https.. The behaviour is the same across all browsers.. and it only the one SR, all the other show just fine...

Are the any logs I can try and probe to find a root to the problem?

Well, I will try and test if its the VPN, next time im in the office.. But from what I remember its the same when connected directly to the local network..

Okay, so wierdly it works over http, but not over https.. Is that intended?