[Docs] Instructions for Apache reverse proxy with Certbot #4489

New Issue

GiteaMirror · 2025-11-02T05:52:31-06:00

GiteaMirror commented

2025-11-02 05:52:31 -06:00

Originally created by @nztim on GitHub (Dec 15, 2019).

I've just spent a bit of time trying to configure Apache as a reverse proxy for Gitea. It works fine as per the docs until you want to use Certbot. It seems to me that the configuration in the docs results in the acme challenge being proxied to Gitea (and a 404) regardless of whether you have a document root, an alias in place or anything.

The solution I used was to add ProxyPass /.well-known ! on the line before ProxyPass / http://localhost:3000/ nocanon, there may be other solutions. Do you think this would be useful to add to the docs?

Originally created by @nztim on GitHub (Dec 15, 2019). I've just spent a bit of time trying to configure Apache as a reverse proxy for Gitea. It works fine as per the docs until you want to use Certbot. It seems to me that the configuration in the docs results in the acme challenge being proxied to Gitea (and a 404) regardless of whether you have a document root, an alias in place or anything. The solution I used was to add `ProxyPass /.well-known !` on the line before `ProxyPass / http://localhost:3000/ nocanon`, there may be other solutions. Do you think this would be useful to add to the docs?

GiteaMirror added the issue/stale type/docs labels 2025-11-02 05:52:31 -06:00

GiteaMirror closed this issue

2025-11-02 05:52:31 -06:00

GiteaMirror commented

2025-11-02 05:52:32 -06:00

@lunny commented on GitHub (Dec 16, 2019):

Please send a PR and we can discuss there.

@lunny commented on GitHub (Dec 16, 2019): Please send a PR and we can discuss there.

GiteaMirror commented

2025-11-02 05:52:32 -06:00

@stale[bot] commented on GitHub (Feb 14, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 14, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:52:32 -06:00

@techknowlogick commented on GitHub (Feb 14, 2020):

Closing as this has been added to docs

@techknowlogick commented on GitHub (Feb 14, 2020): Closing as this has been added to docs

GiteaMirror referenced this issue

2025-11-02 10:08:53 -06:00

Make Change Password on First Sign In optional in config #12407

GiteaMirror referenced this issue

2025-11-02 13:09:08 -06:00

[PR #4489] [MERGED] Force user to change password #17397

Sign in to join this conversation.