Unable to access resources behind cloudflared. about homelab

[cheers1999]

Thanks! I've been running external from the external folder. I've been using your repo to learn, sorry I missed the copyright. I deleted quite a few things in one of those moments of frustration, and I must have deleted that as well. I'll correct that quickly. I appreciate you taking the time to help, I'll follow your instructions and report back.

…

On Wed, May 18, 2022, 7:05 AM Khue Doan ***@***.***> wrote: Are you building the external layer using cd external && make or running make external/make all from the root directory of the project? I think it's due to the change in this commit dc7d125 <dc7d125>, can you try again by running make external from the root directory of the project (I'll need to update the documentation). Btw please keep the copy right notice or add an acknowledgement to your repo in case you forgot 😉 — Reply to this email directly, view it on GitHub <#61 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZGXM4OXE45NI7QD4SVWIBTVKTMJ3ANCNFSM5WGRDXIQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[khuedoan]

Is it accessible via LAN? Most services are only accessible via LAN by default, you must explicitly allow internet access.

Could you please provide the following additional information:

1. Are you accessing Hajimari via LAN or internet?
2. Your homelab repository
3. Cloudflare tunnel logs (available from the cloudflared namespace)
4. Ingress addresses (./scripts/get-dns-config)
5. DNS config on Cloudflare dashboard (this should be updated automatically, just double checking)

[cheers1999]

Thanks for the quick reply. Yes, I enabled by following those instructions.

1. Accessing it via LAN.
2. https://gitlab.com/rijndael128/homelab
3. Looks like terraform apply failed , and the cloudflare namespace was not created.

│ Error: Get "http://localhost/api/v1/namespaces/cloudflared/secrets/cloudflared-credentials": dial tcp 127.0.0.1:80: connect: connection refused
│
│   with module.cloudflare.kubernetes_secret.cloudflared_credentials,
│   on modules/cloudflare/main.tf line 43, in resource "kubernetes_secret" "cloudflared_credentials":
│   43: resource "kubernetes_secret" "cloudflared_credentials" {
│
╵
╷
│ Error: Get "http://localhost/api/v1/namespaces/external-dns/secrets/cloudflare-api-token": dial tcp 127.0.0.1:80: connect: connection refused
│
│   with module.cloudflare.kubernetes_secret.external_dns_token,
│   on modules/cloudflare/main.tf line 79, in resource "kubernetes_secret" "external_dns_token":
│   79: resource "kubernetes_secret" "external_dns_token" {
│
╵
╷
│ Error: Get "http://localhost/api/v1/namespaces/cert-manager/secrets/cloudflare-api-token": dial tcp 127.0.0.1:80: connect: connection refused
│
│   with module.cloudflare.kubernetes_secret.cert_manager_token,
│   on modules/cloudflare/main.tf line 110, in resource "kubernetes_secret" "cert_manager_token":
│  110: resource "kubernetes_secret" "cert_manager_token" {

10.10.69.224   argocd.weyland.io
10.10.69.224   dex.weyland.io
10.10.69.224   git.weyland.io
10.10.69.224   home.weyland.io
10.10.69.224   jellyfin.weyland.io
10.10.69.224   chat.weyland.io
10.10.69.224   matrix.weyland.io
10.10.69.224   grafana.weyland.io
10.10.69.224   paperless.weyland.io
10.10.69.224   seafile.weyland.io
10.10.69.224   tekton.weyland.io
10.10.69.224   registry.weyland.io
10.10.69.224   vault.weyland.io

Also, the tunnel was created but it shows as inactive on the cloudflare dashboard.

[khuedoan]

Are you building the external layer using cd external && make or running make external/make all from the root directory of the project?

Due to the change in this commit dc7d125, can you try again by running make external from the root directory of the project (I'll need to update the documentation or revert the change).

Btw please keep the copy right notice or add an acknowledgement to your repo in case you forgot 😉

[cheers1999]

Alright, looks like that was it. More user error than a bug. Dex is having trouble with secret "dex-secrets" not found, but I can go ahead and troubleshoot that. Thanks for the help!!

[khuedoan]

Nice!

Some secrets (Dex, Renovate...) require manual token creation and put into Vault, I haven't automate this process yet, it should be completed in the next version (before the first beta release).

You can see this section to see where to put those secrets in Vault:

homelab/platform/vault/files/generate-secrets/config.yaml

Lines 7 to 13 in 606c7ab

	# TODO create tokens and put to Vault automatically
	# - gitea/renovate:
	# - id
	# - token
	# - gitea/dex:
	# - client_id
	# - client_secret