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.

Che-theia doesn't inform che-master about activity in workspace when https with self-signed cert is used

See original GitHub issue

Describe the bug

Che-theia doesn’t inform che-master about activity in the workspace when https with self-signed cert is used. I assume the reason is that https://github.com/eclipse/che-theia/blob/master/extensions/eclipse-che-theia-activity-tracker/src/node/activity-tracker-service.ts#L68-L90 is not covering usecase with a self-signed cert.

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

  1. Setup Che chectl server:start --platform=crc --installer=operator --tls --self-signed-cert
  2. Start workspace.
  3. Workspace would be stopped with default timeout no matter what you are doing inside of it.

Expected behavior

Che-theia should send activity reports to che-master

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

Installation method

  • chectl chectl/0.0.20200211-next.1744186 darwin-x64 node-v10.19.0
  • che-operator
  • minishift-addon
  • I don’t know

Environment

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

Additional context

Issue Analytics

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

github_iconTop GitHub Comments

1reaction
vitaliy-guliycommented, Mar 6, 2020

It’s very annoying issue.

0reactions
azatsarynnyycommented, Feb 27, 2020

@l0rd last sprint we investigated it a bit with @skabashnyuk We will take it to the next sprint.

Read more comments on GitHub >

github_iconTop Results From Across the Web

accepting HTTPS connections with self-signed certificates
The first thing you need to do is to set the level of verification. Such levels is not so much:.
Read more >
Chapter 3. Installing CodeReady Workspaces in TLS mode ...
Self -signed certificates are not trusted by default. For example, when a website owner uses a self-signed certificate to provide HTTPS services, ...
Read more >
Troubleshooting SSL - GitLab Docs
SSL certificate problem: self signed certificate in certificate chain. This error indicates that the client does not trust the certificate or CA.
Read more >
How to Generate and Install an SSL Certificate on a ...
If you have already generated an SSL certificate on one of your StoreFront servers in the StoreFront server group, you can just export...
Read more >
Use Google-managed SSL certificates | Load Balancing
Google-managed SSL certificates are Domain Validation (DV) certificates that Google Cloud obtains and manages for your domains. They support multiple hostnames ...
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