Hardware: Hetzner VPS YunoHost version: 11.1.11.2 (stable) I have access to my server : SSH and Webadmin Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no If yes, please explain: If your request is related to an app, specify its name and version: Gitea 1.17.4~ynh1 and/or Forgejo 1.18.5-0~ynh2
Description of my issue
Hello! So I have been trying to get Gitea/Forgejo (issue reproduces basically identically between either, the main goal currently is to get Forgejo working however) working for a few months now, with the same issue happening every time.
What happens is:
I install Gitea/Forgejo
I go to the app and check my profile
Instead of my email being the correct nick@tar.black, it shows up as something like [random-hash]@localhost
For example right now I have both Forgejo and Gitea installed to see if both apps are still having the issues, and the emails are 05d193c6-32ed-429a-ab69-9609977c179a@localhost and dd5857ab-dc52-4031-84a0-991e9db04c08@localhost respectively.
I really would appreciate if someone could find the root of this issue, here are the logs from a fresh reinstall and then me accessing the Forgejo page to initialise my account, if that helps: https://paste.yunohost.org/raw/evaxotafeg
I looked at both Gitea and Forgejo and got the same as you… I didn’t have this problem with my rewrite of Gitea GitHub - ericgaspar/gitea_ynh where I get the email to display correctly. Might be worth looking for the diffs between the different app.ini config files…
I’ve just finished looking into this and I think I might know the culprit in that case
The difference is in how the LDAP auth is added to Gitea I believe.
I can only assume it was enabled to allow the Single Sign-On / Proxy Auth to work, but if it breaks the whole authorisation process it might be best to disable it until a fix is found
@mchal and I will use the Forgejo instance on tar.black with ENABLE_REVERSE_PROXY_AUTHENTICATION set to false. Thank you for your help @ericg (and @mchal), and let us know if there are changes to YunoHost or the Forgejo app that will allow for login with SSO without breaking things Thanks!
Yes! This seems as if it may have worked. I spun up a test YunoHost instance on a separate Hetzner VPS @ <domain.tld>, and after installing Forgejo from my fork with your commits on it (https://github.com/futiiile/forgejo_ynh), it seems to have worked right away!
Thank you for figuring it out, I hope to see this fix on the main branch soon!
(Also, maybe someone should apply this fix to the Gitea package too as it has the same issue )
Thanks!