Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

Can not connect to Plugin from QlikSense Nodes / other Host #36

Open
sirpod opened this issue Apr 25, 2018 · 3 comments
Open

Can not connect to Plugin from QlikSense Nodes / other Host #36

sirpod opened this issue Apr 25, 2018 · 3 comments

Comments

@sirpod
Copy link

sirpod commented Apr 25, 2018

Description

Can not connect to Plugin from QlikSense Nodes

Steps to Reproduce

  1. Change gRPC host in SSEtoRserve.exe.config to "0.0.0.0"
  2. Restartet SEE-plugin
  3. Restartet QlikEngine
  4. Opend port 50051 (from config)
  5. Analytic connection still works with host:localhost
  6. Changed host in analytics connection to server name and domain
  7. Restarted Engine
Expected behavior

With the change config, opend port and specific host, R should be working from all nodes and not only the central node where the plugin is runnig on

Actual behavior

After changing the host address to server and domain name (myserver.domain.com), R plugin dosen't work at all.
When changing it back to localhost, it works again from the central node

Environment

Operating system where the SSE plugin is deployed
[x] Windows Server 2012 R2
[ ] Linux
Qlik Sense
[ ] Desktop
[ x] Server

Versions

  • sse-r-plugin: v1.2.1
    testet on Qlik Sense Feb 2017 & QlikSense Apr 2018

Regards Tobias

@tobiaslindulf
Copy link
Contributor

Hi, if it works on the same machine as the SSE Plugin is located on, then the problem got to be related to network access, routing or firewall settings.
-Are you able to ping the servername.domainname address from a cmd prompt?
-What happens if you use the ip number instead of the servername.domainname?
-Check the firewall settings in the machine where the SSE plugin is located.

@konne
Copy link

konne commented Apr 26, 2018 via email

@sirpod
Copy link
Author

sirpod commented Apr 30, 2018

Hello Tobias,
thanks for your help.

I tried different domains names like IP, DNS & URL but nothing helped.

In the end I had issues with the used certificates.
I created them new with a diffenrt sse_server_config.cfg and a modified open_ssl_config.exe.cfg

Further more I shared the folder with the created certificates to all nodes and viola, it's working :)

Regards Tobias

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants