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.

Workspace fails to start with DNS configuration issue

See original GitHub issue

Describe the bug

When starting up any workspace, I get the following message:

Starting Init Plugin Broker
Cleaning /plugins dir
Unified Che Plugin Broker
List of plugins and editors to install
- che-incubator/typescript/latest - Typescript language features
- eclipse/che-machine-exec-plugin/0.0.1 - Che Plug-in with che-machine-exec service to provide creation terminal or tasks for Eclipse CHE workspace machines.
- eclipse/che-theia/7.0.0-next - Eclipse Theia, get the latest release each day.
Starting Che plugins and editor processing
Starting VS Code and Theia plugins processing
Downloading VS Code extension for plugin 'che-incubator/typescript/latest'
Get https://github.com/che-incubator/ms-code.typescript/releases/download/v1.35.1/che-typescript-language-1.35.1.vsix: x509: certificate is valid for <myDomain>, not github.com
Error: Failed to run the workspace: "Plugins installation process failed. Error: Plugin broking process for workspace workspacetmujzgxq3e83ylyx failed with error: Get https://github.com/che-incubator/ms-code.typescript/releases/download/v1.35.1/che-typescript-language-1.35.1.vsix: x509: certificate is valid for <myDomain>, not github.com"

Che version

  • latest
  • nightly
  • other: please specify

7.0.0-rc-5.0-SNAPSHOT

Steps to reproduce

  1. Deploy che using either of the following:
  • chectl server:start --installer=helm --domain=<myDomain> --multiuser --platform=k8s --tls --self-signed-cert
  • chectl server:start --installer=helm --domain=<myDomain> --multiuser --platform=k8s --tls or;
  • chectl server:start --installer=helm --domain=<myDomain> --multiuser --platform=k8s
  1. Create an organization
  2. Create & startup any workspace

Expected behavior

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Screenshots

image

Installation method

  • chectl
  • che-operator
  • minishift-addon
  • I don’t know

chectl/0.0.2-a74ad81 linux-x64 node-v10.4.1

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: please specify

private cloud hosted by ubuntu server

Additional context

Looks relevant to https://github.com/eclipse/che/issues/12999 & https://github.com/eclipse/che/issues/13685 maybe?

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:18 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
SDAdhamcommented, Aug 25, 2019

This issue has been resolved, the whole issue was actually produced by maas where when it would compose new machine, it will automatically add search into the DNS settings. Removing those search values from the DNS configuration helped resolving the issue immediately and now that the DNS is stable.

Bug has been reported to the MAAS team https://bugs.launchpad.net/maas/+bug/1841334

Thanks everyone!

1reaction
skryzhnycommented, Jul 29, 2019

I doubt it related to che, more like infrastructure or DNS problem. Can you do curl like curl -v https://github.com/ from workspace pod?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Update DNS servers for Amazon WorkSpaces
Step 1: Update the DNS server settings on your WorkSpaces · On your Windows WorkSpace, open the Windows search box, and enter powershell...
Read more >
Workspace DNS resolution is wrong | AWS re:Post
I have a workspace machine (Windows 10) where the DNS resolution is always returning the wildcard domain over the actual entries in the...
Read more >
My domain verification failed - Google Workspace Admin Help
If you get an error that says your domain verification failed, it could be due to timing or how you entered the verification...
Read more >
Error: "Cannot Complete Your Request" Due to DNS ...
The following error is displayed due to DNS misconfiguration on NetScaler Gateway: Cannot Complete Your Request.
Read more >
Guidance for troubleshooting DNS - Windows Server
The trouble occurs in Active Directory-integrated zones. Issues occur when the DNS Server IP address is changed on the client. When the IP ......
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