Connect ACTAtek device from the Internet
ACTAtek4 Remote Internet Access: Port Forwarding, No-IP DDNS, and Static Public IP Configuration
Applies to: All ACTAtek Series Devices and IP Reader Models
This article explains how to configure an ACTAtek terminal for remote Internet access using a private LAN IP address, router port forwarding, No-IP Dynamic DNS, or an ISP-assigned static public IP address.
1. Understanding the Three Deployment Methods
- Port forwarding without DDNS: Access the ACTAtek through the router's public IP address and an external TCP port.
- Port forwarding with No-IP DDNS: Access the ACTAtek using a hostname that automatically follows changes to the router's public IP address.
- Static public IP: Map a dedicated public IP address to the ACTAtek through a router/firewall, or assign the IP directly when the ISP and network architecture support it.
2. Configure ACTAtek on the Local Network
Before configuring external access, make sure that the ACTAtek works properly on the internal network.
Example ACTAtek network settings:
| Setting | Example Value |
|---|---|
| IP Address | 192.168.1.105 |
| Subnet Mask | 255.255.255.0 |
| Default Gateway | 192.168.1.50 |
| DNS Server | 8.8.8.8 |
| HTTPS Port | 443 |
Note: These are example values only. The ACTAtek's IP address, gateway, and subnet must match the actual customer's network configuration. Confirm that HTTPS on port 443 (default) is set on the particular device.
Verify that the terminal's web interface is accessible locally:
https://192.168.1.105/
Use a reserved DHCP address or a properly assigned static LAN IP to prevent the device's address from changing unexpectedly.
Option 1:Login to the physical device's console IP setting menu to turn on DHCP first,and then turn off to have the fixed IP address.
Option 2: Enter the valid IP settings manually according to the local area network settings.
1.Run the below command at your laptop/PC where it is connect to the same router/WiFi AP router ready to access the Internet
C:>ipconfig /all
IPv4 Address. . . . . . . . . . . : 192.168.1.106(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : July 3, 2025 1:50:21 PM
Lease Expires . . . . . . . . . . : July 4, 2025 1:50:22 PM
Default Gateway . . . . . . . . . : 192.168.1.50
DHCP Server . . . . . . . . . . . : 192.168.1.50
DHCPv6 IAID . . . . . . . . . . . : 77857465
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2A-E4-70-F8-98-E7-F4-4C-76-4C
DNS Servers . . . . . . . . . . . : 8.8.8.8
2.Login to the physical ACTAtek device's console IP setting menu to enter IP settings as an example below.
Subnet Mask:255.255.255.0
IP Address:192.168.1.105
Gateway:192.168.1.50
DNS IP:8.8.8.8
3.Once done,please use Chrome to open the device's webpage at 192.168.1.105.
Note: The device's "Allowed IP" setting is used to restrict access to the web interface. Only the specified IP address(es) will be permitted to access the device, while access from all other IP addresses will be denied.
3. Port Forwarding Without Dynamic DNS
When the ACTAtek is installed behind a network router, the router must direct incoming traffic from the Internet to the device's private IP address.
Log in to the network router and locate the Port Forwarding, Virtual Server, or NAT configuration page.See the attached files as examples.
Create a rule similar to the following:
| Router Setting | Value |
|---|---|
| WAN Interface | Internet/WAN |
| External Port | 444 |
| Internal Destination IP | 192.168.1.105 |
| Internal Port | 443 |
| Protocol | TCP/UDP |
| Status | Enabled |
Example external URL:
https://YOUR-PUBLIC-IP:444/
Important: The router must have a publicly reachable WAN IP address.You can access https://whatismyipaddress.com/ to find your external IP address.
4. Recommended External Port Numbers
TCP port 444 is a convenient documented example for ACTAtek port forwarding. The following additional ports may also be used if they are available and permitted by the customer's network:
| External TCP Port | Internal TCP Port | Notes |
|---|---|---|
| 444 | 443 | Preferred documentation example |
| 8443 | 443 | Common alternative HTTPS port |
| 10443 | 443 | Alternative external port |
| 11443 | 443 | Alternative external port |
| 18443 | 443 | Alternative external port |
Only one external port is generally needed for each terminal. Multiple ACTAtek terminals behind the same public IP can use different external port numbers mapped to their respective private IP addresses.
Example:
PUBLIC-IP:444to192.168.1.105:443PUBLIC-IP:8443to192.168.1.106:443PUBLIC-IP:10443to192.168.1.107:443
5. Port Forwarding With No-IP Dynamic DNS
No-IP Dynamic DNS is useful for customers whose Internet service provider assigns a public IP address that may change.
Instead of remembering a numeric IP address, the customer can connect using a hostname such as:
https://customer-example.ddns.net:444/
Step 1: Register a No-IP Account
- Visit https://www.noip.com.
- Create an account and verify it as required.
- Create a Dynamic DNS hostname using an available No-IP domain.
- Record the hostname and required DDNS update credentials.
Step 2: Configure the Dynamic DNS Updater
There are three possible update methods:
- Router DDNS: If the router supports No-IP, enter the hostname and appropriate credentials or No-IP DDNS Key in the router's DDNS settings. This is generally preferred.
- No-IP Dynamic Update Client: If the router does not support No-IP, use No-IP's update client on an always-running computer in the same network.
- ACTAtek built-in DDNS client: If neither of the above is available, the ACTAtek device can update No-IP directly using its built-in DDNS client, so no router support or extra computer is needed. On the device's web interface, open the DDNS setting page and configure the settings as shown below. Please refer to the attached files (ACTAtek_ddns_settings.png and ACTAtek_ddns_port-forwarding.png) for examples.
Field Value DDNS Service Provider No-IP.com SSL Disable Username/Email Your No-IP account email Password Your No-IP account password Host Name Your No-IP hostname, e.g. actatekdemo.ddns.netUpdate interval (seconds) 600 (default)
Click Submit to save the settings. Then click Refresh DDNS Status to confirm it is working.
The status log should show the device connecting to the No-IP server and a message such as “Successful alias table update for hostname => new public IP address # x.x.x.x”.
After that, the log should periodically report “No IP# change detected” at each update interval, which means the hostname is up to date. If the device’s public IP changes, it will push the new address to No-IP automatically at the next check.
Note: The ACTAtek device must have Internet access and be connected behind a router with a public IP address and the required port forwarding configured. See Step 3 below.
Step 3: Configure Router Port Forwarding
Create the same TCP port-forwarding rule described in Section 3:
External TCP 444 → 192.168.1.105 TCP 443
Step 4: Verify DDNS and Remote Access
- Verify that the DDNS hostname resolves to the correct public IP.
- Confirm the No-IP updater is active and reporting successful updates.
- Test the hostname from an external Internet connection.
- Confirm that the correct ACTAtek web interface appears. e.g.https://actatekdemo.ddns.net:444/
A customer with a fixed public IP normally does not need DDNS.
6. Remote Access Testing Procedure
- Test the ACTAtek web interface from a computer on the same LAN.
- Verify that the ACTAtek has the correct default gateway.
- Confirm that the router has a publicly reachable WAN IP address.
- Check the port-forwarding or NAT rules and associated firewall permissions.
- For DDNS, verify that the hostname resolves to the correct public IP.
- Switch a test computer or phone to a separate Internet connection, such as cellular data.
- Open the external HTTPS URL using the configured hostname/IP and external port.
- Verify that the correct ACTAtek login page appears.
7. Troubleshooting
| Problem | Recommended Checks |
|---|---|
| Works locally but not remotely | Check NAT, firewall permissions, gateway, WAN address, ISP restrictions, and upstream NAT. |
| DDNS hostname does not connect | Check hostname resolution, DDNS updater status, No-IP account credentials, and port forwarding. |
| Wrong web interface appears | Check the destination IP, external port, router remote-management settings, and conflicting forwarding rules. |
| Public IP does not work | Verify ISP address allocation, gateway, subnet, routing method, network segment, and firewall configuration. |
| Works externally but not using public URL inside LAN | Check whether the router supports NAT loopback/hairpin NAT, or configure appropriate internal DNS. |
8. Security Best Practices
- Change factory-default administrator passwords.
- Use strong, unique credentials for administrative accounts.
- Keep ACTAtek firmware updated.
- Disable unnecessary network services.
- Review network logs for unexpected connection attempts.
9. Frequently Asked Questions
Q: If I configure port forwarding, do I need to change the ACTAtek IP address?
A: No. The ACTAtek normally retains its existing private LAN IP address. The router forwards the selected external port to the device.
Q: What is the recommended external port?
A: TCP port 444 is a convenient documented example, mapped to the ACTAtek's internal HTTPS port 443. Other available external ports can also be used.
Q: Does No-IP eliminate the need for port forwarding?
A: No. No-IP provides a hostname that resolves to the public IP address. The router still needs to direct incoming connections to the ACTAtek.
Q: Do I need No-IP if I already have a static public IP address?
A: Generally, no. You can access the static public IP directly or configure a conventional DNS hostname.
Q: Can multiple ACTAtek terminals share the same public IP address?
A: Yes. When using port forwarding, each device can use a unique external port number directed to its own private IP address and HTTP/HTTPS port.