Deployed Pages Remain after Repo or User is Deleted

veganmosfet commented

2026-02-21 06:22:53 +01:00

Comment

When using the Codeberg Pages (New Method), the pages at xxx.codeberg.page remain published and available even after the pages repo is deleted - and even after the codeberg user is deleted (> 12 hours).
Is it possible to delete them within a short time (1 hour) after deletion of repo and / or user?

### Comment When using the Codeberg Pages (New Method), the pages at xxx.codeberg.page remain published and available even after the *pages* repo is deleted - and even after the *codeberg user* is deleted (> 12 hours). Is it possible to delete them within a short time (1 hour) after deletion of repo and / or user?

👍 3

mahlzahn added the

s/Pages

Codeberg

labels

2026-02-21 08:15:51 +01:00

RemiBardon commented

2026-02-22 04:58:56 +01:00

I have a similar issue, which is that I published Pages to multiple codeberg.page domains while I was debugging stuff. Now I have my Pages being served correctly, but old versions still laying around. I’d like to delete them like I did with grebedoc.dev using git-pages-cli but I can’t seem to figure out which “site”, “server”, “token” and “password” to use… here is what I’ve tried so far:

git-pages-cli https://<username>.codeberg.page --password "${CODEBERG_TOKEN:?}" --delete
result: error
unauthorized
- failed to look up DNS challenge: _git-pages-challenge.<username>.codeberg.page TXT
# This was a mistake, of course it wasn’t going to work

git-pages-cli https://<username>.codeberg.page --token "${CODEBERG_TOKEN:?}" --delete
result: error
unauthorized
- missing Authorization header

git-pages-cli https://codeberg.page/<username> --token "${CODEBERG_TOKEN:?}" --delete
result: error
Method not allowed

git-pages-cli https://<username>.codeberg.page --server codeberg.page --token "${CODEBERG_TOKEN:?}" --delete
result: error
Method not allowed

git-pages-cli https://<username>.codeberg.page --server codeberg.org --token "${CODEBERG_TOKEN:?}" --delete
result:
# Page still online

git-pages-cli http://<username>.codeberg.page --server codeberg.org --token "${CODEBERG_TOKEN:?}" --delete
result:
<!doctype html>…
# Why do I get the page when deleting?

git-pages-cli http://<username>.codeberg.page --server codeberg.page --token "${CODEBERG_TOKEN:?}" --delete
result:
<!doctype html>…
# Same thing on codeberg.page

git-pages-cli http://codeberg.page/<username> --server codeberg.org --token "${CODEBERG_TOKEN:?}" --delete
result: error
<!doctype html>
<html class="codeberg-design">…
# At this point I’m just messing around

# In a Forgejo Actions workflow:
git-pages-cli http://<username>.codeberg.page --server codeberg.org --token '${{ forge.token }}' --delete
result:
# Page still online

I have a similar issue, which is that I published Pages to multiple `codeberg.page` domains while I was debugging stuff. Now I have my Pages being served correctly, but old versions still laying around. I’d like to delete them like I did with `grebedoc.dev` using `git-pages-cli` but I can’t seem to figure out which “site”, “server”, “token” and “password” to use… here is what I’ve tried so far: ```bash git-pages-cli https://<username>.codeberg.page --password "${CODEBERG_TOKEN:?}" --delete result: error unauthorized - failed to look up DNS challenge: _git-pages-challenge.<username>.codeberg.page TXT # This was a mistake, of course it wasn’t going to work git-pages-cli https://<username>.codeberg.page --token "${CODEBERG_TOKEN:?}" --delete result: error unauthorized - missing Authorization header git-pages-cli https://codeberg.page/<username> --token "${CODEBERG_TOKEN:?}" --delete result: error Method not allowed git-pages-cli https://<username>.codeberg.page --server codeberg.page --token "${CODEBERG_TOKEN:?}" --delete result: error Method not allowed git-pages-cli https://<username>.codeberg.page --server codeberg.org --token "${CODEBERG_TOKEN:?}" --delete result: # Page still online git-pages-cli http://<username>.codeberg.page --server codeberg.org --token "${CODEBERG_TOKEN:?}" --delete result: <!doctype html>… # Why do I get the page when deleting? git-pages-cli http://<username>.codeberg.page --server codeberg.page --token "${CODEBERG_TOKEN:?}" --delete result: <!doctype html>… # Same thing on codeberg.page git-pages-cli http://codeberg.page/<username> --server codeberg.org --token "${CODEBERG_TOKEN:?}" --delete result: error <!doctype html> <html class="codeberg-design">… # At this point I’m just messing around # In a Forgejo Actions workflow: git-pages-cli http://<username>.codeberg.page --server codeberg.org --token '${{ forge.token }}' --delete result: # Page still online ```

whitequark commented

2026-02-24 10:57:04 +01:00

Member

I have a similar issue, which is that I published Pages to multiple codeberg.page domains while I was debugging stuff. Now I have my Pages being served correctly, but old versions still laying around. I’d like to delete them like I did with grebedoc.dev using git-pages-cli but I can’t seem to figure out which “site”, “server”, “token” and “password” to use… here is what I’ve tried so far:

You should be able to create a token for your user (make sure it has at least "repository: read and write" level of permission) then use git-pages-cli with the --token ... --delete options to remove it. Let me know if that fails.

> I have a similar issue, which is that I published Pages to multiple codeberg.page domains while I was debugging stuff. Now I have my Pages being served correctly, but old versions still laying around. I’d like to delete them like I did with grebedoc.dev using git-pages-cli but I can’t seem to figure out which “site”, “server”, “token” and “password” to use… here is what I’ve tried so far: You should be able to [create a token for your user](https://codeberg.org/user/settings/applications) (make sure it has at least "repository: read and write" level of permission) then use git-pages-cli with the `--token ... --delete` options to remove it. Let me know if that fails.

whitequark referenced this issue from git-pages/git-pages-cli

2026-02-24 11:12:56 +01:00

Check for Server: header in responses and bail out if it's not a git-pages endpoint #23

whitequark commented

2026-02-24 11:15:40 +01:00

Member

Regarding the unexpected HTML responses, I filed git-pages/git-pages-cli#23 to track that.

Regarding the unexpected HTML responses, I filed https://codeberg.org/git-pages/git-pages-cli/issues/23 to track that.

❤️ 1

RemiBardon commented

2026-02-24 11:22:27 +01:00

You should be able to create a token for your user (make sure it has at least "repository: read and write" level of permission) then use git-pages-cli with the --token ... --delete options to remove it. Let me know if that fails.

@whitequark Thank you for your interest! Unfortunately that’s what the examples with --token "${CODEBERG_TOKEN:?}" used 😕 Did I miss the correct flag/arg combination?

> You should be able to [create a token for your user](https://codeberg.org/user/settings/applications) (make sure it has at least "repository: read and write" level of permission) then use git-pages-cli with the `--token ... --delete` options to remove it. Let me know if that fails. @whitequark Thank you for your interest! Unfortunately that’s what the examples with `--token "${CODEBERG_TOKEN:?}"` used 😕 Did I miss the correct flag/arg combination?

whitequark commented

2026-02-24 22:34:46 +01:00

Member

@RemiBardon Oh, right, we never implemented Forge-Authorization for DELETE requests. I'll make sure we do.

@RemiBardon Oh, right, we never implemented Forge-Authorization for `DELETE` requests. I'll make sure we do.

👍 1

whitequark referenced this issue from git-pages/git-pages

2026-02-24 22:35:32 +01:00

Implement Forge-Authorization for DELETE requests #116

Rows
Columns

Deployed Pages Remain after Repo or User is Deleted #2396

Comment