I recently updated to the latest 4.7 firmware. Unfortunately, I was unaware that, due to security changes, the main Nginx port page and the LuCI port page have been separated.
Before the update, I had configured specific ports for HTTPS. However, after the update to 4.7, while my settings were retained, I can no longer access LuCI using the new default port 8443. Instead, it operates with the designated HTTPS specific port, yet LuCI displays the error "No related RPC reply," which prevents me from making any configurations via the LuCI interface.
I manually adjusted the parameters via shell to reset the Nginx and uHTTPd ports to their default settings. Unfortunately, this approach did not resolve the issue.
Is there an existing solution to this issue that doesn't require resetting the firmware and starting over?
Since Luci does not have very reliable security protection, considering the access security from the WAN side (GL GUI has thoughtful security), v4.7 firmware for Luci sets a separate port and uses "uhttpd" to listen for access to GL GUI and Luci.
If you have manually modified the Luci port in the nginx configuration file, it may be possible to resolve the issue by resetting the firmware.
Thank you for your response. As per your suggestion, I reset the firmware prior to my post and was able to access Luci.
However, would it be possible to reset only the Nginx and uhttpd configuration files instead of performing a full firmware reset? I hope you can understand that, given the extensive effort invested in configuring the system over time, a complete reconfiguration from scratch would take at least two days in my setup, including testing and verification.
I attempted to manually modify the Nginx gl.conf and adjust uhttpd to standard port parameters, but I continued to encounter the Luci error: "No related RPC reply," even with Nginx utilizing standard ports instead of those assigned to uhttpd.
I would sincerely appreciate any additional guidance you can provide as an alternative to fully resetting the firmware.
I have good news! My previous question in my last post led me to a solution for the "Luci no related RPC reply" issue encountered after updating to GL.iNet firmware 4.7.
Since I already had a backup of my settings prior to the update, I decided to reset the router with the 4.7 firmware to review the default configurations for both Nginx and uhttpd files using WinSCP method.
I backed up the default configuration files for both Nginx and uhttpd.
Next, I downgraded to a firmware version prior to 4.7 and restored my most recent settings backup, ensuring compatibility with that specific firmware version.
I then adjusted the ports to their default values, using the backup files Nginx and uhttpd from my 4.7 firmware reset as a reference.
After upgrading back to the latest 4.7 firmware, I was able to access Luci without encountering the error.
Please note that I cannot guarantee this method will work for others, but I wanted to share it in case it proves helpful.
I recommend always creating a settings backup within Luci before making any changes. This precaution ensures that, if anything unexpected occurs, you can quickly restore your previous configuration without complications.
Thank you for your support and Happy Thursday!
PS: If you have time, I would greatly appreciate it if you could kindly review a post I made in November 2024. It may be possible to implement the stated example based on that discussion.
I got same problem after upgrade my router MT3000 to 4.7.x firmware.
But I never use customized port for uhttp or luci. all my these settings are default.
I have tried to upgrade from 4.7.0 to 4.7.4, and tried to reset 4.7.4, problem cannot fix.
Hope GL-iNet can fix the problem in future release.
To ensure the users can fully comprehend the challenges you're facing, it would be prudent to address the following queries:
Have you updated the firmware via the GL-iNet router's administrative interface?
Were the previous settings preserved during the update process?
At any point, did you manually install an alternate version of uhttpd using opkg, whether within Luci or through SSH?
Furthermore, to assist in identifying the access issues with Luci, kindly provide additional context:
When attempting to open Luci, what specific outcome manifests?
Does the URL indicate a particular port?
Is the error message "No related RPC reply" visible?
Alternatively, does Luci present a login screen?
It would be most appreciated if you could supply responses to these inquiries. Such cooperation will enable us to ascertain your current position with respect to the latest firmware upgrade and expedite a resolution.
