v1.20.0 does not start as a windows service #11254

Closed
opened 2025-11-02 09:32:24 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @achikhv on GitHub (Jul 17, 2023).

Description

After upgrade from v1.19.4 to v1.20.0 gitea can not start as a windows service. It gives 1053 (Service didn’t respond in a timely fashion) almost immediately after start attempt. No records are written to log to help debug this issue. Service starts successfully after downgrading back to v1.19.4.

Gitea Version

1.20.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Windows Server 2019

How are you running Gitea?

Self hosted as a windows service.

Database

None

Originally created by @achikhv on GitHub (Jul 17, 2023). ### Description After upgrade from v1.19.4 to v1.20.0 gitea can not start as a windows service. It gives 1053 (Service didn’t respond in a timely fashion) almost immediately after start attempt. No records are written to log to help debug this issue. Service starts successfully after downgrading back to v1.19.4. ### Gitea Version 1.20.0 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Windows Server 2019 ### How are you running Gitea? Self hosted as a windows service. ### Database None
GiteaMirror added the type/bug label 2025-11-02 09:32:24 -06:00
Author
Owner

@lunny commented on GitHub (Jul 18, 2023):

Please take a look at the error log. It's possbile your Gitea instance has some deprecated app.ini configurations.

@lunny commented on GitHub (Jul 18, 2023): Please take a look at the error log. It's possbile your Gitea instance has some deprecated app.ini configurations.
Author
Owner

@achikhv commented on GitHub (Jul 18, 2023):

@lunny, thanks for hinting. As I said gitea did not create any log files. So I started is manually and fixed removed fallbacks found in console. After that service has started successfuly.

@achikhv commented on GitHub (Jul 18, 2023): @lunny, thanks for hinting. As I said gitea did not create any log files. So I started is manually and fixed removed fallbacks found in console. After that service has started successfuly.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#11254