The DD-WRT web interface occasionally crashes — typically after a configuration change or during periods of high router load — leaving you unable to access the admin panel despite the router continuing to route traffic normally. The solution is straightforward if you have SSH enabled: connect to the router via SSH and restart the web server process directly from the command line, restoring access without needing a full reboot that would interrupt all connected devices.
The Fix
SSH into the router using its IP address and the root credentials you set during configuration. Once in, the command to restart the DD-WRT web interface is typically stopservice httpd && startservice httpd or alternatively restart_httpd depending on the DD-WRT build version. On some builds, killall httpd && httpd works directly. The web interface should be accessible again within a few seconds of running the command. If SSH isn’t enabled on your DD-WRT router, enabling it in the Services panel is strongly recommended as it provides exactly this kind of fallback access.
Prevention
The DD-WRT web UI is less stable than the routing engine itself — crashes are more common on older builds and during config-heavy operations. Running a current build, avoiding rapid-fire configuration changes, and having SSH always enabled are the main mitigation strategies. The ability to recover via SSH without rebooting is one of the strongest arguments for always keeping SSH access enabled on a DD-WRT router, even if you rarely use it proactively.
Leave a Reply
You must be logged in to post a comment.