Xen Orchestra SMB Remote problem
-
No, this is a single server, in a lab, in a workgroup. Connecting from the XO Web interface does nothing at all. No error message on the screen. If I open developer tools in Chrome, it shows me a little more about what's happening. see below.
ebSocket connection to 'ws://192.168.1.246/api/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED t {message: "invalid status closed, expected open", name: "t"} message : "invalid status closed, expected open" name : "t" stack : (...) get stack : stack() set stack : stack() __proto__ :rSo every time I click the connect button in the web UI of XO, it seems to restart XO server. Then the only other message that I see that gives me a clue is : xo:api (unknown user) | session.signIn(...) [3ms] ==> object. Full output below.
Oct 04 08:48:44 xeno systemd[1]: xo-server.service: Service hold-off time over, scheduling restart. Oct 04 08:48:44 xeno systemd[1]: Stopped XO Server. Oct 04 08:48:44 xeno systemd[1]: Started XO Server. Oct 04 08:48:46 xeno xo Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xo:perf blocked for 161ms Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xo:main + WebSocket connection (::ffff:192.168.1.41) Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xo:perf blocked for 33ms Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xo:perf blocked for 12ms Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xo:perf blocked for 69ms Oct 04 08:51:07 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:07 GMT xen-api [email protected]: event.from(...) [2s] ==> object Oct 04 08:51:08 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:08 GMT xo:perf blocked for 258ms Oct 04 08:51:08 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:08 GMT xo:api (unknown user) | session.signIn(...) [3ms] ==> object Oct 04 08:51:08 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:08 GMT xen-api [email protected]: event.from(...) [33ms] ==> object Oct 04 08:51:08 xeno xo-server[20453]: Tue, 04 Oct 2016 12:51:08 GMT xo:api -
Without providing the password; what do you have in your SMB connection setting?
You were able to connect to the SMB share from the XO console right?
-
In the CLI of the VM where XO is installed:
smbclient //192.168.1.200/xsbackups -U xenbackups
Then of course I'm prompted for the password and it connect immediately.
-
@fuznutz04 I assume you meant to use \
It's odd that this works from the CLI but not the web interface.
In the address field which is proceeded by
\\and then<address\share>*are you typing in the double\\or just putting in "192.168.1.200\xsbackups"?
-
Or are you putting in just the ip address of the server, and in the following field putting in the folder?
-
It will only allow you to put in the correct format of IP\Share. So in this example, i only put in 192.168.1.200\xsbackups. xsbackups is the name of the SMB share.
I keep looking at this connection refused error. It makes me think it is something specifically with the web interface, or that the API is not working properly.
-
It might be a bug that needs to go up to @olivier to take a look at.
-
Please put a screenshot here with how you filled those fields.
-
mrfusion is the name of my desktop where the share is located. I also tried putting in the workgroup name in that field instead of the PC name.
-
Opening Chrome developer tools gives me these messages when trying to either add the remote share.
-
It seems you have side issues with connection between you browser and the server. Are you in HTTPS?
-
@olivier said in Xen Orchestra SMB Remote problem:
It seems you have side issues with connection between you browser and the server. Are you in HTTPS?
No, I'm not using HTTPS. I've tried from both Safari as well as Chrome so far from multiple computers. I've also disabled the firewall completely on the XO box just to rule that out. Still having the same issue,
-
Even antivirus software are a pain with websocket protocols. That's why we recommend to go in HTTPS before going further in debug.
-
@olivier said in Xen Orchestra SMB Remote problem:
Even antivirus software are a pain with websocket protocols. That's why we recommend to go in HTTPS before going further in debug.
Is HTTPS supposed to be configured during the installation of XO? I cant connect if I try to connect via HTTPS. Are there instructions available regarding how to set that piece up? Thanks for your help!
-
Yes, XOA is bundled with certs (autosigned but still).
Anyway, doc is here: https://xen-orchestra.com/docs/configuration.html
-
@olivier said in Xen Orchestra SMB Remote problem:
Yes, XOA is bundled with certs (autosigned but still).
Anyway, doc is here: https://xen-orchestra.com/docs/configuration.html
I installed using the installation script below, so I didn't use the appliance.
sudo curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bashI'll take a look at that documentation and give see if that will make a difference and report back.
-
So circling back to this, I was determined to add an SMB remote backup share. Instead of adding a remote SMB backup share through XO, I just mounted the SMB share through Ubuntu where XO is installed. In this case, I mounted to /Backups. Then setup a "local" remote in XO that points to /Backups. Backups are now running and being stored on a remote computer.
-
@fuznutz04 said in Xen Orchestra SMB Remote problem:
So circling back to this, I was determined to add an SMB remote backup share. Instead of adding a remote SMB backup share through XO, I just mounted the SMB share through Ubuntu where XO is installed. In this case, I mounted to /Backups. Then setup a "local" remote in XO that points to /Backups. Backups are now running and being stored on a remote computer.
Awesome.
