possible bug - Remote Access with https

Discussion in 'Tomato Firmware' started by arigosh, Jan 24, 2007.

  1. arigosh

    arigosh Network Guru Member

    Anyone been able to work with https over remote access? It's working fine when I set it to http, but I cannot seem to be able to get it working with https, I either get error messages about the encryption (wrt54gl) or it just doesn't work at all (wrt54gs).
  2. digitalgeek

    digitalgeek Network Guru Member


    https://web address url:port/

    don't forget to include the port
  3. ntest7

    ntest7 Network Guru Member

    It's normal for your browser to display a warning about the security certificate when you connect via https.

    This is because the router uses a self-signed certificate and doesn't (and can't) have an official Verisign/Thawte/etc. certificate.

    The exact message varies depending on the browser you are using, IE7 says something like "there is a problem with this website's security certificate" and you can click the "continue to this website (not recommended)" link.

    Firefox says "Website certified by an Unknown Authority" and gives some choices. Just click the "OK" button.
  4. i had a similar issue - it worked with IE but not with firefox - saying something about an invalid serial number of the certificate (i'am using german software so the exact message maybe differ).

    the issue was that for the ip-address there was already a certificate in place which i installed when using another firmware.

    i could fix this using:
    Extras > Settings > Advanced > Tab:Encryption > Show Certifiactes
    (the labels maybe slightly differ)

    There I deleted the old certificate and reinstalled it when connecting to my router the next time.
  5. digitalgeek

    digitalgeek Network Guru Member

    I usually choose the accept temporarily option in firefox, as I have had trouble after an upgrade and had to delete the certificate. The temp option is always selected by default when I connect.
  6. arigosh

    arigosh Network Guru Member

    Thanks, It turns out that my the proxy server used at my workplace does not like encryption on port 8080, moving the port to 443 resolved the problem.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice