I followed the instructions cause could’nt delete through the webui the certificate and I did it through ssh following the instructions of the forum in other thread. I rebooted router (RUTX50) but the certificate still appears in the webui but now I can not do anything with him.
Looks like you got same what I had about month ago. Since certificate is still valid some time, I propose following.
If I were you, I would wait they reply you in few days. And if they have you their recommended working solution, I would go with what they advise you to do.
But incase you do not get answer for a long time, you might solve issue the way I did to fix issue.
You find my conversation with Teltonika support and solution following link. I found a solution myself while they were looking solution their part few days. My solution will require using ssh root@device and using command line, to run commands with a small script I wrote to help if anyone else would need to fix same.
If you wonder why did I not write that script in way that it would execute those commands automatically when script is run. I did not want do that and wanted that whoever runs that will then themselves do run changing command and bear responsibility. And perhaps understands bit better what is happening and not had to blindly rely some random dude (me) written script.
Right, let the support chance to try official fix what they might have already had time to do with new sw releases. Then if not avail or work, this what I did is your backup, right. But let them try if they have a fix now. It’s important that they get that so that it would be easier for admins going on.
Could you confirm which firmware version is currently installed on your RUTX50? Is it 7.17 or above?
Our developers are already aware of an issue related to the uHTTPd server certificate renewal, and it is expected to be resolved in the upcoming 7.20 release.
As a temporary workaround, you can regenerate the WebUI certificates using the following API request:
api POST /access_control/webui/actions/generate '{"data":{"force":"1"}}'
After doing so, it is also recommended to create a backup of your configuration.
The Mesrik’s workaround proposed above is also a valid alternative, so you may try (if not yet) that option as well if you prefer.