question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

There was an unknown error starting Kubernetes: FetchError: request to https://update.k3s.io/v1-release/channels failed, reason: certificate signature failure

See original GitHub issue

Rancher Desktop Version

1.0.0-beta.1

Rancher Desktop K8s Version

1.21.6

What operating system are you using?

macOS

Operating System / Build Version

macOS Big Sur 11.6.1

What CPU architecture are you using?

x64

Windows User Only

No response

Actual Behavior

When starting v1.0.0-beta, get the following error:

There was an unknown error starting Kubernetes: FetchError: request to https://update.k3s.io/v1-release/channels failed, reason: certificate signature failure

This only appears to occur when connecting from inside the corporate network, which uses a self-signed cert for the internal proxy. When disconnected from the internal network, everything starts up as expected.

Steps to Reproduce

  1. Start 1.0.0-beta.1 for the first time after installation, while behind a firewall with a self-signed cert.
  2. Receive the error shown above (and in the screenshot, below) prior to downloading Kubernetes.

Result

image

Expected Behavior

Kubernetes should start.

Additional Information

No response

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:18 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
drenze-athenecommented, Jan 18, 2022

Regarding the logs, all logs lies in this path ~/Library/Logs/rancher-desktop.

Ya - that’s where I found what I posted. There was nothing in there specifically from the installation, and what I posted was from the first startup after I installed, which is when it tried to pull everything down.

0reactions
drenze-athenecommented, May 18, 2022

I have 1.3.0 installed and have had no issues since 1.1.0.

Douglas J. Renze INFRASTRUCTURE SENIOR ENGINEER

From: Gary A Korhonen @.> Date: Tuesday, May 17, 2022 at 4:09 PM To: rancher-sandbox/rancher-desktop @.> Cc: Douglas Renze @.>, Mention @.> Subject: Re: [rancher-sandbox/rancher-desktop] There was an unknown error starting Kubernetes: FetchError: request to https://update.k3s.io/v1-release/channels failed, reason: certificate signature failure (Issue #1261)

ATTENTION: External Email - Be Suspicious of Attachments, Links and Requests for Login Information.

Hi @drenze-athenehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdrenze-athene&data=05|01|drenze%40athene.com|349850546b3f43c64e1708da38498861|70559d03915449e19e59be933c7f8440|0|0|637884185752145236|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=yQHEEOj%2FEyHM1cai3kVwgFHFkPd%2BB1IDx6%2FHf3S%2B60U%3D&reserved=0. Looking over recent work around this area, we did a fix tied to certificates in #1613https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Francher-sandbox%2Francher-desktop%2Fpull%2F1613&data=05|01|drenze%40athene.com|349850546b3f43c64e1708da38498861|70559d03915449e19e59be933c7f8440|0|0|637884185752145236|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=koOyxrd1z2aINHEJDHd0LibO8%2BjePQlFQ6GDFJ%2B4DCw%3D&reserved=0 that was included as part of 1.1.0.

If you’re in a position to do so, are you able to try this again with a more recent version of Rancher Desktop (latest: 1.3.0 with another version due soon) and see if you still have the same problem?

— Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Francher-sandbox%2Francher-desktop%2Fissues%2F1261%23issuecomment-1129319791&data=05|01|drenze%40athene.com|349850546b3f43c64e1708da38498861|70559d03915449e19e59be933c7f8440|0|0|637884185752145236|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=v5PCz2bGvulvbc99nt9KIE2bLIDETH3czx%2BSHLgPIyA%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FATNKTFBCUU7O4MK4LXMGRK3VKQDITANCNFSM5MHOXMGA&data=05|01|drenze%40athene.com|349850546b3f43c64e1708da38498861|70559d03915449e19e59be933c7f8440|0|0|637884185752145236|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=L9VweqqQpCCGmJR%2FBU7gwSbH6z0MlwuJOXXDd8hocdE%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>

Electronic communication sent through the internet is not secure and its delivery is not guaranteed. This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it from your computer. All annuity products and services are offered through Athene Annuity & Life Assurance Company and Athene Annuity and Life Company, in all states except New York, and in New York through Athene Annuity & Life Assurance Company of New York and Athene Life Insurance Company of New York. All investment advisory services are rendered solely through Apollo Insurance Solutions Group LLC. None of the information contained herein should be construed as an offer or sale of any security, product, or service of Apollo Insurance Solutions Group LLC. Past performance is not indicative of future success.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Automated upgrade fails to upgrade v1.18.3+k3s1 to stable
Upgrade jobs are not created and the cluster is not upgraded. I find repeating messages in the system-upgrade-controller log for the k3s ......
Read more >
Automated Upgrades - K3s - Lightweight Kubernetes
You can manage K3s cluster upgrades using Rancher's system-upgrade-controller. This is a Kubernetes-native approach to cluster upgrades. It leverages a ...
Read more >
There was an unknown error starting Kubernetes: FetchError
There was an unknown error starting Kubernetes: FetchError: request to https://update.k3s.io/v1-release/channels failed, reason: certificate ...
Read more >
Reinstall causes x509: certificate signed by unknown authority
I need to know how to properly clean-up after uninstalling HA k3s so I don't get this error: x509: certificate signed by unknown...
Read more >
Fix Rancher SSL certificate - JM Robles - Medium
json file. $ rm rancher/k3s/server/tls/dynamic-cert.json. Finally, I restarted the rancher container and it created ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found