We use cookies to remember your language choice. By using our websites you accept this in accordance with the Cookie section in our Privacy Statement.
Accept
We use cookies to remember your language choice. By using our websites you accept this in accordance with the Cookie section in our Privacy Statement.
Accept

3. Preconfiguration

The package contains a configuration script that will generate all required configuration files depending on the properties you set.

3.1 Define variables

Open the configuration file and set the desired values for the variables listed below (General, Maintenance page, and Email):

nano config.inc

The file doesn’t contain any predefined values so you need to set them all on your side. The commented lines (starting with #) feature example values. The first part (mandatory parameters) is required at all times. Optional parameters may be set later (step 4).

Available parameters and respective property names are:

Mandatory parameters

  • Hub base URL (RXGW_BASE_URL)
    URL to be used to generate all Hub-related links.
    IMPORTANT: For the first launch, you need to set the scheme to HTTP: http://your_hostname. Mind that it should NOT have a slash at the end.
     Once you reach the maintenance page, it is recommended to change the scheme to HTTPS.

Once set up and launched, you will perform any further configuration and repairs on the maintenance page accessible at RXGW_BASE_URL:RXGW_MAINT_PORT/maint/.

  • Maintenance page port (RXGW_MAINT_PORT)
    The most commonly used port value for it is 8080. You may also consider closing this port on the firewall to prevent any third-party access.
  • Maintenance page credentials (RXGW_MAINT_USER) and (RXGW_MAINT_PASS)
    Username and password to access the maintenance page.

Optional parameters

You may choose to set these parameters now or set them later on the maintenance page. If set before the first launch, the server will use the values set here. Once the maintenance page is up and running, any change will rewrite this config with the values you set on the maintenance page.

  • Hub site title (RXGW_HUB_NAME)
    This string will serve as a title for your Remotix Gateway website.
  • Mailing parameters
    Remotix Hub relies on the mailing service to send registration confirmation emails, daily reports, computer state alerts, etc. You may also skip this part and leave all email settings blank. In this case, your local Hub will be unable to send any emails.
    • Mail server address (RXGW_SMTP_SERVER)
      A fully qualified domain name of your mailing server. Must include the port.
    • Sender address (RXGW_SMTP_FROM)
      Email address to place to the “From: ” field for all emails sent by your local Hub.
    • Sender username (RXGW_SMTP_USERNAME) and Sender’s email password (RXGW_SMTP_PASSWORD)
      Credentials used to authorize on the mailing server.
    • Enforced TLS option (RXGW_SMTP_USE_TLS)
      May be set to true or false, depending on whether your mailing server enforces TLS encryption or not.
  • Single Sign-On
    If you want your users to log in to Remotix Hub with Google SSO, you also need to specify the Google SSO key and Google SSO secret.
    • Google SSO key (RXGW_SSO_GOOGLE_KEY)
      Client ID from Google Cloud console.
    • Google Secret (RXGW_SSO_GOOGLE_SECRET)
      Client Secret from Google Cloud console.

Once ready, save the file and exit the editor.

3.2 Apply the defined variables

When ready, run the script to update the server’s configuration and relaunch all dependent components:

./configure.sh

Next ⟶

3.3 Advanced fine-tuning

If you happen to need an uncommon configuration and need to customize it further, you may need to edit other configs as well.

The config which you have just set is located at /var/nulana/rxgateway/etc/config.inc. It serves as a base for all other configuration files:

  • /etc/nginx/conf.d/rxgateway.conf
  • /var/nulana/rxgateway/etc/runtime.conf
  • /var/nulana/rxgateway/etc/static.conf
  • /var/nulana/rxgateway/etc/tunnel.conf.inc
  • /var/nulana/rxgateway/bin/run_tunnel.sh

You may also choose to not set up HTTPS and use less secure HTTP instead and port 80 instead of 443. Note that it will NOT work for clients running macOS 10.11 and will also require an internal domain or IP instead of a public domain (here is why). If you decide to go this way, contact our support for advanced guidance on how to set the backend to use HTTP.

Next ⟶