[dasPaul]

Hi there

I have a local webserver that supports https and I want to make it accessible to the WAN. But as I connect to DDWRT via ssl port 443 is already occupied by DDWRT. So I tried to change the DDWRT https default port:

wd_sslport=443
to
wd_sslport=667
then
nvram commit && reboot

Then if I try to open my browser at "https://192.168.1.1:667" I get an "Unable to connect", but connecting to the old "https://192.168.1.1" I can reach still reach the webinterface.

What am I doing wrong?

[Per Yngve Berg]

That port 443 is in use at the lan interface does not mean it's occupied at the WAN interface. Port forward 443 to your web server. Access it from internet (not your local lan) using the public wan ip address.

I will not recommend making the GUI accessible from the wan.

[dasPaul]

you're absolutly right and it was not my intention to serve the webinterface to WAN. I did not try to access from outside...

I will reset the sslport via nvram and make an portforward from WAN 443 to LANIP 10443 (my webserver ssl port) and try to connect from outside and not lan. I will report back...

[tatsuya46]

http://svn.dd-wrt.com/ticket/5953 isnt helping either

[dasPaul]

it works, from WAN I get the portforwarded webserver with my own certifikate, from LAN the webinterface with ddwrt's certificate.

Thanks!

[Per Yngve Berg]

On the lan, use the local private ip address of the web server.

You can have a local dns that resolves the same domain name to the local ip when on lan.

dnsmasq can be used on dd-wrt for this.