443 not forwarding 384.19->386.1 Dirty Update

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

jaaem

New Around Here
After a dirty upgrade, port forwarding on 443 no longer works for me from outside the network. Other ports work fine. I don't run AI Cloud, but changed the port just in case. The port-forward tables look ok. It will work again without any setting changes with a dirty revert back to 384.19. However, reverting messes up the router password (seems the never version hashes the password). Luckily I could still ssh in with the saved key and reset manually with the commands below. I have done this upgrade->revert process twice, with the same results.
Code:
nvram set http_passwd="mypassword"
nvram commit
reboot

I can try a clean upgrade, but want to make sure nothing else is the issue. Thanks for any help
 

bbunge

Very Senior Member
After a dirty upgrade, port forwarding on 443 no longer works for me from outside the network. Other ports work fine. I don't run AI Cloud, but changed the port just in case. The port-forward tables look ok. It will work again without any setting changes with a dirty revert back to 384.19. However, reverting messes up the router password (seems the never version hashes the password). Luckily I could still ssh in with the saved key and reset manually with the commands below. I have done this upgrade->revert process twice, with the same results.

Code:
nvram set http_passwd="mypassword"
nvram commit
reboot

I can try a clean upgrade, but want to make sure nothing else is the issue. Thanks for any help
As the release notes tells you, be prepared to do a reset if things don't work right. I went from 384.19 to 386.1 and things seemed to work for a while. Then I just did a hard factory reset and configured manually. Forwarding port 443 works for me as well as everything else I need to have working.
The best planned mission goes to pot after the first shot is fired...
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top