Cannot connect to QS Engine

[mountaindude]

When opening the mashup, no apps are shown, the green circle keeps spinning and next to it says "No active document".

I am already authenticated with Sense (Enterprise) on the same server where the Backup and Restore extension is running, but for some reason no connection is established to the QS Server.

Looking at the developer console in Chrome, a couple of errors are reported:

extensions::messaging:65 Uncaught Error: Attempting to use a disconnected port objectPortImpl.postMessage @ extensions::messaging:65target.(anonymous function) @ extensions::SafeBuiltins:19publicClass.(anonymous function) @ extensions::utils:94(anonymous function) @ cleekiagent.js:8555

qsocks.bundle.js:162 WebSocket is already in CLOSING or CLOSED state.(anonymous function) @ qsocks.bundle.js:162tryCallTwo @ qsocks.bundle.js:1940doResolve @ qsocks.bundle.js:2066Promise @ qsocks.bundle.js:1960Connection.ask @ qsocks.bundle.js:156Global.getDocList @ qsocks.bundle.js:1256(anonymous function) @ backup-and-restore.js:457tryCallOne @ qsocks.bundle.js:1932(anonymous function) @ qsocks.bundle.js:1998flush @ qsocks.bundle.js:2648drainQueue @ qsocks.bundle.js:1849

[rachelehughes]

I am having the same problem. Help!!

[countnazgul]

Sorry guys somehow missed the notifications. Which version of the mashup you are using? (you can see the version in the mashup itself in the top right corner)

[mountaindude]

@countnazgul

Using 0.9.3, steps I've taken:

1. install the ZIP file found inside the zip downloaded from GitHub
2. Use the Dev-Hub to find the extension, it shows up nicely there with an icon and everything.
3. Opening it works fine, but then it fails to connect to the server, with the symptoms described above.

I can email you a screen shot etc if needed (let me know your email address if so)

[rachelehughes]

I am also using 0.9.3. I used the Developer Tools in Chrome to trap the error and I’m getting a socket error. We are using https for the site and our certificate wasn’t signed by a CA. I’m wondering if this is the problem.

Thoughts?

Thanks! Rachel

On Feb 19, 2016, at 1:40 AM, mountaindude [email protected] wrote:

@countnazgul https://github.com/countnazgul Using 0.9.3, steps I've taken:

1. install the ZIP file found inside the zip downloaded from GitHub
2. Use the Dev-Hub to find the extension, it shows up nicely there with an icon and everything.
3. Opening it works fine, but then it fails to connect to the server, with the symptoms described above.

I can email you a screen shot etc if needed (let me know your email address if so)

— Reply to this email directly or view it on GitHub https://github.com/countnazgul/QS-backup-and-restore-app/issues/2#issuecomment-186118698.

[mountaindude]

We have a proper commercial cert, and still get that error.

Göran

On 19 Feb 2016, at 14:41, rachelehughes [email protected] wrote:

I am also using 0.9.3. I used the Developer Tools in Chrome to trap the error and I’m getting a socket error. We are using https for the site and our certificate wasn’t signed by a CA. I’m wondering if this is the problem.

Thoughts?

Thanks! Rachel

On Feb 19, 2016, at 1:40 AM, mountaindude [email protected] wrote:

@countnazgul https://github.com/countnazgul Using 0.9.3, steps I've taken:

1. install the ZIP file found inside the zip downloaded from GitHub
2. Use the Dev-Hub to find the extension, it shows up nicely there with an icon and everything.
3. Opening it works fine, but then it fails to connect to the server, with the symptoms described above.

I can email you a screen shot etc if needed (let me know your email address if so)

— Reply to this email directly or view it on GitHub https://github.com/countnazgul/QS-backup-and-restore-app/issues/2#issuecomment-186118698.

— Reply to this email directly or view it on GitHub.

[rachelehughes]

We now have a commercial certificate and we still aren’t getting any response.

The value in URI is "wss:///local/app/%3Ftransient%3D"

Any more progress?

Thanks! Rachel

On Feb 19, 2016, at 7:24 AM, mountaindude [email protected] wrote:

We have a proper commercial cert, and still get that error.

Göran

On 19 Feb 2016, at 14:41, rachelehughes [email protected] wrote:

I am also using 0.9.3. I used the Developer Tools in Chrome to trap the error and I’m getting a socket error. We are using https for the site and our certificate wasn’t signed by a CA. I’m wondering if this is the problem.

Thoughts?

Thanks! Rachel

On Feb 19, 2016, at 1:40 AM, mountaindude [email protected] wrote:

@countnazgul https://github.com/countnazgul Using 0.9.3, steps I've taken:

1. install the ZIP file found inside the zip downloaded from GitHub
2. Use the Dev-Hub to find the extension, it shows up nicely there with an icon and everything.
3. Opening it works fine, but then it fails to connect to the server, with the symptoms described above.

I can email you a screen shot etc if needed (let me know your email address if so)

— Reply to this email directly or view it on GitHub https://github.com/countnazgul/QS-backup-and-restore-app/issues/2#issuecomment-186118698.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/countnazgul/QS-backup-and-restore-app/issues/2#issuecomment-186234847.

[countnazgul]

Just finished some testing and still can't see why its not working. Tested it no 3 different sense server installations and started from the first time.

In the chrome dev tools if you click on the %3Ftransient%3D what is shown under the Frames tab? Any weird/error messages?

Stefan

[rachelehughes]

I am getting:

The webpage at wss:///app/%3Ftransient%3D might be temporarily down or it may have moved permanently to a new web address.

—R

On Feb 22, 2016, at 2:24 PM, Stefan Stoichev [email protected] wrote:

Just finished some testing and still can't see why its not working. Tested it no 3 different sense server installations and started from the first time.

In the chrome dev tools if you click on the %3Ftransient%3D what is shown under the Frames tab? Any weird/error messages?

Stefan

— Reply to this email directly or view it on GitHub https://github.com/countnazgul/QS-backup-and-restore-app/issues/2#issuecomment-187389071.

[mountaindude]

@countnazgul: We are using SAML authentication, if that makes a difference..

[rachelehughes]

We have gotten past this error but the app list is still not populating. Any additional thoughts?

[rachelehughes]

It seems like it is redirecting us to our single sign on page without passing on the authentication tokens. To get to the hub, for instance, we need "https://localhost/local/hub". Without "local" in the url, it will redirect you to an SSO page. Do we need to similarly alter the code somehow to incorporate this in the web socket URI?

[countnazgul]

Yea ticket is not passed. I'll make the change this weekend and bring the ticket to the picture. Need to check about the "local"

[countnazgul]

The main js file is updated. If ticket is present, after the authentication, it will be passed to qSocks and all web socket requests will benefit from this afterwards.

[mountaindude]

@countnazgul, sorry - still no luck. Getting that same spinning green circle, and "No active document" message.

The JS console shows this:

qsocks.bundle.js:162 WebSocket is already in CLOSING or CLOSED state.(anonymous function) @ qsocks.bundle.js:162tryCallTwo @ qsocks.bundle.js:1940doResolve @ qsocks.bundle.js:2066Promise @ qsocks.bundle.js:1960Connection.ask @ qsocks.bundle.js:156Global.getDocList @ qsocks.bundle.js:1256(anonymous function) @ backup-and-restore.js:480tryCallOne @ qsocks.bundle.js:1932(anonymous function) @ qsocks.bundle.js:1998flush @ qsocks.bundle.js:2648drainQueue @ qsocks.bundle.js:1849

Happy to send a screen shot over email if that helps debugging things. Also, I am using a SAML authenticated Sense 2.1.1 system. If you rely on webtickets, that might be the issue..?

[countnazgul]

can you send me the screenshot/copy paste of the response in the dev console - the Frames tab against the "3Ftransient%3D" row? you can mail me at [email protected]

[rachelehughes]

Any updates? Still not working for us.

[fallonchen]

I work with @mountaindude and wanted to follow up on the issue reported. We're still getting the "no active document" error. I just emailed you a screenshot of the Frames tab agains the "3Ftransiend%3D" row, in case it is helpful. Let me know if there's anything else you need to know.!