Author Topic: Remote access to Acuparse web GUI via port other than 80  (Read 151 times)

0 Members and 1 Guest are viewing this topic.

Offline vade64

  • Member
  • *
  • Posts: 2
Remote access to Acuparse web GUI via port other than 80
« on: September 04, 2019, 06:43:58 AM »
Can I access Acuparse via another port other than the default for http of 80?  How can I configure the port on the web interface to something else?

Offline galfert

  • Forecaster
  • *****
  • Posts: 2880
Re: Remote access to Acuparse web GUI via port other than 80
« Reply #1 on: September 04, 2019, 07:54:56 AM »
Most routers have a function to open and forward ports. But it doesn't have to be same port to same port. You can open an external port and forward it to a different internal port. For example you can externally open port 8080 but forward it internally to 80. That is how you get around port 80 being blocked by most ISP companies.

If your router doesn't support this feature then replace your router. If you are using what the ISP gave you then you should replace it anyway for many other reasons. I recommend the Asus RT-AC68U. It supports mesh with more than one of these. Or if you need more coverage and don't want to deal with mesh the get the RT-AC5300, which also can become mesh if you later want. These are wireless or wired mesh (your choice).

BUT... before you open a port you should ensure that the port you are opening is secured. Does Acuparse provide a login? Is it encrypted authentication? Because if not then you are exposing the system to the outside world. You may think ah who cares. But a compromised system can be used for many things not just spying on you and looking at your weather. It can become part of a botnet and rob you of bandwidth. And then you are helping to spread evil.

A solution instead of opening up a firewall port to an insecured device is to make your router a VPN endpoint. The routers I recommended support OpenVPN which have available a free client that you can install on your computer or mobile that will be connecting to your router's VPN remotely. Once you establish a VPN connection to your home router you will have access to all internal devices as if you were home. So you'll be able to access port 80 on that internal IP address directly from anywhere. OpenVPN is free.

A simpler solution to the VPN, is to create a remote access connection to a computer. Then you remotely control that system to then talk to whatever other internal device. Perhaps you can even create a direct remote access to the very computer that is running Acuparse. There are many remote system access solutions. But this is not as elegant of an experience from a mobile device. By remote access I'm referring to Microsoft's Remote Desktop Client access that is built into Windows 10 Pro as the host (but you can use Windows Home as a client or a mobile device app), or you can use a remote access software like TeamViewer or LogMeIn or GoToMyPC or many others.
« Last Edit: September 04, 2019, 08:07:16 AM by galfert »
WS-2000 & WS-2902A | Ecowitt GW1000 | WeatherBridge (Meteobridge)
WU: KFLWINTE111  |  PWSweather: KFLWINTE111
CWOP: FW3708  |  AWEKAS: 14814
Windy: pws-f075acbe
Weather Underground Issue Tracking
Tele-Pole

Offline vade64

  • Member
  • *
  • Posts: 2
Re: Remote access to Acuparse web GUI via port other than 80
« Reply #2 on: September 04, 2019, 08:48:37 AM »
Thanks for the detail.  I'm familiar with port forwarding and security.  My router fortunately has SSL security included and I have activated it for my port forwards.  I do like the idea of using VPN and this too is included with my router.  I will have to give that a try, much more simple/elegant solution.

Offline nincehelser

  • Forecaster
  • *****
  • Posts: 3178
Re: Remote access to Acuparse web GUI via port other than 80
« Reply #3 on: September 04, 2019, 08:57:10 AM »
Can I access Acuparse via another port other than the default for http of 80?  How can I configure the port on the web interface to something else?

You'll want to change the apache2 configuration, probably starting with the /etc/apache2/ports.conf file, then restating apache2.

Quote
$ cat ports.conf
# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default.conf

Listen 80

<IfModule ssl_module>
        Listen 443
</IfModule>

<IfModule mod_gnutls.c>
        Listen 443
</IfModule>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet