Gitea: Internal Server Error #10480

@lunny commented on GitHub (Mar 22, 2023):

We needs more logs

@lunny commented on GitHub (Mar 22, 2023): We needs more logs

GiteaMirror commented

@hiifong commented on GitHub (Mar 23, 2023):

We needs more logs

Seems like there are no more error logs

@hiifong commented on GitHub (Mar 23, 2023): > We needs more logs Seems like there are no more error logs

GiteaMirror commented

@lunny commented on GitHub (Mar 23, 2023):

Or you can change RUN_MODE to dev and try ssh -T again.

@lunny commented on GitHub (Mar 23, 2023): Or you can change RUN_MODE to dev and try ssh -T again.

GiteaMirror commented

@hiifong commented on GitHub (Mar 23, 2023):

Or you can change RUN_MODE to dev and try ssh -T again.

not found any error log

@hiifong commented on GitHub (Mar 23, 2023): > Or you can change RUN_MODE to dev and try ssh -T again. ![image](https://user-images.githubusercontent.com/89133723/227084646-fbd732e0-23ea-466a-9ff1-6cd34dc4a978.png) not found any error log

GiteaMirror commented

@hiifong commented on GitHub (Mar 24, 2023):

I can't solve it by replacing the gitea binary file

@hiifong commented on GitHub (Mar 24, 2023): I can't solve it by replacing the gitea binary file

GiteaMirror commented

@wxiaoguang commented on GitHub (Mar 24, 2023):

Or you can change RUN_MODE to dev and try ssh -T again.

not found any error log: <html>...

You are accessing wrong port. The port you are accessing is a HTTPS server, not SSH server.

@wxiaoguang commented on GitHub (Mar 24, 2023): > > Or you can change RUN_MODE to dev and try ssh -T again. > > not found any error log: `<html>...` You are accessing wrong port. The port you are accessing is a HTTPS server, not SSH server.

GiteaMirror commented

@wxiaoguang commented on GitHub (Mar 24, 2023):

After I start a gitea instance with systemd, and then another gitea instance with the ./gitea web -p 3333 command, Ctrl+C

And I don't see why you should run two different Gitea instances at the same time with the same config.

@wxiaoguang commented on GitHub (Mar 24, 2023): > After I start a gitea instance with systemd, and then another gitea instance with the ./gitea web -p 3333 command, Ctrl+C And I don't see why you should run two different Gitea instances at the same time with the same config.

GiteaMirror commented

@hiifong commented on GitHub (Mar 24, 2023):

After I start a gitea instance with systemd, and then another gitea instance with the ./gitea web -p 3333 command, Ctrl+C

And I don't see why you should run two different Gitea instances at the same time with the same config.

it was purely a mistake

@hiifong commented on GitHub (Mar 24, 2023): > > After I start a gitea instance with systemd, and then another gitea instance with the ./gitea web -p 3333 command, Ctrl+C > > And I don't see why you should run two different Gitea instances at the same time with the same config. it was purely a mistake

GiteaMirror commented

@wxiaoguang commented on GitHub (Mar 24, 2023):

I can not understand your problem.

What's your problem?

Start Gitea by systemd, then start another manually, then stop the manually started one, then the systemd one doesn't work with SSH clone?
Why are you testing the SSH on a HTTPS port?

@wxiaoguang commented on GitHub (Mar 24, 2023): I can not understand your problem. What's your problem? * Start Gitea by systemd, then start another manually, then stop the manually started one, then the systemd one doesn't work with SSH clone? * Why are you testing the SSH on a HTTPS port?

GiteaMirror commented

@hiifong commented on GitHub (Mar 24, 2023):

I can not understand your problem.

What's your problem?

Start Gitea by systemd, then start another manually, then stop the manually started one, then the systemd one doesn't work with SSH clone?

Why are you testing the SSH on a HTTPS port?

step 1：use systemd run a gitea instance
step 2: ./gitea web -p 3333
step 3: Ctrl + C
step 4: can't push code to gitea and git clone

@hiifong commented on GitHub (Mar 24, 2023): > I can not understand your problem. > > What's your problem? > > * Start Gitea by systemd, then start another manually, then stop the manually started one, then the systemd one doesn't work with SSH clone? > * Why are you testing the SSH on a HTTPS port? step 1：use systemd run a gitea instance step 2: `./gitea web -p 3333` step 3: Ctrl + C step 4: can't push code to gitea and git clone

GiteaMirror commented

@wxiaoguang commented on GitHub (Mar 24, 2023):

Restart the systemd service will resolve the problem.

@wxiaoguang commented on GitHub (Mar 24, 2023): Restart the systemd service will resolve the problem.

GiteaMirror commented

@hiifong commented on GitHub (Mar 24, 2023):

Restart the systemd service will resolve the problem.

no

@hiifong commented on GitHub (Mar 24, 2023): > Restart the systemd service will resolve the problem. no

GiteaMirror commented

@hiifong commented on GitHub (Mar 24, 2023):

@hiifong commented on GitHub (Mar 24, 2023): ![image](https://user-images.githubusercontent.com/89133723/227431856-90666437-9c7a-4c58-a50a-5174b0c6bc35.png)

GiteaMirror commented

@hiifong commented on GitHub (Mar 24, 2023):

@hiifong commented on GitHub (Mar 24, 2023): ![image](https://user-images.githubusercontent.com/89133723/227432004-f70097c7-0452-4cf5-a879-b09039d37762.png)

GiteaMirror commented

@wxiaoguang commented on GitHub (Mar 24, 2023):

Try to:

Re-sync the git hook on the admin page
Enable Dev mode ,and try to : ssh git-user@your-server git-receive-pack your-org/your-repo.git to see what's the output. Do not use it on the HTTPS port.

Screenshot:

@wxiaoguang commented on GitHub (Mar 24, 2023): Try to: 1. Re-sync the git hook on the admin page 2. Enable Dev mode ,and try to : `ssh git-user@your-server git-receive-pack your-org/your-repo.git` to see what's the output. Do not use it on the HTTPS port. Screenshot: <details> ![image](https://user-images.githubusercontent.com/2114189/227432779-34166986-1571-416e-b821-ee15f8f39d5a.png) </details>

GiteaMirror commented

@hiifong commented on GitHub (Mar 24, 2023):

@hiifong commented on GitHub (Mar 24, 2023): > ![image](https://user-images.githubusercontent.com/89133723/227433484-c48ce23a-707e-45e6-9f6a-61f0953414ec.png)

GiteaMirror commented

@wxiaoguang commented on GitHub (Mar 24, 2023):

Isn't it clear enough .........

Your LOCAL_ROOT_URL is wrong.

Fix the port

@wxiaoguang commented on GitHub (Mar 24, 2023): Isn't it clear enough ......... Your LOCAL_ROOT_URL is wrong. Fix the port

GiteaMirror commented

@hiifong commented on GitHub (Mar 24, 2023):

Isn't it clear enough .........

Your LOCAL_ROOT_URL is wrong.

Fix the port

thank you，delete LOCAL_ROOT_URL can resolve the problem.

@hiifong commented on GitHub (Mar 24, 2023): > Isn't it clear enough ......... > > Your LOCAL_ROOT_URL is wrong. > > Fix the port thank you，delete `LOCAL_ROOT_URL` can resolve the problem.

GiteaMirror commented

@hiifong commented on GitHub (Mar 24, 2023):

I'm sure I don't have LOCAL_ROOT_URL configured

@hiifong commented on GitHub (Mar 24, 2023): I'm sure I don't have `LOCAL_ROOT_URL` configured

GiteaMirror commented

@wxiaoguang commented on GitHub (Mar 24, 2023):

If there is an issue, please describe all the details clearly and provide enough clues. And it's always better to share console texts than images.

@wxiaoguang commented on GitHub (Mar 24, 2023): If there is an issue, please describe all the details clearly and provide enough clues. And it's always better to share console texts than images.

GiteaMirror commented

@hiifong commented on GitHub (Mar 24, 2023):

If there is an issue, please describe all the details clearly and provide enough clues. And it's always better to share console texts than images.

get it

@hiifong commented on GitHub (Mar 24, 2023): > If there is an issue, please describe all the details clearly and provide enough clues. And it's always better to share console texts than images. get it

GiteaMirror commented