Skip to main content

FAQ

How should Analytics API and Insight API communicate?​

For on-premises installations, you host the services yourself. Based on standard practice for web services and certificates, we recommend one of these options:

  • Same server: Install Analytics API on the same server as Insight API. They then communicate locally.
  • Separate servers: Set up HTTPS certificates between the servers, as in any standard server setup.

For both options, we recommend a reverse proxy (for example nginx on Linux or IIS on Windows):

  • Let Analytics API listen only on localhost.
  • Set up HTTPS in the reverse proxy.
  • Route all requests through the proxy.

A minimal nginx example, with your own host name and certificate:

server {
    listen 443 ssl;
    server_name analytics.example.local;
    ssl_certificate     /etc/nginx/certs/analytics.crt;
    ssl_certificate_key /etc/nginx/certs/analytics.key;

    location / {
        proxy_pass http://127.0.0.1:9090;
    }
}

The setup you choose decides the URL of the API.

Windows installation: I get an error when running the installation​

Error message:

Error: project execution failed, consider restoring from scratch

Caused by:
    The system cannot find the path specified. (os error 3)

Make sure the last folder in the installation directory you chose does not already exist.

Windows installation: Can I use something other than NSSM?​

Yes. The automatic installation and running described in the Windows Installation guide requires NSSM. If you run the .exe file without any commands, the service starts in your terminal, so you can run it with any service manager you prefer.