Closed RickCordero closed 3 years ago
Hi,
This script doesn't do anything to the embedded webserver in Xen Orchestra which might cause something like this. Tested this and can't reproduce with iOS safari/firefox/chrome. My best bet is that this is something to do with the old installation you did by hand and new one with this script and having something cached in your mobile browsers if you're accessing the Xen Orchestra with same URL.
You should continue to debug this with browser developer tools (if available for your mobile browser) and try to do the obvious, as in clear browser history/cache and see if it helps.
Anyway this is something that's out of scope of this script since it doesn't touch parts that might cause behaviour like this. I'll keep this open for a moment if you give more information about the matter, but i'm afraid there's not much i can do.
Good morning, Thank you for your quick reply. After reading your response I created two fresh Debian 10 VMs. One with self-generated SSL certs and one without ssl certs.
Good morning,
Thank you for your quick reply. I think the problem lies with my self-generated X.509 cert.
After reading your response I decided to create two fresh Debian 10 VMs. On one Debian VM I generated X.509 certs, changed the port from 80 to 443, and inputted the path to both the cert & key in xo-install.cfg (Fig 1). I left the other Debian VM with the standard configs (no X.509, port 80, etc). The VM that has the X.509 cert gives me the “still loading” problem when I log into the web interface on my iPad (Fig 2). I have no problems when I log into the web interface that has no X.509 cert (Fig 3). With this new information do you have any further suggestions or is this still out of scope?
Side note: I use this for my simple home lab so nothing mission critical. I just want to learn and fix errors. Let me know if/how to donate money to you.
Fig 1
Fig 2
Fig 3
On Mar 13, 2021, at 2:58 AM, Roni Väyrynen @.***> wrote:
Hi,
This script doesn't do anything to the embedded webserver in Xen Orchestra which might cause something like this. Tested this and can't reproduce with iOS safari/firefox/chrome. My best bet is that this is something to do with the old installation you did by hand and new one with this script and having something cached in your mobile browsers if you're accessing the Xen Orchestra from same URL.
You should continue to debug this with browser developer tools (if available for your mobile browser) and try to do the obvious, as in clear browser history/cache and see if it helps.
Anyway this is something that's out of scope of this script since it doesn't touch parts that might cause behaviour like this. I'll keep this open for a moment if you give more information about the matter, but i'm afraid there's not much i can do.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ronivay/XenOrchestraInstallerUpdater/issues/69#issuecomment-797892808, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMJCO54BOZ2GG2TCDZR2G63TDMLLZANCNFSM4ZDKW6FA.
Hi,
Thank you very much, this helped to debug this further. I was able to reproduce this myself and it is indeed a websocket error when connecting to Xen Orchestra using HTTPS. Did a bit of research and this is a safety feature at least with iOS that it doesn't allow websocket connections with self-signed certificates. So not really other fix at this point except use a "real" certificate or go with HTTP if you otherwise have a safe connection to the server.
I haven't really thought of having a donate option, should i ? :D
Well, I am glad I am not crazy. lol! I am going to try and load a Let’s Encrypt cert into a new XO VM.
Yes, you should. There are plenty of secure ways for followers to donate. Your hard work should be rewarded.
Best,
Rick
On Mar 13, 2021, at 2:06 PM, Roni Väyrynen @.***> wrote:
Hi,
Thank you very much, this helped to debug this further. I was able to reproduce this myself and is indeed a websocket error when connecting to Xen Orchestra. This is actually a safety feature at least with iOS that it doesn't allow websocket connections with self-signed certificates. So not really other fix at this point except use a a "real" certificate or go with HTTP if you otherwise have a safe connection to the server.
I haven't really thought of having a donate option, should i ? :D
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ronivay/XenOrchestraInstallerUpdater/issues/69#issuecomment-798769041, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMJCO57BLZ4Y4U53UO35C2TTDOZSXANCNFSM4ZDKW6FA.
OS Version: Debian 10 Node.js version: v14-16.0 Yarn version: 1.22.4
Server specs 2vCPU & 6GB RAM
Issue I get a "Still loading" after logging into the web interface via my iPhone or iPad. It loads and works perfectly on my MacBook. I use Firefox on all three platforms. I did compiled XO via the documentation and had the ability to use XO on my iPhone or iPad; however, I prefer Ronivay's approach.
Installation logfile
xo-server.service log