4. Configuration (maintenance page)
Once configure.sh finishes its work, you should see the message:
Configuration finished, please proceed to maintenance page: [...]
From this point, you can make all adjustments using the maintenance page located at the URL shown in the message (RXGW_BASE_URL:RXGW_MAINT_PORT/maint/
).
Please mind that most changes you can make on the maintenance page require the backend to relaunch. Be sure to wait for it to get back up.
4.1 Place license file
For a trial, please request a license file from the support team.
- Find a block named Provisioning.
- Click an Import provisioning button.
- In the pop-up window, choose a provisioning file (usually named provisioning.b64). You should see its contents in the field below.
- Click Import button and close the window once done.
- If applied successfully, you will see your instance ID, license expiration date and maximum number of clients and agents allowed to use your local cloud.
In your OS, you may find the imported file at /var/nulana/rxgateway/etc/provisioning.b64
.
4.2 Set HTTPS
To provide the proper level of security, it is strongly recommended to use the HTTPS scheme– which requires a valid TLS certificate.
- Scroll down to a block named HTTPS.
- In the pop-up window, click Import TLS certificate.
- Choose private key and full certificate chain files.
E.g., if you use Let’s Encrypt for certificate generation, the private key would beprivkey.pem
, and the chain would befullchain.pem
. Once chosen, you should see its contents in the field below. - Click Import button at the bottom and close the window.
- Once applied, you will see the certificate validity dates and a list of domains covered by this certificate.
In your OS, the imported files will be located at /var/nulana/rxgateway/etc/privkey.pem
and /var/nulana/rxgateway/etc/chain.pem
.
When the TLS certificate is set, change the scheme:
- Scroll up to a block named Base URL.
- Click Change base URL.
- Use the same base URL as before but add “s”, changing
http://
tohttps://
.
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.
Important: The maintenance page is independent of your local Hub and always works over HTTP.
4.3 Set mailing
You need a mailing service to let your local Hub send registration confirmation emails, daily reports, computer state alerts, etc. To set it for a Hub:
- Find a block named Mail settings.
- Click an Change settings button.
- In the pop-up window, fill in the following:
- SMTP Server address
A fully qualified domain name of your mailing server. Must include the port.
If you don’t own any mailing server, you may use smtp.gmail.com:587 with your personal Gmail account credentials and email. Please be sure to authorize “less secure app access” to your Google account for this. You may also find various instructions on how to use the Gmail SMTP server to send emails on the Internet. - SMTP FROM address: an email to show in the “From: ” field of all emails sent by your local Hub.
If you choose to use Gmail, put your Gmail address here. - SMTP username: a username used to authorize on the mailing server.
If using Gmail, put your Gmail address. - SMTP password: a password matching the username above.
If using Gmail, specify your Gmail password. - SMTP use TLS
May be checked or not, depending on whether your mailing server enforces TLS encryption or not.
For Gmail, you need to set it to “false”. Otherwise, please refer to the enforced TLS documentation for your mailing server.
- SMTP Server address
- Click Apply button and close the window once done.
- If applied successfully, you will see the specified parameters under Mail settings.
Important: If mailing isn’t set, your local Hub will be unable to perform any actions that involve sending emails (basically everything related to user management).
4.4 Add a superuser
To finish the setup and make your local copy of the Remotix Hub usable, you need to add the first administrator to the Hub:
- Find a block named Users,
- Click Add user,
- In the pop-up window, enter the email and password that you will use to log in to Hub,
- Click Add user and close the window once done.
To check the list of existing Hub users, click Show users.
Congratulations! Now your instance of the Remotix Gateway is good to go. The next step is to set client and agent apps to use it.