FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
811 views 0 comments
by anonymous
Opened RMS Session to RUT240 device (latest SW version) connected via LTE network to the internet. Other device with https access possibility is connected via LAN port to the RUT240 LAN port, so device is "behind" the RUT240, which is itself connected via LTE to the internet. Now goal is to open a https session on the device from the RUT240 RMS session:

Under Actions|Device Access I added the new device:

a) Added Device Name string (any name I liked)

b) Added local private IP address assigned from RUT240 to WAN port of the device via DHCP

c) Added https port, unter which https on the device is accessible - port number 48842 in my case

d) Selected https protocol from the selection list

-> Successfully added the new device in addition to CLI and WebUI in the list

Clicked on new device in the list:

Case a) Pressed "Generate" with "Use legacy mode" unchecked: Window in browser pops up saying "Company has no data left"

Case b) Pressed "Generate" with "Use legacy mode" checked: Link is generated. When opening the link in a new tab, the following error message is displayed in the new tab:
"An error has occured while trying to browse through the proxy.
Failed to connect to device. Possible problems are that the server was not found, the connection timed out, or the connection refused by the host. Try connecting again and check if the address is correct."

Why does access not work? Can somebody help? Are there any modifications to the RUT240 firewall settings required? Thanks a lot.

1 Answer

0 votes
by anonymous
Hi,

Could you make sure that RMS can access your router WebUI and other devices except for the one that is not working at this moment?

Make sure that the device got the right gateway and IP given by the DHCP server and is connected by WAN port.

EB.