Skip to content
This repository has been archived by the owner on Feb 26, 2023. It is now read-only.

Nomad fs with TLS #308

Closed
mlosiewicz-pl opened this issue Sep 1, 2017 · 4 comments
Closed

Nomad fs with TLS #308

mlosiewicz-pl opened this issue Sep 1, 2017 · 4 comments

Comments

@mlosiewicz-pl
Copy link

I have a Nomad cluster configured with TLS with certificates for client.eu-west-1.nomad and server.eu-west-1.nomad and with configuration via environment variables I was able to run Hashi UI on the cluster. Everything works but for logs and files for allocations. I am getting
13:19:15.931 connection.go:78 ▶ ERROR [4080d319] Unable to fetch directory: Get https://{{domain_name}}:4646/v1/client/fs/ls/155bb020-fbfa-53b3-7dc1-8463564917c6?path=%2Falloc%2Flogs%2F: x509: certificate is valid for server.eu-west-1.nomad, client.eu-west-1.nomad, localhost, not client..nomad

I was having the same issue with nomad agent but setting NOMAD_REGION to eu-west-1 solved the issue with agent, as far as I know there is no way to do it in Hashi UI.

@jippi
Copy link
Owner

jippi commented Sep 1, 2017

It is 99,999% a Nomad upstream issue - sounds a lot like hashicorp/nomad#3127

@jippi jippi closed this as completed Sep 1, 2017
@jippi
Copy link
Owner

jippi commented Sep 1, 2017

Oops, closed to fast! when 0.6.3 is out and hashi-ui is build against it, lets see if it works or not :)

@SoMuchToGrok
Copy link

SoMuchToGrok commented Sep 14, 2017

Currently have Nomad 0.6.3 (TLS) along with hashi-ui 0.18.0, everything is working great 👍

@jippi
Copy link
Owner

jippi commented Sep 15, 2017

Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants