{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreiftyfgqg3ahcsg7agpcon4bwjytd63p75rizlmxet3js6ab2vkhsu",
"uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mkjbluoq4e22"
},
"path": "/t/deepsite-page-not-found-error/175600#post_2",
"publishedAt": "2026-04-27T23:07:09.000Z",
"site": "https://discuss.huggingface.co",
"tags": [
"linusorii/deepsite-v2 initial commit",
"Load existing project · linusorii/deepsite-v2",
"DeepSite v4 app",
"enzostvs/deepsite commit history around my-projects",
"Spaces Overview — Space visibility",
"Spaces Custom Domain",
"Download project as Zip · enzostvs/deepsite",
"https://discord.gg/KpanwM3vXa",
"I cant access deepsite. its asking me to login but showing 404 error",
"Unable to use Deepsite - Log in problem",
"I’m trying to use Deepsite for the first time but 400 error login",
"Saving Project in DeepSight AI Generator",
"How to edit website after huggingface has built it",
"How can I create a new page theme that still inherits the home page style?",
"Where in the TOS does it specify usage of things created with Deepsite?"
],
"textContent": "There are a lot of questions about `DeepSite`, and if the issue is on the HF side, asking HF or HF users may help you find a clue.\n\nHowever, for many DeepSite-specific issues, the realistic answer is probably: “only the author of `DeepSite` really knows how `DeepSite` works internally, and only the author can fix DeepSite-side issues.”\n\nFor example, if the generated HF Space still exists, HF users may be able to help you recover the files from that Space. But if the problem is that DeepSite can no longer reopen the project, the project disappeared from DeepSite, or an old `deepsite.hf.co/...` URL now returns “Page not found”, that is probably about DeepSite’s own project/editor logic.\n\nAs far as I could find, the most likely place for DeepSite bug reports/support right now is the dedicated DeepSite Discord server. There used to be a DeepSite Space/Community on HF, but it looks like it may now be protected or otherwise not publicly accessible on the Hub, so normal users may not be able to post there anymore.\n\nIf you just want to contact the author, X or GitHub/profile links may also be possible. But for actual bug reports or project recovery, the Discord seems more likely to be the right place.\n\nFollowing is just an unofficial / LLM-generated triage note, not an official DeepSite or Hugging Face answer:\n\n* * *\n\n## Unofficial / LLM-generated triage notes\n\nThe following is **not an official DeepSite or Hugging Face answer**.\n\nThis is an **LLM-generated summary** based on public Hugging Face docs, old DeepSite commits/forks, and related HF Forum posts. Please treat it as a triage guide and hypothesis, not as a confirmed diagnosis.\n\nI am writing this because DeepSite questions seem to get scattered across HF Forum, HF Discord, Reddit, X, and old Space Community pages, and it is easy for users to get lost.\n\n* * *\n\n## Short answer\n\nThis looks like a **DeepSite project/editor recovery issue** , not simply “the Hugging Face Space disappeared”.\n\nIf the generated Space repo still exists here:\n\n`https://huggingface.co/spaces/<username>/<project>`\n\nthen the generated files may still be recoverable from the Space repo.\n\nBut opening or continuing the project through DeepSite is a different thing. DeepSite appears to have its own project/editor state, project lookup logic, URL routing, and import/recovery behavior.\n\nSo for issues like:\n\n * old `deepsite.hf.co/...` project URL now shows “Page not found”\n * project disappeared from DeepSite “My Projects”\n * existing Space cannot be reopened in DeepSite\n * private/protected Space does not show up in DeepSite\n * old project URL used to work but no longer does\n * prompt/editor state needs to be restored\n\n\n\nthe most useful path is probably:\n\n> **Ask the DeepSite maintainer / current DeepSite support channel.**\n\nGeneral HF users can help check the underlying Space repo, but they probably cannot determine whether DeepSite V4 still supports an old project/editor route or can reconnect the project.\n\n* * *\n\n## Why this is probably not enough for general HF Forum users to solve\n\nThere are two separate things involved:\n\n### 1. The generated Hugging Face Space\n\nExample:\n\n`https://huggingface.co/spaces/<username>/<project>`\n\nThis is the Space repo on Hugging Face. It may still contain the generated website files.\n\n### 2. The DeepSite project/editor entry\n\nExample patterns:\n\n`https://deepsite.hf.co/projects/<username>/<project>`\n\nor older/alternate DeepSite project URLs.\n\nThis is the DeepSite-side route that may reopen the project in the DeepSite editor.\n\nThose two are related, but not necessarily identical.\n\nA Space repo can still exist while the DeepSite project/editor URL no longer works.\n\nThat means:\n\n> “The Space exists” does not automatically mean “DeepSite can still reopen it as a DeepSite project.”\n\n* * *\n\n## Evidence / clues\n\n### 1. DeepSite V2-like code appears to have used DeepSite-side project records\n\nOld public V2-related code/forks suggest DeepSite stored project metadata on the DeepSite side, keyed by things like `user_id` and `space_id`, and then used that to reopen projects.\n\nExample old V2-related commit:\n\nlinusorii/deepsite-v2 initial commit\n\nAnother old commit appears to add a “load existing project” flow:\n\nLoad existing project · linusorii/deepsite-v2\n\nBased on those public traces, DeepSite project recovery may have required several things to line up:\n\n\n Generated HF Space exists\n + DeepSite has a project record for it\n + logged-in user matches the expected owner\n + DeepSite can read Space metadata\n + DeepSite can fetch the generated HTML\n = DeepSite can reopen the project/editor\n\n\nSo even if the HF Space repo still exists, DeepSite can still fail to reopen the project if DeepSite’s own lookup/import/editor state has changed or cannot access it.\n\n* * *\n\n### 2. DeepSite V4 seems to have changed project routes\n\nThe current DeepSite app identifies itself as V4:\n\nDeepSite v4 app\n\nThere are also commit-history traces around the current DeepSite Space showing project-route-related changes, including:\n\n * `remove /projects route`\n * `[BIG UPDATE] New generation files`\n * `add base path deepsite`\n * `fix api issue`\n\n\n\nCommit history view:\n\nenzostvs/deepsite commit history around my-projects\n\nThis does **not** prove the exact cause of this issue.\n\nBut it does make this hypothesis plausible:\n\n> Old DeepSite project URLs or old project recovery routes may have changed during the V3/V4 migration.\n\nSo this may be an undocumented breaking change, or a migration regression, or a private/protected Space handling issue.\n\nOnly the DeepSite maintainer can really confirm which one it is.\n\n* * *\n\n### 3. The original DeepSite Space Community may no longer be publicly accessible\n\nHugging Face now supports public, protected, and private Spaces.\n\nThe official docs explain that **protected Spaces keep source code private on the Hub, while the running app remains publicly accessible through the`hf.space` URL or custom domain**:\n\nSpaces Overview — Space visibility\n\nThe custom domain docs also say custom domains require public or protected visibility:\n\nSpaces Custom Domain\n\nThis means the following pattern can be expected for a protected Space:\n\n\n Running app is still accessible:\n https://deepsite.hf.co\n https://enzostvs-deepsite.hf.space\n\n But Hub repo/source/community may not be publicly visible:\n https://huggingface.co/spaces/enzostvs/deepsite\n https://huggingface.co/spaces/enzostvs/deepsite/discussions\n\n\nSo if the old DeepSite Space Community returns 404 for regular users, that may be because the DeepSite app Space is now protected or otherwise no longer public on the Hub.\n\nThat would explain why the old Community tab is no longer a reliable support path.\n\nHowever, this only explains the DeepSite tool’s own repo/community visibility.\n\nIt does **not** fully explain why an individual user’s old DeepSite project URL fails.\n\nThat second problem still depends on DeepSite’s own project/editor logic.\n\n* * *\n\n### 4. DeepSite had a Discord Community link in the app UI\n\nThere is a public commit trace showing a **Discord Community** button in DeepSite navigation:\n\nDownload project as Zip · enzostvs/deepsite\n\nThe visible invite in that commit is:\n\nhttps://discord.gg/KpanwM3vXa\n\nThis suggests that DeepSite intended Discord to be a community/support route, or at least one official-ish place where DeepSite users could go.\n\nI cannot verify from outside whether that Discord is still actively maintained, but it is a stronger lead than asking random HF users, because it was linked from the DeepSite app itself.\n\n* * *\n\n## Related symptom clusters\n\nThis exact issue may be hard to search for because users describe it differently.\n\nRelated DeepSite confusion includes:\n\n * login leads to 404\nI cant access deepsite. its asking me to login but showing 404 error\n\n * login/authorization loop\nUnable to use Deepsite - Log in problem\n\n * first-time login error\nI’m trying to use Deepsite for the first time but 400 error login\n\n * saving project fails with `huggingface.co refused to connect`\nSaving Project in DeepSight AI Generator\n\n * users want to edit DeepSite-generated websites after generation\nHow to edit website after huggingface has built it\n\n * DeepSite-specific feature questions where the practical answer is “ask the author”\nHow can I create a new page theme that still inherits the home page style?\n\n * DeepSite output / TOS / usage questions where the answer also depends on the tool owner\nWhere in the TOS does it specify usage of things created with Deepsite?\n\n\n\n\nThese are not all the same bug. But they show a broader pattern:\n\n> DeepSite users often arrive in general Hugging Face channels, while many of the answers depend on DeepSite-specific implementation or policy.\n\n* * *\n\n## Triage: where to ask\n\n * **HF Space build error**\nBetter place to ask: HF Forum `Spaces`\n\n * **`.hf.space` app URL is down**\nBetter place to ask: HF Forum `Spaces`\n\n * **public/private/protected Space visibility**\nBetter place to ask: HF Forum `Spaces` or HF support\n\n * **billing / Pro / ZeroGPU / Inference Providers**\nBetter place to ask: HF billing/support or relevant HF Forum category\n\n * **generated files need to be downloaded**\nBetter place to ask: the generated Space repo / HF repo tools\n\n * **manually editing the generated Space**\nBetter place to ask: HF Space repo / Git / web dev help\n\n * **DeepSite My Projects missing**\nBetter place to ask: DeepSite maintainer / DeepSite Discord\n\n * **old`deepsite.hf.co/...` URL shows Page not found**\nBetter place to ask: DeepSite maintainer / DeepSite Discord\n\n * **reopening the project in DeepSite editor**\nBetter place to ask: DeepSite maintainer / DeepSite Discord\n\n * **prompt history or DeepSite editor state recovery**\nBetter place to ask: DeepSite maintainer / DeepSite Discord\n\n * **private/protected Space support inside DeepSite**\nBetter place to ask: DeepSite maintainer / DeepSite Discord\n\n * **fork/local DeepSite version**\nBetter place to ask: that fork’s maintainer\n\n\n\n\nA useful rule of thumb:\n\n> HF can help with the generated Space as a Space.\n> DeepSite maintainers are needed for DeepSite project/editor state.\n\n* * *\n\n## What to back up first\n\nIf the generated Space repo still exists, back it up before doing anything risky.\n\nPossible recovery steps:\n\n 1. Open the Space repo:\n\n`https://huggingface.co/spaces/<username>/<project>`\n\n 2. Download or copy files from the `Files` tab.\n\n 3. Clone the Space repo with git.\n\n 4. Save at least:\n\n * `index.html`\n * CSS files\n * JS files\n * assets/images\n * README metadata\n * any generated project files\n 5. Check whether the running Space still works:\n\n * `https://<username>-<project>.hf.space`\n * or possibly `https://<username>-<project>.static.hf.space` for static Spaces\n\n\n\nThis may not restore the DeepSite editor state, but it can preserve the generated website.\n\n* * *\n\n## What to include when reporting to DeepSite support\n\nPlease include both sides of the problem:\n\n### DeepSite side\n\n\n Failing DeepSite URL:\n https://deepsite.hf.co/...\n\n\n### Hugging Face Space side\n\n\n Generated Space repo:\n https://huggingface.co/spaces/<username>/<project>\n\n\nAlso include:\n\n * whether the Space is public / protected / private\n * whether the Space repo still exists\n * whether the `.hf.space` app URL still works\n * whether the project appears in DeepSite My Projects\n * whether DeepSite can import the Space URL\n * when the DeepSite URL last worked\n * browser and OS\n * login status\n * whether strict tracking protection or third-party cookie blocking is enabled\n * screenshot of the exact “Page not found” page\n\n\n\n* * *\n\n## A neutral summary for this specific class of issue\n\nA good neutral way to describe this is:\n\n> The generated Hugging Face Space still exists, but the old DeepSite project/editor URL no longer resolves. This suggests that the generated site/repo and the DeepSite project/editor entry are separate. The issue may be related to DeepSite V4 route changes, project lookup, import behavior, or private/protected Space handling. General HF users can help check the Space repo, but whether the old DeepSite URL should still work probably needs DeepSite maintainer clarification.\n\nShorter version:\n\n> This looks less like “the Space is gone” and more like “DeepSite can no longer reopen this Space as a DeepSite project.” That is probably not something the general HF community can determine from the outside.\n\n* * *\n\n## Bottom line\n\nIf your goal is only to view or recover the generated website, use the Hugging Face Space repo and back up the files.\n\nIf your goal is to reopen the project in DeepSite, continue editing with prompts, recover prompt/editor state, or understand why an old DeepSite project URL now returns “Page not found”, this probably needs DeepSite maintainer clarification.\n\nThe most practical next step is likely the DeepSite Discord / current DeepSite support channel, because the old Space Community route may no longer be publicly accessible.\n\nAgain, this is an unofficial LLM-generated triage note, not an official answer.",
"title": "Deepsite Page not found error"
}