Think you have been setting your router up just right – but still cant connect to it from WAN.

This helped for me:

1) SSH into the router

2) Identify the pid of the httpd service with the command: ps | grep http

3) Kill the pid with the command: kill -9 <pid-number>

4) Change directory through the command: cd /etc/config

5) Start the service again through command: startservice httpd

6) Verify service is running again with the command: ps | grep http


Hopefully you should be able to connect to your router again now.

If IE9/IE10 complains about certificate and it doesnt work to click “Continue” then make sure that Internet Explorer are able to connect to 512 bit certificated sites by issueing the command certutil -setreg chain\minRSAPubKeyBitLength 512 as administrator in ms dos prompt. After this you should be able to access the dd-wrt without any problems.

1 comment so far

Add Your Comment
  1. DD-WRT rocks. The first thing I do when I or someone I know buys a WRT54G(L) is flash the ltseast version in. I have one, my parents have one, my in parents-in-law have one, my brother-in-law has one, we have 2 in the head office and 1 in each of 5 branch offices all running DD-WRT. I’m even giving one to my boss for his mother’s house. I also have 2 more sitting around waiting to be put to use.About the coolest thing I ever did with DD-WRT was set up one on an ethernet line in a hotel conference center, use the PPTP client to connect to the VPN at work. I then used 2 more as wireless _clients_ to the one on the VPN and connected 2 WYSE thin clients to each router and configured them to automatically login and auto-start IE to our Outlook Web Access. Our users could just enter their name and password to check their email between break-out sessions. I didn’t have to run a single network cable longer than the 3 feet from the router to the thin client, and the users didn’t have to worry about signing on the VPN, just sit-and-go.