mosaicstack/stack
1
0
Fork 0
Code Issues 77 Pull Requests Actions Packages Projects Releases 15 Wiki Activity

install.sh: mosaicstack.dev/install.sh returns HTTP 500 — primary advertised install path is down #803

New Issue
Open
opened 2026-07-16 21:28:46 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-07-16 21:28:46 +00:00
Owner
Copy Link

Summary

https://mosaicstack.dev/install.sh returns HTTP 500. This is the install path advertised at the top of tools/install.sh and is presumably the one most users hit first.

Reproduction

$ curl -fsSL -o /dev/null -w "http=%{http_code}\n" https://mosaicstack.dev/install.sh
curl: (22) The requested URL returned error: 500
http=500

Observed 2026-07-16 from a Fedora Kinoite workstation. The Gitea raw path is healthy by contrast:

$ curl -fsSL -o /dev/null -w "http=%{http_code}\n" https://git.mosaicstack.dev/mosaicstack/stack/raw/branch/next/tools/install.sh
http=200

So this is an issue with the mosaicstack.dev endpoint/redirect itself, not with Gitea or the installer script.

Impact

The documented quick-start is fully broken:

curl -fsSL https://mosaicstack.dev/install.sh | bash

Because the fetch fails before bash ever receives a script, the failure is opaque — it never reaches argument parsing, so any flags the user passed are irrelevant and unreported. This compounded with # (unknown-flag silent ignore) to make a next-lane install failure very hard to diagnose.

Expected

mosaicstack.dev/install.sh serves the installer (200), presumably proxying/redirecting to the Gitea raw URL.

Notes

Worth adding an uptime/synthetic check on this URL — it is the front door and currently fails silently from the user's perspective.

## Summary `https://mosaicstack.dev/install.sh` returns **HTTP 500**. This is the install path advertised at the top of `tools/install.sh` and is presumably the one most users hit first. ## Reproduction ``` $ curl -fsSL -o /dev/null -w "http=%{http_code}\n" https://mosaicstack.dev/install.sh curl: (22) The requested URL returned error: 500 http=500 ``` Observed 2026-07-16 from a Fedora Kinoite workstation. The Gitea raw path is healthy by contrast: ``` $ curl -fsSL -o /dev/null -w "http=%{http_code}\n" https://git.mosaicstack.dev/mosaicstack/stack/raw/branch/next/tools/install.sh http=200 ``` So this is an issue with the mosaicstack.dev endpoint/redirect itself, not with Gitea or the installer script. ## Impact The documented quick-start is fully broken: ``` curl -fsSL https://mosaicstack.dev/install.sh | bash ``` Because the fetch fails before bash ever receives a script, the failure is opaque — it never reaches argument parsing, so any flags the user passed are irrelevant and unreported. This compounded with #<UNKNOWN> (unknown-flag silent ignore) to make a next-lane install failure very hard to diagnose. ## Expected `mosaicstack.dev/install.sh` serves the installer (200), presumably proxying/redirecting to the Gitea raw URL. ## Notes Worth adding an uptime/synthetic check on this URL — it is the front door and currently fails silently from the user's perspective.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#803
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?