Forgejo error
Hello!
I am using the newest version of Forgejo, and I set up a Git connection using this tutorial: https://docs.dokploy.com/docs/core/gitea.
I can not see any of my repositories. The Test Connection throws me 403, however, the Connect to Gitea button works.
22 Replies
Same here
Gitea not connected
I have checked the code, the issue is 'gitea_id not found '
GitHub
dokploy/packages/server/src/utils/providers/gitea.ts at e83efa33795...
Open Source Alternative to Vercel, Netlify and Heroku. - Dokploy/dokploy
Error throw here i think
https://github.com/Dokploy/dokploy/blob/e83efa3379504afe686de8af0738eefda7ce916d/packages/server/src/services/gitea.ts#L76
GitHub
dokploy/packages/server/src/services/gitea.ts at e83efa3379504afe68...
Open Source Alternative to Vercel, Netlify and Heroku. - Dokploy/dokploy
What is Forgejo?
Forgejo – Beyond coding. We forge.
Forgejo is a self-hosted lightweight software forge. Easy to install and low maintenance, it just does the job.
forgejo is a fresh fork of gitea and it's developed in-house on their own forgejo instance
we added a one-click template for it
https://templates.dokploy.com/?q=forgejo
I would guess they then do some things differently than Gitea. The Gitea provider works wonderfully with the official Gitea container
I have checked logs from forgejo in my docker and it seems like Forgejo may have some different way to fetch repos than Gitea.
Thats the 403 Forbidden error.
In that case I guess you can't use it, it's for gitea
I have shared an error code section
Gitea_id not found.
This is the main issue
I can try and add support for Forgejo
Thanks brother
can you share the logs file?
Which log file?
nvm
Where can I get it?
don't worry about it
Okey
I would really appreciate it, thank you!
I just encountered this error with my Forgejo instance as well, I figured it would have been close enough to Gitea to where it would just work. I'll see if I can dig into the Gitea integration over the next few days see where it differs from Forgejo.
Right now, I'm thinking it's related to the way the scopes are being included in the API requests:
403 Forbidden in 4.1ms @ v1/api.go:336(v1.Routes.func2.7.tokenRequiresScopes.16)