7.2 SSL Connect to local Elasticube from Elasticube Manager
With 7.2 and SSL enabled on port 443, from the Elasticube Manager, how do you connect to an existing Elasticube on the local host from the "Add Data" button? I've tried a variety of choices in the "Database Server Location" without any luck,
localhost:8081
localhost:443
localhost:27018
localhost:14996
None of these connect
Thank you,
Tom
-
Same issue here. The "Sisense ElastiCube Connector" and the documentation for importing elasticube data, https://documentation.sisense.com/latest/managing-data/connectors/sisense-elasticube.htm, is not clear what is meant by "database server location", "address of your elasticube", or "the port you changed" (there are many ports that can be changed??). Best guess is "Gateway service" was intended here, according to https://documentation.sisense.com/latest/getting-started/communication-ports.htm and the reference to port 8081.
I worked around the issue by disabling SSL on Sisense, and adding an SSL-enabled reverse proxy server to Sisense services. Here are the steps I used, though IIS can be used in place of nginx:
- Disable SSL on Sisense and move Sisense gateway to a private port, e.g. 12345
- Install nginx
- Configure nginx to forward requests to Sisense gateway (sample configuration below)
- Configure SSL on nginx
- Wrap nginx into a windows service (via winsw, for example)
Sample nginx configuration:
server {
listen 443 ssl;
server_name data.example.com;
ssl_certificate /path/to/cert.crt;
ssl_certificate_key /path/to/cert.pem;
location / {
proxy_pass http://data.example.com:12345/; # hosts file maps FQDN to 127.0.0.1
proxy_http_version 1.1;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
}
Please sign in to leave a comment.
Comments
3 comments