Does the HTTPS/TLS certificate change with each reboot?

[sirwifi]

It seems that Chrome complains after reboot that the GUI's HTTPS certificate is not trusted. I tried adding it permanently but it doesn't seem to work, after a router reboot, it starts complaining again. Is this expected? Any workaround to just make a browser trust it?

 

[john9527]

It seems that Chrome complains after reboot that the GUI's HTTPS certificate is not trusted. I tried adding it permanently but it doesn't seem to work, after a router reboot, it starts complaining again. Is this expected? Any workaround to just make a browser trust it?

By default, the router generates a new certificate on every reboot. To prevent this telnet/ssh to the router and enter

nvram set https_crt_save=1
nvram commit

Then reboot and add the certificate to Chrome. Then it should stick.

EDIT: I'm not sure if this got moved to jffs in the later levels, but if it hasn't, it will take up about 1K of nvram space. So double check your nvram space on the Tools>Sysinfo page after making the change.

 

[Wutikorn]

By default, the router generates a new certificate on every reboot. To prevent this telnet/ssh to the router and enter

nvram set https_crt_save=1
nvram commit

Then reboot and add the certificate to Chrome. Then it should stick.

EDIT: I'm not sure if this got moved to jffs in the later levels, but if it hasn't, it will take up about 1K of nvram space. So double check your nvram space on the Tools>Sysinfo page after making the change.

Thanks! That helps a lot. After some reboots, I see no more than 0.1MB change in JFFS, so it is probably stored in NVRAM, but there is enough space there.