We use a private APN which gives public IP addresses on our network.
We usually just set the DMZ for 192.160.1.10 for the device (camera) and a :9443 port forward for the web GUI which directs to 192.168.1.1:80 - all on http.
When setting up the TRB160 i can’t get it to work the same way.
I’ve manged to get it to partially work how I want. I have two port forwards for the device (camera) via :1-9442 and :9442-65535 - this is to cover all other ports as we use a variety of cameras and some don’t always use :80.
Then to access the web GUI i have enabled https remote access in access controls and changed the port to :9443. When I try to do this with HTTP the web GUI will not load. It does load with HTTPS but it creates some confusion for users accessing the page as you have to ensure you add https:// before the IP address and it’s not needed for accessing the camera.
Is there a way to enable http//:192.168.X.X:9443 to take me to the web GUI whilst http://192.168.X.X takes me directly to the device. Without the need for the certificate errors of HTTPS and confusion over adding it to the address bar.
I’ll add that I’ve tried enabling HTTP remote access under a different port “:8443” and this just takes me directly to the device (camera), not the web GUI
First things first, I’d like to ask you to upgrade your firmware version to 7.17.1, since 7.17 was taken out due to having issues. The firmware download page can be found here: TRB160 Firmware Downloads - Teltonika Networks Wiki
The way you have your configuration set up at the moment, theoretically, sounds like it should function the way you want to; however, just to be sure, you can do the following:
Head to System → Administration → Access Control and enable Remote access on HTTPs. I’d suggest changing the default port to something else (for example, 80 to 8080). I’d also like to mention, that there were changes with the HTTP and HTTPS protocols that can be found here: RUTX11 Product Change Notifications - Teltonika Networks Wiki
Basically, all HTTP requests are now redirected to HTTPS automatically.
After you’ve set up the remote access on step 1, you should be able to access your device via 192.168.x.x:8080
You then should set up port forwards, or just use the ones you already have to access your end-devices, the way you would do that is enter the same 192.168.x.x:port to be redirected to the device.
Let me know if this helps, or if further assistance is required.
From reading the change notification link it sounds like there just isn’t a way to access the web UI over HTTP anymore.
Our frustration is having to manually type in the “https://” in the browser when typing 192.168.X.X works fine for the device, if you just add the :9443 on the end after viewing the device it fails to load the web UI. We have to manually add in “https://” and then accept the certificate errors for the the web UI to load. It’s just another step in the workflow.
This is actually completely normal behaviour. Modern browsers default to HTTPS because it’s more secure, encrypting data to prevent interception and tampering. Features like HSTS and HTTPS-First Mode make browsers try https:// before http://, and many websites enforce HTTPS redirects themselves. This improves user safety drastically.
You may try to enable “Redirect to HTTPS” setting under System → Administration → Access Control → “Edit” on HTTPS to see if that improves the situation.
