{"id":36541,"date":"2018-12-03T13:00:21","date_gmt":"2018-12-03T12:00:21","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=36541"},"modified":"2020-03-15T18:06:59","modified_gmt":"2020-03-15T17:06:59","slug":"veeam-fix-self-signed-certificate-issue","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-fix-self-signed-certificate-issue\/","title":{"rendered":"Veeam self-signed certificates issue"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-36545 size-full\" title=\"veeam-self-signed-certificates-issue-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/12\/veeam-self-signed-certificates-issue-01.jpg\" alt=\"veeam-self-signed-certificates-issue-01\" width=\"602\" height=\"202\" \/><\/p>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/veeam-availability-orchestrator-setup-pt-1\/\">Veeam<\/a> reported a bug related to self-signed certificates generated during the installation of the software and used by the backup infrastructure components to <strong>communicate safely<\/strong>.<\/p>\n<p>By default the generated self-signed certificate is created and set to <strong>expire after one year<\/strong> and due to a bug after the\u00a0<a href=\"https:\/\/nolabnoparty.com\/en\/veeam-backup-and-replication-9-5-update-3a-now-available\/\">Update 3<\/a> installation date, a <strong>strange behavior<\/strong>\u00a0occurs while opening the Veeam Backup console.<!--more--><\/p>\n<p>The problem arises when you <strong>open the Veeam Backup console after 11 months<\/strong> after Update 3 installation time. You receive a <em>Failed to check certificate expiration date<\/em> error message and, if the message is ignored, <strong>after 12 months<\/strong> the Veeam functionality breaks and the<strong> agent management functionality<\/strong> and all <strong>granular restores<\/strong> fail.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-36547 size-full\" title=\"veeam-self-signed-certificates-issue-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/12\/veeam-self-signed-certificates-issue-02.jpg\" alt=\"veeam-self-signed-certificates-issue-02\" width=\"335\" height=\"171\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Fix the self-signed certificates issue<\/h2>\n<p>This bug will be fixed in the Update 4 and <strong>the solution to quickly solve the problem<\/strong>\u00a0requires the creation of a <strong>new self-signed certicate<\/strong>\u00a0as reported in the\u00a0<a href=\"https:\/\/www.veeam.com\/kb2806\" target=\"_blank\" rel=\"noopener noreferrer\">KB2806<\/a>.<\/p>\n<p>Before proceeding, make sure <strong>no backup jobs<\/strong> are currently running.\u00a0Open the Veeam Backup console and access the <strong>General Options<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-36549 size-large\" title=\"veeam-self-signed-certificates-issue-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/12\/veeam-self-signed-certificates-issue-03-600x394.jpg\" alt=\"veeam-self-signed-certificates-issue-03\" width=\"600\" height=\"394\" \/><\/p>\n<p>Go to <strong>Security<\/strong> tab and click <strong>Install<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-36551 size-full\" title=\"veeam-self-signed-certificates-issue-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/12\/veeam-self-signed-certificates-issue-04.jpg\" alt=\"veeam-self-signed-certificates-issue-04\" width=\"512\" height=\"511\" \/><\/p>\n<p>Select <strong>Generate new certificate<\/strong> option and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-36553 size-large\" title=\"veeam-self-signed-certificates-issue-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/12\/veeam-self-signed-certificates-issue-05-600x427.jpg\" alt=\"veeam-self-signed-certificates-issue-05\" width=\"600\" height=\"427\" \/><\/p>\n<p>Make sure no backup jobs are running then click <strong>Yes<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-36564 size-full\" title=\"veeam-self-signed-certificates-issue-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/12\/veeam-self-signed-certificates-issue-06.jpg\" alt=\"veeam-self-signed-certificates-issue-06\" width=\"581\" height=\"126\" \/><\/p>\n<p>Leave the default\u00a0<strong>Friendly Name<\/strong>\u00a0or enter a new one\u00a0<span class=\"List_L1\">for the created self-signed\u00a0certificate\u00a0<\/span>then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-36566 size-large\" title=\"veeam-self-signed-certificates-issue-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/12\/veeam-self-signed-certificates-issue-07-600x427.jpg\" alt=\"veeam-self-signed-certificates-issue-07\" width=\"600\" height=\"427\" \/><\/p>\n<p>A new self-signed certificate is being created.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-36568 size-full\" title=\"veeam-self-signed-certificates-issue-08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/12\/veeam-self-signed-certificates-issue-08.jpg\" alt=\"veeam-self-signed-certificates-issue-08\" width=\"360\" height=\"100\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to save the new certificate\u00a0<span class=\"List_L1\">in the\u00a0<\/span><strong><span class=\"List_L1\">shared<\/span><\/strong><span class=\"List_L1\"><strong>\u00a0certificate store<\/strong> on the Veeam Backup Server.<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-36570 size-large\" title=\"eeam-self-signed-certificates-issue-09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2018\/12\/veeam-self-signed-certificates-issue-09-600x427.jpg\" alt=\"eeam-self-signed-certificates-issue-09\" width=\"600\" height=\"427\" \/><\/p>\n<p>This fix allows you to avoid nasty surprises in your backups due to self-signed certificates issue keeping your <strong>backup infrastructure healthy<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<h4>UPDATE<\/h4>\n<p>The issue has been fixed in <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-backup-replication-9-5-update-4-upgrade-procedure\/\">Veeam Backup &amp; Replication 9.5 Update 4<\/a>.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Veeam reported a bug related to self-signed certificates generated during the installation of the software and used by the backup infrastructure components to communicate safely. By default the generated self-signed certificate is created and set to expire after one year and due to a bug after the\u00a0Update 3 installation date, a strange behavior\u00a0occurs while opening the Veeam Backup console.<\/p>\n","protected":false},"author":3,"featured_media":36545,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2138,933],"tags":[2161,682,1939,1940],"class_list":["post-36541","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-backup-en","category-veeam-en","tag-bug-en-2","tag-certificate-en","tag-self-signed","tag-veam","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/36541","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=36541"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/36541\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/36545"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=36541"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=36541"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=36541"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}