#672 Can't login to private instance: "No Gitea detected"

Closed
opened 1 month ago by hasufell · 14 comments
hasufell commented 1 month ago

# What do you want to address?

# Describe your matter briefly

Cannot login to private Gitea instance via token.

  • created token
  • started app, chose token auth method, entered token and url
  • => leads to Error “No Gitea detected!” with no further information
  • gitea instance is running fine and can be accessed by other users
Some additional details

  • The version of Gitea you are using: cf4f2cf
  • The version of GitNex you are using: 3.1.1
  • Phone OS version and model: Galaxy S5e
  • The type of certificate you are using (self-signed, signed): let’sencrypt
  • How you used to log in (via password or token): token
## # What do you want to address? - [x] Bug - [ ] Feature - [ ] Suggestion ## # Describe your matter briefly Cannot login to private Gitea instance via token. - created token - started app, chose token auth method, entered token and url - => leads to Error "No Gitea detected!" with no further information - gitea instance is running fine and can be accessed by other users ##### Some additional details --- * The version of **Gitea** you are using: cf4f2cf * The version of **GitNex** you are using: 3.1.1 * Phone **OS** version and model: Galaxy S5e * The type of certificate you are using (self-signed, signed): let'sencrypt * How you used to log in (via password or token): token
6543 added the
Bug
label 1 month ago
6543 commented 1 month ago
Collaborator

for other devs/maintainer: gitea version is around v1.12.0-rc1

@hasufell I dont know if it is related but the current stable version is v1.12.3 ...

I would like to know what you mean by private instance, is it accessible authentificated only? or do you just rever to hosting a own public installation?

*for other devs/maintainer: gitea version is around v1.12.0-rc1* @hasufell I dont know if it is related but the current stable version is v1.12.3 ... I would like to know what you mean by **private instance**, is it accessible **authentificated** only? or do you just rever to hosting a own **public** installation?
6543 commented 1 month ago
Collaborator

@hasufell I think it has to do with how you have compiled/got gitea - it looks like it return a version GitNex do not understand (GitNex must be able to parse the version to enable/disable features/workarounds/...)

would be nice if you could tell me what you get when opening following url of your gitea:

https://you-gitea-domain.tld/api/v1/version

(for example codeberg: https://codeberg.org/api/v1/version)

@hasufell I think it has to do with how you have compiled/got gitea - it looks like it return a version GitNex do not understand (GitNex must be able to parse the version to enable/disable features/workarounds/...) would be nice if you could tell me what you get when opening following url of your gitea: `https://you-gitea-domain.tld/api/v1/version` (for example codeberg: https://codeberg.org/api/v1/version)
hasufell commented 1 month ago
Poster

@hasufell I dont know if it is related but the current stable version is v1.12.3 ...

I can’t upgrade because every other release is broken: https://github.com/go-gitea/gitea/issues/12267

I would like to know what you mean by private instance, is it accessible authentificated only? or do you just rever to hosting a own public installation?

It’s public.

would be nice if you could tell me what you get when opening following url of your gitea:

{"version":"cf4f2cf"}
> @hasufell I dont know if it is related but the current stable version is v1.12.3 ... I can't upgrade because every other release is broken: https://github.com/go-gitea/gitea/issues/12267 > I would like to know what you mean by private instance, is it accessible authentificated only? or do you just rever to hosting a own public installation? It's public. > would be nice if you could tell me what you get when opening following url of your gitea: ``` {"version":"cf4f2cf"} ```
6543 commented 1 month ago
Collaborator

@hasufell ok there it is - GitNex has no idear what version this should be (eaven I had to lookup things via git manualy)

I think we should add an option to manualy type in the version it it could not detect it ...

@hasufell ok there it is - GitNex has no idear what version this should be (eaven I had to lookup things via git manualy) I think we should add an option to manualy type in the version it it could not detect it ...
6543 removed the
Bug
label 1 month ago
hasufell commented 1 month ago
Poster

Is there a way I can fix this inside my gitea configuration?

Is there a way I can fix this inside my gitea configuration?
6543 commented 1 month ago
Collaborator

@hasufell I have created #673 for your usecase

at the moment you have three options:

  1. switch to a official gitea release
  2. compile in a understandable Version string (1.12.0 I would say) <- notifications feature wont work (>= 1.12.3)
  3. manualy change & compile GitNex to use v1.12.0 if it could not detect version
@hasufell I have created #673 for your usecase at the moment you have three options: 1. switch to a official gitea release 2. compile in a understandable Version string (`1.12.0` I would say) <- notifications feature wont work (>= 1.12.3) 3. manualy change & compile GitNex to use v1.12.0 if it could not detect version
hasufell commented 1 month ago
Poster

switch to a official gitea release

Well, I don’t know which one works. And I don’t really want to bisect.

compile in a understandable Version string (1.12.0 I would say) <- notifications feature wont work (>= 1.12.3)

how? What sets it?

> switch to a official gitea release Well, I don't know which one works. And I don't really want to bisect. > compile in a understandable Version string (1.12.0 I would say) <- notifications feature wont work (>= 1.12.3) how? What sets it?
6543 added the
Question
label 1 month ago
6543 commented 1 month ago
Collaborator

to manualy set Version string on compile:

  • the go compile option: -X "main.Version=1.12.0"
  • or export GITEA_VERSION="1.12.0" before make
to manualy set Version string on compile: * the go compile option: `-X "main.Version=1.12.0"` * or `export GITEA_VERSION="1.12.0"` before `make`
6543 commented 1 month ago
Collaborator

@hasufell

Well, I don’t know which one works. And I don’t really want to bisect.

the release/v1.12 branch should be the most stable and working one

@hasufell > Well, I don’t know which one works. And I don’t really want to bisect. the `release/v1.12` branch should be the most stable and working one
6543 commented 1 month ago
Collaborator

@hasufell tell me if it works :)

@hasufell tell me if it works :)
hasufell commented 1 month ago
Poster

the release/v1.12 branch should be the most stable and working one

Well, I don’t know if that one doesn’t suffer from: https://github.com/go-gitea/gitea/issues/12267

> the release/v1.12 branch should be the most stable and working one Well, I don't know if that one doesn't suffer from: https://github.com/go-gitea/gitea/issues/12267
6543 commented 1 month ago
Collaborator

I cant tell you either - do GitNex now work?

I cant tell you either - do GitNex now work?
hasufell commented 1 month ago
Poster

Yes, after setting the version during build, it works.

Yes, after setting the version during build, it works.
6543 closed this issue 1 month ago
6543 commented 1 month ago
Collaborator

@hasufell if you like you could subscribe #673 ;)

@hasufell if you like you could subscribe #673 ;)
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.