Termix-SSH / Termix-SSH/Support

[BUG] Sync: fetch failed

Open
#1,294 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auth bug platform-desktop platform-docker platform-linux security
Dominant language
No language data
Stars
28
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Title

Sync: fetch failed with Self-signed certificate

Platform

Desktop App - Linux

Server Installation Method

Docker

Version

2.7.1

CLI Installation Method

No response

CLI Version

No response

Troubleshooting
  • I have examined logs and tried to find the issue
  • I have reviewed opened and closed issues
  • I have tried restarting the application
  • I have checked open issues and ensured this is not a duplicate
The Problem

I deployed version 2.7.1 of the product on an isolated server using Docker, with the latest version of Angie serving as the reverse proxy. The server has a local IP address and an FQDN within the local domain zone; a self-signed certificate was generated for this FQDN. I access the service via a browser after accepting the local certificate. When launching the client, I attempt to configure remote synchronization: I enter the server address and toggle the setting to allow invalid certificates. The server's authorization window appears, and I enter my credentials, but synchronization fails to start after I click the login button.
Error: fetch failed
Logg in terminal client

  Allowed invalid certificate for configured server {
  url: 'https://termix.localzone/ssh/tunnel/status',
  error: 'net::ERR_CERT_AUTHORITY_INVALID',
  issuer: 'termix.localzone',
  subject: 'termix.localzone'
}
Allowed invalid certificate for configured server {
  url: 'https://termix.localzone/host/db/host',
  error: 'net::ERR_CERT_AUTHORITY_INVALID',
  issuer: 'termix.localzone',
  subject: 'termix.localzone'
}
[backend] [20:10:05] [INFO] [📡] Found 0 autostart hosts and 0 total hosts for endpointHost resolution
Error occurred in handler for 'get-remote-sync-user-info': [TypeError: fetch failed] {
  [cause]: Error: self signed certificate; if the root CA is installed locally, try running Node.js with --use-system-ca
      at TLSSocket.onConnectSecure (node:internal/tls/wrap:1748:34)
      at TLSSocket.emit (node:events:509:28)
      at TLSSocket._finishInit (node:internal/tls/wrap:1185:8)
      at ssl.onhandshakedone (node:internal/tls/wrap:966:12) {
    code: 'DEPTH_ZERO_SELF_SIGNED_CERT'
  }
}
How to Reproduce
  1. Set up a server with a self-signed certificate over reverse-proxy.
  2. Configure synchronization using the Ubuntu client with the option to allow invalid certificates enabled.
Additional Context

Allowing an invalid certificate must enable not only login but also synchronization with the server in question.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the desktop client's remote-sync flow and the handler named get-remote-sync-user-info, using the provided terminal log as the first diagnostic clue. Reproduce with the Ubuntu client, Docker server, reverse proxy, and self-signed certificate while allowing invalid certificates. Done means login and synchronization both work without the fetch failed error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, linux, node.js
Domain
desktop, networking, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
57/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.