"internal server error" on edwinvanl/rtttex wiki #1570

edwinvanl commented 2024年05月21日 19:52:34 +02:00

Comment

I tried to setup a wiki here: https://codeberg.org/edwinvanl/rtttex/wiki/?action=_pages, but it broke the wiki. I have tried to repair it, by checking out and cleaning up the page, but that did not work. The wiki git repository currently contains one markdown file and one gif.

### Comment I tried to setup a wiki here: https://codeberg.org/edwinvanl/rtttex/wiki/?action=_pages, but it broke the wiki. I have tried to repair it, by checking out and cleaning up the page, but that did not work. The wiki git repository currently contains one markdown file and one gif.

n0toose commented 2024年05月21日 23:02:48 +02:00

Sounds very similar to #1566, could you please describe what you did (did you create the wiki and it broke right off the bat)?

Sounds very similar to https://codeberg.org/Codeberg/Community/issues/1566, could you please describe what you did (did you create the wiki and it broke right off the bat)?

edwinvanl commented 2024年05月22日 09:20:33 +02:00

I did notice that one, but their solution did not seem relevant to my issue at all, so decided to open a new issue instead.

The steps I took as far as I remember:

1. Enable the wiki
2. Add a new page. The new page had a header (## header) and one (temporary) dead link [vhs]()
3. When saving this, I got the internal server error.
4. I tried to fix it, by pulling the wiki repository and removing the dead link. Even after pushing that, it is still broken.

I did notice that one, but their solution did not seem relevant to my issue at all, so decided to open a new issue instead. The steps I took as far as I remember: 1. Enable the wiki 2. Add a new page. The new page had a header (## header) and one (temporary) dead link `[vhs]()` 3. When saving this, I got the internal server error. 4. I tried to fix it, by pulling the wiki repository and removing the dead link. Even after pushing that, it is still broken.

algernon commented 2024年05月22日 16:48:40 +02:00

I can't reproduce this on neither 7.0.2, nor current 8.0. I'll keep trying.

I can't reproduce this on neither 7.0.2, nor current 8.0. I'll keep trying.

algernon commented 2024年05月22日 17:33:26 +02:00

Reproduced! Kinda.

@fnetX was kind enough to do a little digging on the Codeberg side, and it appears that when trying to list the wiki pages, Forgejo is trying to find a file named Screenshots.md - which does not exist on the main branch of the wiki.

However, it does exist on the develop branch! That, in itself should not be a problem, because the Forgejo is supposed to look up wiki pages from the wiki's default branch (which should be main). In this particular case, it appears that the default branch was set to develop instead, and that confuses the heck out of Forgejo.

I had to fiddle with the database to reproduce it, but... I can reproduce it now, and that gives me a few ideas how to tackle this further.

The quick fix here, I believe, would be to delete the wiki completely ("Delete wiki data" on the repo settings page), and re-create it, making sure there's only one branch. I'm not 100% convinced that will work, it might result in the same situation we have now. I'm digging into this further, and will report back as I know more, and if I managed to figure out a safe way to fix the repo until a fix can be deployed.

Reproduced! Kinda. @fnetX was kind enough to do a little digging on the Codeberg side, and it appears that when trying to list the wiki pages, Forgejo is trying to find a file named `Screenshots.md` - which does not exist on the `main` branch of the wiki. However, it *does* exist on the `develop` branch! That, in itself should not be a problem, because the Forgejo is supposed to look up wiki pages from the wiki's default branch (which should be main). In this particular case, it appears that the default branch was set to `develop` instead, and that confuses the heck out of Forgejo. I had to fiddle with the database to reproduce it, but... I can reproduce it now, and that gives me a few ideas how to tackle this further. The quick fix here, I believe, would be to delete the wiki completely ("Delete wiki data" on the repo settings page), and re-create it, making sure there's only one branch. I'm not 100% convinced that will work, it might result in the same situation we have now. I'm digging into this further, and will report back as I know more, and if I managed to figure out a safe way to fix the repo until a fix can be deployed.

algernon commented 2024年05月22日 17:58:49 +02:00

I think I now understand how this problem came to be. The repository was migrated from GitLab, right?

Meanwhile, I think the easiest way to resolve the situation until a fix can be deployed on the Codeberg/Forgejo side is to delete the wiki completely and recreate it. This should Just Work. You may even see a "Normalize the Wiki branch name" button near the bottom of the repo settings page. That is safe - and a good idea! - to press in this case.

I think I now understand how this problem came to be. The repository was migrated from GitLab, right? Meanwhile, I think the easiest way to resolve the situation until a fix can be deployed on the Codeberg/Forgejo side is to delete the wiki completely and recreate it. This should Just Work. You may even see a "Normalize the Wiki branch name" button near the bottom of the repo settings page. That is safe - and a good idea! - to press in this case.

edwinvanl commented 2024年05月22日 18:00:14 +02:00

Yes it is migrated from gitlab, although I only started the wiki after migrating to codeberg

Yes it is migrated from gitlab, although I only started the wiki after migrating to codeberg

edwinvanl commented 2024年05月27日 22:27:39 +02:00

Thanks, I deleted the data and recreated the wiki without further problems

Thanks, I deleted the data and recreated the wiki without further problems