Home page shows 688 No Reason Phrase #964

New Issue

GiteaMirror · 2025-11-02T03:43:26-06:00

GiteaMirror commented

2025-11-02 03:43:26 -06:00

Originally created by @rugk on GitHub (Aug 14, 2017).

Gitea version (or commit ref): v1.1.3
Operating system: Debian Jessie
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io: N/A
Log gist: everything works

Description

Accessing the home page shows "Found." using the error "688 No Reason Phrase".

Gitea runs behind an nginx reverse proxy installed in a subdirector (/subdir), which is correctly set as ROOT_URL in the settings.

I think this issue was introduced in one of the latter gitea versions, as previous versions were executed correctly.

Accessing /explore/repos (manually by changing the URL), however, works.

Also, the login does not work. It seems to execute something, but then returns "700 No Reason Phrase".

My nginx config is basically a location block to catch all static assets, which uses a try_files to redirect all other requests to a @proxy, which then does mostly this:

rewrite /subdir/(.*) /$1 break;
rewrite ^/subdir$ /subdir/ permanent;
proxy_buffering off;
# some proxy headers
proxy_pass […];

Screenshots

Originally created by @rugk on GitHub (Aug 14, 2017). - Gitea version (or commit ref): v1.1.3 - Operating system: Debian Jessie - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: N/A - Log gist: everything works ## Description Accessing the home page shows "<a href="/subdir/explore">Found</a>." using the error "688 No Reason Phrase". Gitea runs behind an nginx reverse proxy installed in a subdirector (`/subdir`), which is correctly set as `ROOT_URL` in the settings. I think this issue was introduced in one of the latter gitea versions, as previous versions were executed correctly. Accessing `/explore/repos` (manually by changing the URL), however, works. Also, the login does not work. It seems to execute something, but then returns "700 No Reason Phrase". My nginx config is basically a location block to catch all static assets, which uses a `try_files` to redirect all other requests to a `@proxy`, which then does mostly this: ``` rewrite /subdir/(.*) /$1 break; rewrite ^/subdir$ /subdir/ permanent; proxy_buffering off; # some proxy headers proxy_pass […]; ``` ## Screenshots ![grafik](https://user-images.githubusercontent.com/11966684/29281999-6dda2250-8121-11e7-916b-972504334207.png)

GiteaMirror added the type/question label 2025-11-02 03:43:26 -06:00

GiteaMirror closed this issue

2025-11-02 03:43:26 -06:00

GiteaMirror commented

2025-11-02 03:43:27 -06:00

@lunny commented on GitHub (Aug 16, 2017):

Gitea has supported subdir. Maybe you should change your config to enable it.

@lunny commented on GitHub (Aug 16, 2017): Gitea has supported subdir. Maybe you should change your config to enable it.

GiteaMirror commented

2025-11-02 03:43:27 -06:00

@rugk commented on GitHub (Aug 16, 2017):

It is configured in the ROOT_URL. That has worked since Gogs. Is there another option I should change/add?

@rugk commented on GitHub (Aug 16, 2017): It is configured in the `ROOT_URL`. That has worked since Gogs. Is there another option I should change/add?

GiteaMirror commented

2025-11-02 03:43:27 -06:00

@rugk commented on GitHub (Aug 29, 2017):

Any news?

I also see errors when trying to push repos to gitea:

$ git push
fatal: unable to access 'https://example.com/subdir/orga/repo.git/': The requested URL returned error: 502

@rugk commented on GitHub (Aug 29, 2017): Any news? I also see errors when trying to push repos to gitea: ```shell $ git push fatal: unable to access 'https://example.com/subdir/orga/repo.git/': The requested URL returned error: 502 ```

GiteaMirror commented

2025-11-02 03:43:27 -06:00

@rugk commented on GitHub (Sep 22, 2017):

This could be an nginx error, I'll look into this soon…

@rugk commented on GitHub (Sep 22, 2017): This could be an nginx error, I'll look into this soon…

GiteaMirror commented

2025-11-02 03:43:27 -06:00

@techknowlogick commented on GitHub (May 10, 2018):

Can this ticket be closed?

@techknowlogick commented on GitHub (May 10, 2018): Can this ticket be closed?

GiteaMirror referenced this issue

2025-11-02 11:52:15 -06:00