zeekayandHanzo Dev 31deee7551 fix(deploy): dedicated api-explore.lux.network ingress with letsencrypt-prod TLS ...

The explorer Go backend answers by Host header via the ingress default backend,
so api-explore.lux.network responded 200 with no ingress rule — but with no TLS
block for that SNI the controller served the self-signed INGRESS DEFAULT CERT,
which browsers reject (ERR_CERT_AUTHORITY_INVALID). The explorer FE was stuck in
skeleton loaders. Add a dedicated Ingress -> explorer-unified:8090 with a
letsencrypt-prod TLS block (mirrors api-explore.osage.network). Verified live:
explore.lux.network now loads live blocks/txns/stats (ssl_verify_result=0).

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-15 18:13:04 -07:00

..

k8s

fix(deploy): dedicated api-explore.lux.network ingress with letsencrypt-prod TLS

2026-07-15 18:13:04 -07:00

scripts

fix(explore): reconcile chainIds to live/canonical + migrate chain RPC to /v1 (v1.1.7)

2026-07-14 10:06:17 -07:00

tools

feat: rename @blockscout to @luxfi, monochrome theme, horizontal blocks

2026-03-02 12:28:15 -08:00

values

feat: explorer FE — stateless SSR, chain selector, localnet, registry cleanup

2026-03-01 18:00:00 -08:00

helmfile.yaml.gotmpl

regcred from helmfile for review

2025-11-05 11:15:23 -03:00