1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Access the Humax web interface over the internet?

Discussion in 'HD/HDR-FOX T2 Customised Firmware' started by sohlinux, Apr 27, 2012.

  1. sohlinux

    sohlinux Member

    How do I setup the Humax HDR Fox 2 web interface so I can access it over the internet while im away?

    I dont want to use dyndns , ill just access it over my static ip address 90.x.x.x portx with a password, but how do I assign the web interface to a port number? and will I need to open the port in the router?

  2. SimpleSim

    SimpleSim Member

    I have made the settings in my router so that port 81 points to the fixed IP address of my humax (on port 80) within my internal network. I have used port 81 only because I already have a NAS running a webserver (on the standard port 80). I use a free O2 wireless router and followed guidance here - http://www.o2help.co.uk/router-port-forwarding/ Find details online of how to do it for your specific router .

    To connect remotely you could just use http://staticipaddress:81/ or I think just http://staticipaddress/

    I have seen the latter version confuse some routers as they want to run their own web administration pages on this address so that might be another reason for using port 81.

    Scared my daughter the other day when she had said she was doing her homework and I could see remotely what film she was watching :)
  3. xyz321

    xyz321 Well-Known Member

    It would be better to enable https, use port 443 and enable authentication.
  4. SimpleSim

    SimpleSim Member

    Thanks xyz321, I hadnt done that believing that I would need to have a SSL certificate (like Thawte or GoDaddy). Is it just a case of using the correct https port?
  5. xyz321

    xyz321 Well-Known Member

    You could either let the browser complain about the certificate and accept it anyway or get a valid certificate from one of the certification authorities.
  6. SimpleSim

    SimpleSim Member

    My understanding is that without the certificate the browser will complain, which I could except, and the traffic will not be encrypted anyway so I am no better off than just using port 80. I couldnt find guidance on putting a certificate on the box so I have just accepted the small risk. Happy to be shown a better way.
  7. sohlinux

    sohlinux Member

    thanks got it working now!
  8. Black Hole

    Black Hole Theloniuos Abbot

    There has been a long discussion on this topic HERE (click).
  9. af123

    af123 Administrator Staff Member

    By default the box will generate a certificate for you. Traffic will be encrypted but the browser will not trust the certificate hence the warning. If you are security concious then you can manually inspect the certificate before accepting it to make sure you are really talking to your Humax - access it over your local network first and take note of the certificate fingerprint then you can look for the same fingerprint when connecting remotely. You can tell that encryption is occurring by the padlock icon in the browser.