Supported version: Saleculator 4.5 and later.
Saleculator Dyn remote access gives a store a fixed URL such as storename.dyn.saleculator.com. Partners can use this URL to reach the customer computer when Saleculator POS and the local web service are running.
How Dyn remote access works #
Dyn remote access uses an outbound SSH tunnel from the customer computer to dyn.saleculator.com. The customer network does not need to open an incoming port. The customer computer must be able to make an outbound SSH connection to dyn.saleculator.com on port 22.
When the tunnel is online, the Dyn URL forwards requests to the local Webin, XAMPP, or lighttpd service configured in Saleculator. When the tunnel is not online, the Dyn URL may show a message such as Remote access is temporarily offline.
Before you configure Dyn #
- Keep Saleculator POS installed and working on the customer computer.
- Start Webin, XAMPP, or lighttpd locally.
- Confirm the local service opens on the configured port, normally
http://localhostorhttp://localhost:80. - Make sure the customer internet connection is active.
- Make sure the customer network allows outbound SSH to
dyn.saleculator.comport22.
Test before creating the Dyn URL #
Before you click Connect, click Test on the Remote Access screen. The test checks whether local Webin is reachable and whether the customer computer can reach dyn.saleculator.com on SSH port 22.
If the test fails, fix the reported issue first. Saleculator will not create the Dyn URL until the required local Webin and SSH checks pass. This helps avoid creating a paid Dyn URL that immediately shows the offline page.
Configure remote access in Saleculator #
- Open Saleculator POS on the customer computer.
- Go to Settings.
- Open the Remote Access tab.
- Enter the Dyn URL name assigned to the customer. Enter only the name part, for example
hotbuns, or the full URLhotbuns.dyn.saleculator.com. - Enter the local Webin, XAMPP, or lighttpd port used on the customer computer.
- Save the settings.
- Click Test and confirm the local Webin and SSH checks pass.
- Click the option to connect or reconnect Remote Access. Saleculator checks the same requirements before creating the Dyn URL.
After connection, open the Dyn URL in a browser, for example https://hotbuns.dyn.saleculator.com.
Check whether SSH to Dyn is allowed #
On the customer Windows computer, open Command Prompt and run:
ssh -p 22 saleculator@dyn.saleculator.com
If the result says Connection closed by 68.183.239.156 port 22, the computer can reach the Dyn SSH server. This is enough to confirm that outbound SSH is not blocked at the basic network level.
If the command times out, cannot resolve the host, or cannot connect, check the customer firewall, antivirus firewall, router, ISP, or office network policy. The network must allow outbound TCP traffic to dyn.saleculator.com on port 22.
Check the local Webin or web server port #
On the same customer computer, run:
curl http://localhost
Port 80 is normally used for Webin. If the customer setup uses another port, replace the URL with the port configured in Saleculator, for example http://localhost:8080. If this does not open locally, Dyn remote access cannot work. Start Webin, XAMPP, or lighttpd and confirm the local page opens first.
If the Dyn URL shows Remote access is temporarily offline #
This message means the Dyn URL is active, but Saleculator could not reach the customer computer through the tunnel at that moment.
- Keep Saleculator POS running on the customer computer.
- Start Webin, XAMPP, or lighttpd locally.
- Confirm the local URL opens, normally
http://localhostorhttp://localhost:80. - Reconnect Remote Access from Saleculator settings.
- Confirm outbound SSH to
dyn.saleculator.comport22is allowed. - Restart Saleculator POS if the tunnel does not reconnect.
- If needed, restart the customer computer and connect Remote Access again.
Useful checks for partners #
From any internet-connected computer, check the customer Dyn URL:
curl -I https://customername.dyn.saleculator.com/
If the URL returns the Saleculator offline page, DNS and HTTPS are working, but the customer-side tunnel or local service is offline.
Check SSH from the customer computer:
ssh -p 22 saleculator@dyn.saleculator.com
A connection closed message from the server means SSH is reachable. A timeout or connection failure usually means the customer network is blocking SSH.
Common causes #
- Saleculator POS is closed.
- Webin, XAMPP, or lighttpd is not running.
- The configured local port is wrong.
- The customer firewall or antivirus is blocking the local web server.
- The customer network blocks outbound SSH on port
22. - The internet connection changed or dropped after Remote Access was connected.
- The computer went to sleep or restarted.
What to send to support #
If the issue continues, send these details to your Saleculator partner or support team:
- The Dyn URL, for example
hotbuns.dyn.saleculator.com. - The local Webin/XAMPP/lighttpd port.
- The result of
curl http://localhost:PORTfrom the customer computer. - The result of
ssh -p 22 saleculator@dyn.saleculator.comfrom the customer computer. - Whether Saleculator POS was running when the test was done.