With your Keenetic router, you can provide remote access from the Internet to web applications on your home network, including the router's web interface and the Transmission built-in torrent client's GUI. This can be done through the KeenDNS service using 4th-level domain names, even without a public IP address.
First, select a free KeenDNS domain name in the settings and configure the service. Detailed setup is presented in the KeenDNS service article.
TIP: Note: The digital certificate and HTTPS private key are stored directly on the Keenetic router. When accessing via a cloud server using HTTPS, a secure tunnel is built up to the router, ensuring the security and confidentiality of data transmitted via the Internet. The session is established using end-to-end encryption. This means, among other things, that the information transmitted between the router and the browser via HTTPS is not available to KeenDNS cloud servers, which provide data transfer at the transport layer. With cloud access via HTTP, a secure channel is established between the router and the KeenDNS server using a KeenDNS digital certificate, guaranteeing security and data protection against interception.
Here is an example of remote access to the web interface of a QNAP NAS (running on port 80) connected to the home network. You can configure remote access to any web-enabled device in your home network (a webcam, network drive, router, server, etc.).
1. To start with, it is necessary to register the devices in the router to be accessible remotely. More information can be found in the Connected devices registration article.
2. On the 'Domain name' page, on the 'KeenDNS' tab, click 'Add' in the section 'Access to web applications running on your network'.
NOTE: Important! The 'Access to web applications running on your network' section is only present in the main Router Mode and is not available in the secondary Extender Mode.
3. The 'Access settings' page appears.
In the 'Host' field, select the device registered in your home network on which the web application is running. You can choose the router to access the built-in services (e.g. Transmission GUI) or any other device registered in your home network.
Create a domain name for this application in the 'Domain name' field. The name should be in the Latin alphabet.
In our example, the application uses the router's domain name 'myrouter01.keenetic.link' and the 4th level domain name 'qnap' to access the web interface of the network storage. Thus, the QNAP interface will be available by the domain name 'qnap.myrouter01.keenetic.link'.
To access the QNAP interface from the Internet, you should allow remote access in the corresponding field.
In the 'TCP port' field, specify the port number on which the web application runs on your home network.
The rule to access the web interface of QNAP network storage will look like this:
4. Once configured, the home network device will be available via the following 4th-level domain name from the Internet:
That being said, the Keenetic router has a private IP address for the Internet connection.
NOTE: Important! The cloud service (operating mode 'Cloud access') only supports operation via the protocols:
HTTP on ports: 80, 81, 280, 591, 777, 5080, 8080, 8090 and 65080
HTTPS on ports: 443, 5083, 5443, 8083, 8443 и 65083
If you have changed the pre-configured Keenetic management port 80 to another one, then accessing the home network resources via the 4th level domain will also be via the changed port. For example, for port 777:
You can change the Keenetic web interface control port on the 'Users and access' page in the 'Administrative services' section in the 'HTTP port' field.
For information on setting up remote access to the 3G/4G USB modem or GPON router web interface, see the Access to the USB modem web interface via the KeenDNS service manual.
Examples of how to provide access to an IP camera from the Internet can be found in the Internet access to an IP camera connected to a Keenetic device article.
Enabling authentication for a device with an open web interface when using remote access via the KeenDNS service.