Conor
Conor
CCoder.com
Created by Conor on 6/19/2024 in #help
Access url is throwing a cert error
I have coder deployed using helm on a k3s cluster. I also have a self signed CA which is needed to authenticate requests to https://coder.lan values.yaml files:
coder:
certs:
secrets:
- name: homelab-ca
value: cert.crt
service:
type: ClusterIP
env:
- name: CODER_PG_CONNECTION_URL
valueFrom:
secretKeyRef:
name: coder-db-url
key: url

- name: CODER_ACCESS_URL
value: "https://coder.lan"

- name: CODER_WILDCARD_ACCESS_URL
value: "*.coder.lan"
image:
repo: "ghcr.io/coder/coder"
tag: "v2.11.2"
coder:
certs:
secrets:
- name: homelab-ca
value: cert.crt
service:
type: ClusterIP
env:
- name: CODER_PG_CONNECTION_URL
valueFrom:
secretKeyRef:
name: coder-db-url
key: url

- name: CODER_ACCESS_URL
value: "https://coder.lan"

- name: CODER_WILDCARD_ACCESS_URL
value: "*.coder.lan"
image:
repo: "ghcr.io/coder/coder"
tag: "v2.11.2"
Error: EACS03: get healthz endpoint: Get "https://coder.lan/healthz": tls: failed to verify certificate: x509: certificate signed by unknown authority The cert is being mounted to /etc/ssl/certs successfully. However, it is not being updated for curl (for example) to access the url without getting an x509: certificate signed by unknown authority error Any ideas why this is?
6 replies
CCoder.com
Created by Conor on 4/9/2024 in #help
Accessing an sql server from outside the workspace
Hi, I have coder deployed on a k8s cluster and a workspace using docker in docker. I have deployed an sql server in the workspace using docker compose, exposing 1433 and 1434 (TCP). Our team wants to be able to access that sql server from outside the workspace. Is this possible? If it is what’s the best way of doing it?
5 replies