# Remote access of Supermon from outside LAN **URL:** \ **Category:** Archive\ **Created:** [March 3, 2022, 4:18am UTC](https://community.allstarlink.org/t/remote-access-of-supermon-from-outside-lan/19228 "2022-03-03T04:18:59Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![kb0nhx](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kb0nhx/32/1986_2.png) [@kb0nhx](https://community.allstarlink.org/u/kb0nhx)\ **Post date:** [March 3, 2022, 4:18am UTC](https://community.allstarlink.org/t/remote-access-of-supermon-from-outside-lan/19228/1 "2022-03-03T04:18:59Z")
Besides using the htttp://xxx.xxx.xxx.xxx:8081/supermon (or whatever port you choose) I’ve been told you can access the node remotely using something like IRLP does with their [stnxxx.irlp.net](http://stnxxx.irlp.net) web address. I cannot find a reference to this in the supermon setup instructions. Is anyone accessing their node in this manner? If so, how is it done? ---
**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\ **Post date:** [March 9, 2022, 4:46pm UTC](https://community.allstarlink.org/t/remote-access-of-supermon-from-outside-lan/19228/2 "2022-03-09T16:46:25Z")
I know nothing of supermon but, Assuming you are using port 8081 for local http, You can port forward a port to the ip of the webhost. In most routers, it does not have to be the same port. Say we take port 8090 and forward that traffic to local ip 192.168.1.100 port 8081 (web server ip/port) You would work/browse your external ip 117.117.117.123:8090 and would be forwarded to that local webserver on the correct port based on your port forward config in the router. The port could be the same, but I’m showing it different for example. I make them different for security of popular ports. A hack does not immediately know what they stumble on open and likely not what they are looking for. Hacks would know what 80 81 8080 8081 8180 8181 are likely used for if they are looking to penetrate www server. Not that it is an issue for you to worry about. Perhaps that info will serve you down the road. Not necessary but explained for better understanding. This method can be used if you have more than one webserver behind your NAT. Add a port fwd to it. ---
**Author:** ![kb0nhx](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kb0nhx/32/1986_2.png) [@kb0nhx](https://community.allstarlink.org/u/kb0nhx)\ **Post date:** [March 10, 2022, 3:31am UTC](https://community.allstarlink.org/t/remote-access-of-supermon-from-outside-lan/19228/3 "2022-03-10T03:31:27Z")
I found the solution to my problems: 1 - Besides updating the Manager.conf file to show my port for remote access, I also had to update the “Virtual Host” to the proper port as well in the 000-default.conf file 2 - To access the node remotely without knowing the public IP, you can browse to: [http://xxxxx.asnode.org](http://xxxxx.asnode.org):yy/supermon xxxxx = your all star node number and yy=your specific port number used for remote access ---
**Author:** ![system](https://community.allstarlink.org/uploads/default/original/2X/4/42700284e201b031bd667c3f63bbae05a74b3104.png) [@system](https://community.allstarlink.org/u/system)\ **Post date:** [March 13, 2022, 3:11pm UTC](https://community.allstarlink.org/t/remote-access-of-supermon-from-outside-lan/19228/4 "2022-03-13T15:11:19Z")
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.