Hi,
I’ve been creating a website using Deepsite in a private space. Everything worked great until recently. The problem now is that when I go to the space at https://deepsite.hf.co/username/my-project, I get greeted with a ‘Oh no! Page not found. The page you are looking for does not exist.’ message.
deepsite . hf . co also doesn’t show my project anymore despite seeing it on https://huggingface.co/spaces/username/my-project
How can I get back to the URL where I can edit the website?
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.
However, 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.”
For 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.
As 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.
If 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.
Following is just an unofficial / LLM-generated triage note, not an official DeepSite or Hugging Face answer:
The following is not an official DeepSite or Hugging Face answer.
This 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.
I 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.
This looks like a DeepSite project/editor recovery issue, not simply “the Hugging Face Space disappeared”.
If the generated Space repo still exists here:
https://huggingface.co/spaces/<username>/<project>
then the generated files may still be recoverable from the Space repo.
But 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.
So for issues like:
deepsite.hf.co/... project URL now shows “Page not found”the most useful path is probably:
Ask the DeepSite maintainer / current DeepSite support channel.
General 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.
There are two separate things involved:
Example:
https://huggingface.co/spaces/<username>/<project>
This is the Space repo on Hugging Face. It may still contain the generated website files.
Example patterns:
https://deepsite.hf.co/projects/<username>/<project>
or older/alternate DeepSite project URLs.
This is the DeepSite-side route that may reopen the project in the DeepSite editor.
Those two are related, but not necessarily identical.
A Space repo can still exist while the DeepSite project/editor URL no longer works.
That means:
“The Space exists” does not automatically mean “DeepSite can still reopen it as a DeepSite project.”
Old 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.
Example old V2-related commit:
linusorii/deepsite-v2 initial commit
Another old commit appears to add a “load existing project” flow:
Load existing project · linusorii/deepsite-v2
Based on those public traces, DeepSite project recovery may have required several things to line up:
Generated HF Space exists
+ DeepSite has a project record for it
+ logged-in user matches the expected owner
+ DeepSite can read Space metadata
+ DeepSite can fetch the generated HTML
= DeepSite can reopen the project/editor
So 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.
The current DeepSite app identifies itself as V4:
There are also commit-history traces around the current DeepSite Space showing project-route-related changes, including:
remove /projects route[BIG UPDATE] New generation filesadd base path deepsitefix api issueCommit history view:
enzostvs/deepsite commit history around my-projects
This does not prove the exact cause of this issue.
But it does make this hypothesis plausible:
Old DeepSite project URLs or old project recovery routes may have changed during the V3/V4 migration.
So this may be an undocumented breaking change, or a migration regression, or a private/protected Space handling issue.
Only the DeepSite maintainer can really confirm which one it is.
Hugging Face now supports public, protected, and private Spaces.
The 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:
Spaces Overview — Space visibility
The custom domain docs also say custom domains require public or protected visibility:
This means the following pattern can be expected for a protected Space:
Running app is still accessible:
https://deepsite.hf.co
https://enzostvs-deepsite.hf.space
But Hub repo/source/community may not be publicly visible:
https://huggingface.co/spaces/enzostvs/deepsite
https://huggingface.co/spaces/enzostvs/deepsite/discussions
So 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.
That would explain why the old Community tab is no longer a reliable support path.
However, this only explains the DeepSite tool’s own repo/community visibility.
It does not fully explain why an individual user’s old DeepSite project URL fails.
That second problem still depends on DeepSite’s own project/editor logic.
There is a public commit trace showing a Discord Community button in DeepSite navigation:
Download project as Zip · enzostvs/deepsite
The visible invite in that commit is:
This suggests that DeepSite intended Discord to be a community/support route, or at least one official-ish place where DeepSite users could go.
I 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.
This exact issue may be hard to search for because users describe it differently.
Related DeepSite confusion includes:
login leads to 404
I cant access deepsite. its asking me to login but showing 404 error
login/authorization loop
Unable to use Deepsite - Log in problem
first-time login error
I’m trying to use Deepsite for the first time but 400 error login
saving project fails with huggingface.co refused to connect
Saving Project in DeepSight AI Generator
users want to edit DeepSite-generated websites after generation
How to edit website after huggingface has built it
DeepSite-specific feature questions where the practical answer is “ask the author”
How can I create a new page theme that still inherits the home page style?
DeepSite output / TOS / usage questions where the answer also depends on the tool owner
Where in the TOS does it specify usage of things created with Deepsite?
These are not all the same bug. But they show a broader pattern:
DeepSite users often arrive in general Hugging Face channels, while many of the answers depend on DeepSite-specific implementation or policy.
HF Space build error
Better place to ask: HF Forum Spaces
.hf.space app URL is down
Better place to ask: HF Forum Spaces
public/private/protected Space visibility
Better place to ask: HF Forum Spaces or HF support
billing / Pro / ZeroGPU / Inference Providers
Better place to ask: HF billing/support or relevant HF Forum category
generated files need to be downloaded
Better place to ask: the generated Space repo / HF repo tools
manually editing the generated Space
Better place to ask: HF Space repo / Git / web dev help
DeepSite My Projects missing
Better place to ask: DeepSite maintainer / DeepSite Discord
old deepsite.hf.co/... URL shows Page not found
Better place to ask: DeepSite maintainer / DeepSite Discord
reopening the project in DeepSite editor
Better place to ask: DeepSite maintainer / DeepSite Discord
prompt history or DeepSite editor state recovery
Better place to ask: DeepSite maintainer / DeepSite Discord
private/protected Space support inside DeepSite
Better place to ask: DeepSite maintainer / DeepSite Discord
fork/local DeepSite version
Better place to ask: that fork’s maintainer
A useful rule of thumb:
HF can help with the generated Space as a Space.
DeepSite maintainers are needed for DeepSite project/editor state.
If the generated Space repo still exists, back it up before doing anything risky.
Possible recovery steps:
Open the Space repo:
https://huggingface.co/spaces/<username>/<project>
Download or copy files from the Files tab.
Clone the Space repo with git.
Save at least:
index.htmlCheck whether the running Space still works:
https://<username>-<project>.hf.spacehttps://<username>-<project>.static.hf.space for static SpacesThis may not restore the DeepSite editor state, but it can preserve the generated website.
Please include both sides of the problem:
Failing DeepSite URL:
https://deepsite.hf.co/...
Generated Space repo:
https://huggingface.co/spaces/<username>/<project>
Also include:
.hf.space app URL still worksA good neutral way to describe this is:
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.
Shorter version:
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.
If your goal is only to view or recover the generated website, use the Hugging Face Space repo and back up the files.
If 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.
The 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.
Again, this is an unofficial LLM-generated triage note, not an official answer.
Discord helped (posted there in parallel) and logging out/back in worked.