https://agenti.cash serves the *.github.io certificate, so HTTPS fails

Open
  • Is something wrong?
#158 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Under an hour
Newbie friendliness
20/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github
Domain
infrastructure

Research direction

The fault is in the GitHub Pages custom-domain setup, not in repository code, so start under Settings → Pages in the nirholas/agenti repository. Reproduce with the curl and openssl commands in the issue, which show the wrong *.github.io certificate for agenti.cash. Done means https://agenti.cash returns a certificate for agenti.cash and Enforce HTTPS can be enabled; this needs repository admin rights, so confirm with the maintainers first.

Written by the indexing model from the issue text.

Description

https://agenti.cash fails TLS (checked 2026-09-23 03:45 UTC). The server presents GitHub's *.github.io certificate instead of one for agenti.cash. That certificate covers github.com, github.io and githubusercontent.com, so browsers show a certificate warning and HTTP clients refuse the connection.

  • http://agenti.cash works: 200, Server: GitHub.com, serving the docs site from GitHub Pages.
  • The apex A records point at GitHub Pages (185.199.108–111.153) and www.agenti.cash is a CNAME to nirholas.github.io, so the DNS looks right.
  • What is missing is the certificate GitHub Pages issues for a custom domain. Removing and re-adding the custom domain under Settings → Pages usually restarts issuance. Once it completes, "Enforce HTTPS" can be switched on.

To check:

$ curl -sI https://agenti.cash
curl: (60) SSL: no alternative certificate subject name matches target host name 'agenti.cash'

$ echo | openssl s_client -connect agenti.cash:443 -servername agenti.cash 2>/dev/null | openssl x509 -noout -subject -ext subjectAltName
subject=CN=*.github.io
X509v3 Subject Alternative Name:
    DNS:*.github.com, DNS:*.github.io, DNS:*.githubusercontent.com, DNS:github.com, DNS:github.io, DNS:githubusercontent.com

How we noticed. Sato Hub checks the site of every listing once a day. Our check has not completed against https://agenti.cash on any of the 70 days from 2026-07-14 to 2026-09-21. Our probe filed that as inconclusive. Checked by hand with curl and openssl today, the certificate is the cause.

Context. Sato Hub is an index of onchain-agent tooling. Agenti is listed at https://satohub.ai/resources/agenti, and cryptocurrency.cv at https://satohub.ai/resources/cryptocurrency-cv. Maintainers can claim a listing to correct its description, links, tags and chains (https://satohub.ai/claim/agenti). A claim grants no badge or verified status. The certificate fix above does not depend on any of this.

— Sato Hub

Dominant language
TypeScript
Stars
80
Forks
21
Avg merge
22h 2m
Merged PRs (30d)
11

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nirholas/agenti

All issues in nirholas/agenti

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.