You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to organize my Projects wiki in folders. Some of the links work perfectly fine, some throw an 500 Error. For better understanding here the file/folder structure:
Both Markdown-Files entered the Repository with the same commit - Home.md works fine, L2Page.md throws a 500 Error: GetCommitByPath, object does not exist [id: L2Page.md, rel_path: ], though when cloning the Repository the file shows up, is editable, also can be pushed to the repository again. The 500 Error stays, even after editing and recommiting/pushing the file multiple times.
That file is just an example, i have several markdown files throwing the same error, not necesarily in a level 2 subfolder, some files from Level1 Subfolders also throw the error when accessing them via the gitea wiki.
My Links from the HomePage to the subfolders look like this (from global start page to Level1-Home, working):
* [[TopLevel1/Home.md]]
From Level1 Homepage to L2Page.md (throwing 500):
* [[TopLevel1/TopLevel2/L2Page.md]]
I run gitea from the latest docker image, even with Debug-Logging enabled there are no clues on whats going wrong:
2024/10/13 19:18:58 ...dules/git/command.go:291:Run() [D] git.Command.RunDir(/data/git/repositories/organisation/repository.wiki.git): /usr/bin/git -c protocol.version=2 -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= log -1 --pretty=format:%H -- L2Page.md
2024/10/13 19:18:58 ...ers/web/repo/wiki.go:587:Wiki() [E] GetCommitByPath: object does not exist [id: L2Page.md, rel_path: ]
2024/10/13 19:18:58 .../context_response.go:70:HTML() [D] Template: status/500
2024/10/13 19:18:58 ...eb/routing/logger.go:102:func1() [I] router: completed GET /organisation/repository/wiki/TopLevel1/TopLevel2/L2Page.md for 192.168.178.59:0, 500 Internal Server Error in 57.4ms @ repo/wiki.go:532(repo.Wiki)
While troubleshooting I did a
git ls-files | grep L2Page.md
fatal: detected dubious ownership in repository at '/data/git/repositories/organisation/repository.wiki.git'
Docker Compose file with no special configuration, I can provide it later. Traefik is used for SSL Offloading and LetsEncrypt, the gitea container is using port 22 for SSH (git clone, git push etc.)
Database
PostgreSQL
The text was updated successfully, but these errors were encountered:
Description
I'm trying to organize my Projects wiki in folders. Some of the links work perfectly fine, some throw an 500 Error. For better understanding here the file/folder structure:
Both Markdown-Files entered the Repository with the same commit - Home.md works fine, L2Page.md throws a 500 Error:
GetCommitByPath, object does not exist [id: L2Page.md, rel_path: ]
, though when cloning the Repository the file shows up, is editable, also can be pushed to the repository again. The 500 Error stays, even after editing and recommiting/pushing the file multiple times.That file is just an example, i have several markdown files throwing the same error, not necesarily in a level 2 subfolder, some files from Level1 Subfolders also throw the error when accessing them via the gitea wiki.
My Links from the HomePage to the subfolders look like this (from global start page to Level1-Home, working):
From Level1 Homepage to L2Page.md (throwing 500):
I run gitea from the latest docker image, even with Debug-Logging enabled there are no clues on whats going wrong:
While troubleshooting I did a
and set
but that did not solve the issue.
Gitea Version
1.22.3 (latest docker)
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Ubuntu 22.04 - docker compose
How are you running Gitea?
Docker Compose file with no special configuration, I can provide it later. Traefik is used for SSL Offloading and LetsEncrypt, the gitea container is using port 22 for SSH (git clone, git push etc.)
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: