This page describes the standard customer-side installer workflow for a Modibus remote access deployment. Use it when a customer, distributor or service partner needs to install the local access package, prepare the connection profile and verify that the device can be reached through the approved service channel.
What this installer does
The customer installer prepares a workstation for controlled remote service. It does not replace site security policy; it gives the technician a repeatable way to place the VPN profile, credentials file and diagnostic checks in the correct order.
- Prepares the customer-specific connection profile supplied with the project handover package.
- Creates or references the local authentication file required by the project.
- Imports the profile into the approved remote access client.
- Runs a connectivity check against the target Modibus gateway or service endpoint.
- Collects a small support package when installation does not complete successfully.
Before you begin
- The Windows user must have permission to install or run the approved remote access client.
- The customer must have the project username and password or an approved credential file.
- Outbound UDP traffic to the assigned VPN endpoint must be allowed by the customer firewall.
- The target gateway must already be commissioned, powered and connected to the internet.
- If the site uses endpoint protection, the installer folder should be allow-listed before starting.
Create the authentication file
The installer expects a local credential file path provided for the customer project. The file should contain the username on the first line and the password or token on the second line.
customer-user@example.com
customer-password-or-tokenSecurity note: Do not email the completed authentication file. Store it only on the approved workstation or in the customer password manager, and remove it after troubleshooting if the access is temporary.
Installer workflow
- Create a working folder such as
C:\Modibus\RemoteAccessand place the installer, connection profile and credential file inside it. - Edit the project placeholders for the endpoint, port, protocol and credential file path according to the project handover sheet.
- Import the profile into the approved remote access client or run the installer script that performs the import automatically.
- Start the VPN session with the customer-approved account and wait until the client reports a connected state.
- Verify routing by pinging the assigned gateway service address or opening the local device web UI through the VPN.
- Record the acceptance result including date, workstation name, operator and target gateway serial number.
Validation checklist
| Check | Expected result |
|---|---|
| Installer package | The supplied project package is present on the workstation and matches the handover version. |
| Profile import | The approved remote access client shows the Modibus customer profile without syntax errors. |
| Authentication | The session passes username/password or token validation. |
| Routing | The assigned gateway or service address is reachable only after VPN connection. |
| Audit | The support record includes operator, device serial number and installation timestamp. |
Troubleshooting
The profile imports but does not connect
Confirm that the endpoint hostname, UDP/TCP protocol and port match the customer project. Then check whether the firewall blocks outbound VPN traffic.
The client asks for credentials every time
Check that the credential file path points to the correct local file and that the remote access client has permission to read it.
The VPN connects but the gateway is unreachable
Verify the assigned route, gateway LAN address and customer-side subnet. Overlapping local networks are the most common cause of this symptom.
The installer is blocked by antivirus or endpoint protection
Ask the customer IT team to review the event log, allow-list the installer folder and confirm that the binary or script hash matches the version supplied by Modibus.
Support package
If the installer cannot complete, send Modibus support the profile version, installer version, operating system, remote access client log, gateway serial number and a screenshot of the final error. Do not include the password or token.