Skip to content

internxt add-cert fail on fedora #262

Description

@noticons

I recently moved to Fedora from Arch. Following this tutorial I still had to edict the /etc/hosts file to add https://webdav.local.internxt.com:3005/ to 127.0.0.1. no biggie. When I ran the add-cert command, however, it returned an error, the fundamental problem being that it didn't recognize the -i flag. I examined the script at /usr/local/lib/node_modules/@internxt/cli/scripts/add-cert.sh and saw the only -i flag was on the update-ca-trust command in the fedora section.
I checked to see if it had, in fact, copied the cert file, and it had. Then I ran the update-ca-trust command manually without the -i flag. It ran fine without issue. That being said, rclone still through up the typical x509: certificate signed by unknown authority error.
Anyway, I ran it with the --no-check-certificate and of course, it works fine. I can't say why, however, it is still throwing up the error, though, since the certificate was added. If I have anything to update, I'll add it later.

Bottom Line

it is likely that the command in the add-cert.sh script is malformed for fedora, since the update-ca-trust doesn't take an -i flag.

Further Investigation

I read the readme at /etc/pki/ca-trust/extracted/pem/README and it said
This directory /etc/pki/ca-trust/extracted/pem/ contains
CA certificate bundle files which are automatically created
based on the information found in the
/usr/share/pki/ca-trust-source/ and /etc/pki/ca-trust/source/
directories.

I thought, perhaps the add-cert.sh script was perhaps copying the cert file to the wrong directory, since rclone isn't trusting the CA. I have no idea. Anyway, just bumbling through.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions