The web server of Linkurious delivers the application to end users through HTTP/S.
It is configured in the
server configuration key within the configuration
3000): The port of the web server
Some firewalls block network traffic ports other than
root users can listen on ports lower than 1024,
you may want reroute traffic from
3000 as follows:
sudo iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 3000
If you use SSL, you can add a second rule to redirect
sudo iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-port 3443
"localhost"): The domain or sub-domain used to access the web server. It is mandatory to edit it for publishing visualizations online. It is also used to restrict the validity of cookies to a domain or sub-domain.
listenPort): The public HTTP port of the web server.
listenPortHttps): The public HTTPS port of the web server.
In some cases, Linkurious needs to generate links to itself (for example when generating a link to a widget). For that, the server needs to know its public domain and port to generate those links.
The public port can be different from the actual port if you use traffic rerouting
(using a firewall or a reverse-proxy). In the example above (traffic rerouting),
the actual HTTP port (
3000, but the public HTTP port (
cookieDomain(optional): Set this value if you need your cookie to be set fo a domain different from
"*"): Define the cross-origin resource sharing (CORS) policy. Accept cross-site HTTP/S requests by default. The value can be:
- a string (
"abc.com"): only requests from "abc.com" domain are allowed.
- wildcard-prefixed string (
"*.abc.com"): request from all sub-domains of
- an array of strings (
["abc.com", "*.def.com"]): requests from
abc.comand all sub-domains of
- a single wildcard (
"*"): requests from any domain are allowed.
- a string (
"anonymous"): Restrict the origin of images displayed in visualizations to prevent running malicious code on the graphic card of users. Display images from any origin by default. Read here to learn more.
3443): The port of the web server if HTTPS is enabled. See the Install section to learn why you should not set
false): Encrypt communications through HTTPS if
true. Require a valid SSL certificate.
false): Force all traffic to use HTTPS only if
true. The server will redirect HTTP
GETrequests to HTTPS and reject all other HTTP requests.
certificateFile: The relative path to the SSL certificate (must be located within the
certificateKeyFile: The relative path to a public key of the SSL certificate (must be located within the
certificatePassphrase: The pass-phrase protecting the SSL certificate.
External communications with the Linkurious server can be secured using SSL without installing third-party software.
If the Linkurious server, graph database, and the search index are installed on different machines, we recommend using secure communication channels between these machines (e.g. HTTPS or WSS). Please refer to the data-source documentation and search index documentation to learn how to enable HTTPS.
To use custom Certificate Authorities (CA), please check how to use additional Certificate Authorities in Linkurious.