original-birdman
Occasional Visitor
A few weeks ago I managed to get my own self-signed certificate working with my RT-BE92U.
On Saturday morning I had an oddity. My nightly backup showed that a file,
Attempting to login to the Web GUI told me that the certificate was unrecognized - it had reverted to an Asus generated one!!
I accepted this and looked at the config. According to the Web interface my self-signed certificate was still active (but clearly it wasn't as far as the actual httpd process was concerned).
I uploaded the key and certificate again, but this made no difference.
I had to leave home at that point, so left a note to look at it again this afternoon (Sunday). Oddly my self-signed certificate is now working again.
All odd. (The
The certificates on the secondary AIMesh nodes were unchanged (still my sefl-signed one).
Any suggestions as to what happened and why?
Meanwhile, I'll just wait to see whether it happens again.
On Saturday morning I had an oddity. My nightly backup showed that a file,
/tmp/https_srv.csr, had arrived on the main system and I wondered what this was.Attempting to login to the Web GUI told me that the certificate was unrecognized - it had reverted to an Asus generated one!!
I accepted this and looked at the config. According to the Web interface my self-signed certificate was still active (but clearly it wasn't as far as the actual httpd process was concerned).
I uploaded the key and certificate again, but this made no difference.
I had to leave home at that point, so left a note to look at it again this afternoon (Sunday). Oddly my self-signed certificate is now working again.
All odd. (The
https-srv.csr is a certificate signing request from Asus - no idea who they are expecting to sign it).The certificates on the secondary AIMesh nodes were unchanged (still my sefl-signed one).
Any suggestions as to what happened and why?
Meanwhile, I'll just wait to see whether it happens again.
