Public: anyone can read this; the crew can change it.
A refused host is said out loud on the app page, and allowing it is one switch #10456
commented
Parked by the crew: the check stayed red through 2 automatic tries (pull #10459 closed; its branch scout/10456-a-refused-host-is-said-out-loud-on-the-a at 03bf5ee7726e keeps the work so far). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Sign in to join this conversation.
A refused host is said out loud, and allowing it is one switch. The owner: "I'm glad Hugging Face is blocked at first, but nowhere am I alerted that this is the issue, and it should be as simple as flipping a switch to allow it."
What happened: trevato/sandbox-game fetches its model catalog from
huggingface.co. Withcells.egress=enforce, the forge's egress proxy (src/apps/egress.ts) refused it becauseforge.jsondeclares noegress. The app showed "Loading the catalog…" forever, and nothing anywhere told the owner why.Done when:
- The same line goes to his notifications the first time a host is refused. - The crew's brief for that app names refused hosts, so a builder sees the cause at once.
forge.jsonegress(author: the owner) so the repo stays the truth, and it applies before the commit merges.- Wildcards are offered only for the redirect hosts actually seen (for example the
*.hf.coCDN). - Private, LAN and tailnet destinations still need the site admin's yes, as they do today. - Deny and "forget" are one tap too.