topic Re: Mashup API: external webserver and websocket issue in Integration, Extension & APIs

Mashup API: external webserver and websocket issue

Fri, 16 Sep 2016 11:31:32 GMT

Hi,

We are trying to move a mashup developed on a Sense server to a external webserver.

All settings from Mashup API reference seems correct:

var config = { host: "sense.ourhost.com", prefix: "/", port: 443, isSecure: true };

But when we try to load an app by appid we get a websocket error:

Error during WebSocket handshake: net::ERR_CONNECTION_RESET

The domain of the external page is whitelisted in the Sense proxy settings.

Has anyone encountered this issue?

Thansk!

//Daniel

Re: Mashup API: external webserver and websocket issue

Francis_Kabinoff — Fri, 16 Sep 2016 17:33:56 GMT

What version of Sense are you using?

Re: Mashup API: external webserver and websocket issue

Sat, 17 Sep 2016 09:48:06 GMT

We are using sense 3.0.

Re: Mashup API: external webserver and websocket issue

Alexander_Thor — Mon, 19 Sep 2016 02:21:34 GMT

And you are authenticating your users properly?

Are you using the self-signed certificates that come out of the box? Some browsers and security settings are not keen on loading resources from a external site with self-signed certificates

Re: Mashup API: external webserver and websocket issue

Francis_Kabinoff — Mon, 19 Sep 2016 13:51:11 GMT

There's a bug in sense 3.0.0 surrounding external mashups. So if you are using 3.0.0, I suggest you upgrade to 3.0.1

Re: Mashup API: external webserver and websocket issue

Thu, 06 Oct 2016 14:44:56 GMT

So just to update you on the issue:

It seems the problem was an issue with the Mashup location and secure traffic over https to the Sense server. After reinstalling the certificates all works fine.

Re: Mashup API: external webserver and websocket issue

oknotsen — Wed, 04 Apr 2018 11:55:08 GMT

Are there more versions with this bug? Any version of the February 2018 edition for example?

I am getting the same "net::ERR_CONNECTION_RESET" and want to know if I am hunting a ghost or made an actual mistake.

I have added the IP address of the machine I am testing / developing with to the Host white list.