You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have rportd and rport-pairing running in our private cloud with the client and pairing endpoints exposed on the WAN at their respective ports, but the API only accessible through the private networks within the cloud on another port (for which we use the internal IPs or DNS names served up by Designate). This creates a bit of a problem for rportcli:
$ rportcli client list
FATAL: operation failed with an error: Get "https://internal.host.local:9443/api/v1/clients?fields%5Bclients%5D=id%2Cname%2Ctimezone%2Ctunnels%2Caddress%2Chostname%2Cos_kernel%2Cconnection_state%2Cdisconnected_at&page%5Blimit%5D=50&page%5Boffset%5D=0": x509: certificate is valid for wan.host.tld, not internal.host.local
This is something i run into with Go and Rust quite a bit - produced binaries don't have a --disable-cert-validation type of CLI flag. Any chance there is one, or an environment variable i can set, and i'm just not seeing it in the CLI or the docs?
The text was updated successfully, but these errors were encountered:
We have
rportd
andrport-pairing
running in our private cloud with the client and pairing endpoints exposed on the WAN at their respective ports, but the API only accessible through the private networks within the cloud on another port (for which we use the internal IPs or DNS names served up by Designate). This creates a bit of a problem forrportcli
:This is something i run into with Go and Rust quite a bit - produced binaries don't have a
--disable-cert-validation
type of CLI flag. Any chance there is one, or an environment variable i can set, and i'm just not seeing it in the CLI or the docs?The text was updated successfully, but these errors were encountered: