Resuming Older Issue #7994

New Issue

GiteaMirror · 2025-11-02T07:45:07-06:00

GiteaMirror commented

2025-11-02 07:45:07 -06:00

Originally created by @jeff-hykin on GitHub (Oct 19, 2021).

https://github.com/go-gitea/gitea/issues/16516#issuecomment-946862122

Note, locking the issue means random new issues like this one need to be made to continue the conversation. (Which is fine if that's the structure you guys want, just fyi it can be somewhat messy/discontinuous)

please don't post in closed issues. Your report will get lost. As this is not a bug I recommend hopping into our chat where someone can help you set your configuration.

@techknowlogick

Thanks for the chat recommendation, however the reason I post on a closed issue is because that it shows up on Google when searching based on the problem.

If I ask in chat, it's not going to help anyone else searching for the same problem.

Please do not half comment on old closed issues without providing full information. You should open another issue or likely just go to our discord and ask for help there as it would be quicker.

@zeripath

I intentionally posted only the info I believed was relevant as to not clutter the issue. I had a very similar setup, and simply wanted to check if I was correctly doing what had been recommended on that issue. I very much intended for it to be a continuation of the existing conversation by clarifying what had been said there. I did read the setup documentation, I did try different combinations of the app.ini, leaving out the local root url, or specifying it as localhost, etc. If I was going to do an information dump of my situation, yes I would have opened a new issue.

I realized I could self host GitLab though so I'm just going to do that instead.

Originally created by @jeff-hykin on GitHub (Oct 19, 2021). https://github.com/go-gitea/gitea/issues/16516#issuecomment-946862122 Note, locking the issue means random new issues like this one need to be made to continue the conversation. (Which is fine if that's the structure you guys want, just fyi it can be somewhat messy/discontinuous) > please don't post in closed issues. Your report will get lost. As this is not a bug I recommend hopping into our chat where someone can help you set your configuration. @techknowlogick Thanks for the chat recommendation, however the reason I post on a closed issue is because that it shows up on Google when searching based on the problem. If I ask in chat, it's not going to help anyone else searching for the same problem. > Please do not half comment on old closed issues without providing full information. You should open another issue or likely just go to our discord and ask for help there as it would be quicker. @zeripath I intentionally posted only the info I believed was relevant as to not clutter the issue. I had a very similar setup, and simply wanted to check if I was correctly doing what had been recommended on that issue. I very much intended for it to be a continuation of the existing conversation by clarifying what had been said there. I did read the setup documentation, I did try different combinations of the app.ini, leaving out the local root url, or specifying it as localhost, etc. If I was going to do an information dump of my situation, yes I would have opened a new issue. I realized I could self host GitLab though so I'm just going to do that instead.

GiteaMirror closed this issue

2025-11-02 07:45:08 -06:00

GiteaMirror commented

2025-11-02 07:45:13 -06:00

@jeff-hykin commented on GitHub (Oct 19, 2021):

(Closed because I just needed a thread to respond)

@jeff-hykin commented on GitHub (Oct 19, 2021): (Closed because I just needed a thread to respond)

GiteaMirror commented

2025-11-02 07:45:14 -06:00

@jolheiser commented on GitHub (Oct 19, 2021):

We do generally prefer new issues, as they show up at the top and can be triaged.

As Gitea has a multitude of configuration, generally more is better than less, and snippets of config are usually not enough to diagnose an issue.

If you have any further questions or decide GL isn't to your liking, feel free to stop by chat so we can triage your issue.

@jolheiser commented on GitHub (Oct 19, 2021): We do generally prefer new issues, as they show up at the top and can be triaged. As Gitea has a multitude of configuration, generally more is better than less, and snippets of config are usually not enough to diagnose an issue. If you have any further questions or decide GL isn't to your liking, feel free to stop by chat so we can triage your issue.

GiteaMirror commented

2025-11-02 07:45:16 -06:00

@zeripath commented on GitHub (Oct 19, 2021):

Dude seriously - it would have been fine to open another issue with a reference to the old issue, but give us all the information that we need to help you. That is all we ask.

Give us the logs, the information about your version and your set-up. You can say - I think this is similar to #16516.

What is your version?
How are you running gitea?
What do the logs show?
What makes you think this is similar to #16516 ?

This is basic information we need to help you.

Did you read my comment?

Why did you set your LOCAL_ROOT_URL the way you set it?

If I had to guess - and unfortunately that's all the information you've given us can allow me to do - it should be http://localhost:3000/

@zeripath commented on GitHub (Oct 19, 2021): Dude seriously - it would have been fine to open another issue with a reference to the old issue, but give us all the information that we need to help you. That is all we ask. Give us the logs, the information about your version and your set-up. You can say - I think this is similar to #16516. * What is your version? * How are you running gitea? * What do the logs show? * What makes you think this is similar to #16516 ? This is basic information we need to help you. Did you read my comment? * Why did you set your LOCAL_ROOT_URL the way you set it? If I had to guess - and unfortunately that's all the information you've given us can allow me to do - it should be http://localhost:3000/

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#7994