- I understand so there is no server expiry unless I change the server.crt for my server. The current server shows “certificate Invalid”, So I guess I’ll change my server certificate to CA signed or something right? But then If i change my server certificate, Do I need to re-run the steps for production server again right, to generate new server.crt?
If you get a new server cert outside of the production server setup (ie by purchasing it from an agency) then you need to skip the steps in our docs that create the server and simply use the one provided by the agency.
- Is it possible to redeploy the already deployed release to my device, Because its in the testing phase, so everytime Im generating new release and uploading it. Its extremely important for my use case, because I’ll be using the post deployment API in my Mender-client, and its might need to redeploy the same release.
No. The server will detect that the artifact name has not changed and refuse to re-send it. As long as the artifact name is changed then you should be ok.
- Also, guide me to how to update the Mender client if new version is released from your end, Because for sure these devices are gona be remote, so how to update these client version with all the parameters.
The client is just part of the root filesystem so it depends on how you generated the image in the first place.
If you use Yocto then it is part of your Yocto build. When the updated client versions are available in your checked out Yocto layers, then simply rebuilding with the new commits will have the new version.
If you are using mender-convert then you will need to re-run that tool to make sure the newer client is included.
If any mender.conf file changes are needed they will be handled similarly.
- If I upgrade my production server to newer version, Will the server.crt be same and all mender clients still be connected ?
As long as you don’t change the certificate file in your server setup directory.