Error when opening files

6543 commented

2020-06-04 06:58:30 +00:00

Member

Created By: @Anagastes

# What do you want to address?

Bug
Feature
Suggestion

# Describe your matter briefly

I have problems with Gitea 1.11 and 1.12-rc1 with Gitnex 2.5.1 opening data in the repository.

Get the message "The version is not supported, user Gitea 1.7 or higher" in the subfolder. But it is already in use at a higher level.

Unfortunately I have no log on Android. I only have the following log from Gitea itself.

Some additional details (Useful, when we are trying to reproduce a bug)

The version of Gitea you are using: 1.11 and 1.12-rc1
The version of GitNex you are using: 2.5.1
Phone OS version and model: Redmi Note 7 Pro "Violet" / Android 10
The type of certificate you are using (self-signed, signed): LetsEncrypt
How you used to log in (via password or token): Token-Login

We would appreciate some screenshots or stacktrace's, but this is also not required.

Screenshot attached ;)

Gites-Log

2020/05/30 03:16:04 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `id`, `owner_id`, `owner_name`, `lower_name`, `name`, `description`, `website`, `original_service_type`, `original_url`, `default_branch`, `num_watches`, `num_stars`, `num_forks`, `num_issues`, `num_closed_issues`, `num_pulls`, `num_closed_pulls`, `num_milestones`, `num_closed_milestones`, `is_private`, `is_empty`, `is_archived`, `is_mirror`, `status`, `is_fork`, `fork_id`, `is_template`, `template_id`, `size`, `is_fsck_enabled`, `close_issues_via_commit_in_any_branch`, `topics`, `avatar`, `created_unix`, `updated_unix` FROM `repository` WHERE `owner_id`=? AND `lower_name`=? LIMIT 1 [1 documentations] - 439.258µs 
2020/05/30 03:16:04 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `id`, `repo_id`, `user_id`, `mode` FROM `collaboration` WHERE `repo_id`=? AND `user_id`=? LIMIT 1 [34 1] - 257.233µs 
2020/05/30 03:16:04 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `id`, `repo_id`, `type`, `config`, `created_unix` FROM `repo_unit` WHERE (repo_id = ?) [34] - 502.416µs 
2020/05/30 03:16:04 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT count(*) FROM `release` WHERE repo_id=? AND is_draft=? [34 false] - 339.846µs 
2020/05/30 03:16:08 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT user_id, count(*) AS count FROM notification WHERE user_id IN (SELECT user_id FROM notification WHERE updated_unix >= ? AND updated_unix < ?) AND status = ? GROUP BY user_id [1590801356 1590801366 1] - 1.021752ms

Created By: @Anagastes ## # What do you want to address? - [X] Bug - [ ] Feature - [ ] Suggestion ## # Describe your matter briefly I have problems with Gitea 1.11 and 1.12-rc1 with Gitnex 2.5.1 opening data in the repository. Get the message "The version is not supported, user Gitea 1.7 or higher" in the subfolder. But it is already in use at a higher level. Unfortunately I have no log on Android. I only have the following log from Gitea itself. ##### Some additional details (Useful, when we are trying to reproduce a bug) * The version of **Gitea** you are using: **1.11 and 1.12-rc1** * The version of **GitNex** you are using: **2.5.1** * Phone **OS** version and model: **Redmi Note 7 Pro "Violet" / Android 10** * The type of certificate you are using (self-signed, signed): **LetsEncrypt** * How you used to log in (via password or token): **Token-Login** ##### We would appreciate some screenshots or stacktrace's, but this is also not required. Screenshot attached ;) #### Gites-Log ```sql 2020/05/30 03:16:04 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `id`, `owner_id`, `owner_name`, `lower_name`, `name`, `description`, `website`, `original_service_type`, `original_url`, `default_branch`, `num_watches`, `num_stars`, `num_forks`, `num_issues`, `num_closed_issues`, `num_pulls`, `num_closed_pulls`, `num_milestones`, `num_closed_milestones`, `is_private`, `is_empty`, `is_archived`, `is_mirror`, `status`, `is_fork`, `fork_id`, `is_template`, `template_id`, `size`, `is_fsck_enabled`, `close_issues_via_commit_in_any_branch`, `topics`, `avatar`, `created_unix`, `updated_unix` FROM `repository` WHERE `owner_id`=? AND `lower_name`=? LIMIT 1 [1 documentations] - 439.258µs 2020/05/30 03:16:04 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `id`, `repo_id`, `user_id`, `mode` FROM `collaboration` WHERE `repo_id`=? AND `user_id`=? LIMIT 1 [34 1] - 257.233µs 2020/05/30 03:16:04 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `id`, `repo_id`, `type`, `config`, `created_unix` FROM `repo_unit` WHERE (repo_id = ?) [34] - 502.416µs 2020/05/30 03:16:04 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT count(*) FROM `release` WHERE repo_id=? AND is_draft=? [34 false] - 339.846µs 2020/05/30 03:16:08 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT user_id, count(*) AS count FROM notification WHERE user_id IN (SELECT user_id FROM notification WHERE updated_unix >= ? AND updated_unix < ?) AND status = ? GROUP BY user_id [1590801356 1590801366 1] - 1.021752ms ```

6543 added the

❤️ Support

label 2020-06-04 06:58:30 +00:00

6543 closed this issue

2020-06-04 06:58:30 +00:00

mmarif commented

2020-06-04 06:59:11 +00:00

Owner

Can you tell us what version is showed in the app About screen?

Does this happen for all files?

Can you tell us what version is showed in the app About screen? Does this happen for all files?

opyale commented

2020-06-04 06:59:31 +00:00

Member

Does this bug occur for you when using the latest build of GitNex? You can get it here: https://cloud.swatian.com/s/Cq592xGEfnsGAAW

6543 commented

2020-06-04 06:59:51 +00:00

Author

Member

Created By: @Anagastes

Can you tell us what version is showed in the app About screen?

Does this happen for all files?

Version 1.12-rc1 is displayed in the app

Does this bug occur for you when using the latest build of GitNex? You can get it here: https://cloud.swatian.com/s/Cq592xGEfnsGAAW

I'm afraid not. Even with the app the error remains. I now have a LogCat attached. Maybe this will help.

Created By: @Anagastes > Can you tell us what version is showed in the app About screen? > > Does this happen for all files? Version 1.12-rc1 is displayed in the app > Does this bug occur for you when using the latest build of GitNex? You can get it here: https://cloud.swatian.com/s/Cq592xGEfnsGAAW I'm afraid not. Even with the app the error remains. I now have a LogCat attached. Maybe this will help.

opyale commented

2020-06-04 07:00:11 +00:00

Member

By the way, thank you for your efforts. We really appreciate that. I will have a look at your stack traces now.

mmarif commented

2020-06-04 07:00:31 +00:00

Owner

@Anagastes can you confirm,

Does this happen for all files?

Is this private instance?, if you don't mind can you create a test user and send the details to gitnex@swatian.com. It will help debug this further.

@Anagastes can you confirm, > Does this happen for all files? Is this private instance?, if you don't mind can you create a test user and send the details to gitnex@swatian.com. It will help debug this further.

6543 commented

2020-06-04 07:00:51 +00:00

Author

Member

Created By: @Anagastes

@mmarif

Is this private instance?, if you don't mind can you create a test user and send the details to gitnex@swatian.com. It will help debug this further.

It is only for data that is in subfolders. Data in the root directory I can open.

Test-User-Link ist send to this address. :)

It's in every repository. Mine are private. But you can just create a new one. That's where the error should occur.

Created By: @Anagastes @mmarif > Is this private instance?, if you don't mind can you create a test user and send the details to gitnex@swatian.com. It will help debug this further. It is only for data that is in subfolders. Data in the root directory I can open. Test-User-Link ist send to this address. :) It's in every repository. Mine are private. But you can just create a new one. That's where the error should occur.

mmarif commented

2020-06-04 07:01:11 +00:00

Owner

It’s in every repository. Mine are private. But you can just create a new one. That’s where the error should occur.

Thanks, I will soon test it out.

> It’s in every repository. Mine are private. But you can just create a new one. That’s where the error should occur. Thanks, I will soon test it out.

mmarif commented

2020-06-04 07:01:31 +00:00

Owner

While trying to access the site, I get this. Anything I am missing, adblock is disabled. It fails to load some js libraries.

6543 commented

2020-06-04 07:01:52 +00:00

Author

Member

Created By: @Anagastes

While trying to access the site, I get this. Anything I am missing, adblock is disabled. It fails to load some js libraries.

@mmarif

f****k Ive enabled http2 on reverse proxy. One moment please

Created By: @Anagastes > While trying to access the site, I get this. Anything I am missing, adblock is disabled. It fails to load some js libraries. @mmarif f****k Ive enabled http2 on reverse proxy. One moment please

6543 commented

2020-06-04 07:02:12 +00:00

Author

Member

Created By: @Anagastes

@mmarif

I'm sorry, please cleare cache and try again. This bug still alive.

Created By: @Anagastes @mmarif I'm sorry, please cleare cache and try again. This bug still alive.

mmarif commented

2020-06-04 07:02:32 +00:00

Owner

Ok.

In the mean time, if you are using Apache as reverse proxy. Can you add this AllowEncodedSlashes On in httpd.conf and try.

Ok. In the mean time, if you are using Apache as reverse proxy. Can you add this `AllowEncodedSlashes On` in httpd.conf and try.

6543 commented

2020-06-04 07:02:52 +00:00

Author

Member

Created By: @Anagastes

Ok.

In the mean time, if you are using Apache as reverse proxy. Can you add this AllowEncodedSlashes On in httpd.conf and try.

Ok. Ive changed from AllowEncodedSlashes NoDecode to AllowEncodedSlashes On now. And Its solved!

Created By: @Anagastes > Ok. > > In the mean time, if you are using Apache as reverse proxy. Can you add this `AllowEncodedSlashes On` in httpd.conf and try. > Ok. Ive changed from `AllowEncodedSlashes NoDecode` to `AllowEncodedSlashes On` now. And Its solved!

mmarif commented

2020-06-04 07:03:12 +00:00

Owner

Great. 👍

I also tested it, and it works with sub dirs and files.

I will close this issue now. And hope you can leave a nice review in play store. :)

Great. 👍 I also tested it, and it works with sub dirs and files. I will close this issue now. And hope you can leave a nice review in play store. :)

mmarif referenced this issue

2020-06-04 07:05:36 +00:00

"This Request needs a higher Gitea Version" or "Gitea version > 1.7 required" #519

6543 referenced this issue

2020-06-04 07:06:16 +00:00

"This Request needs a higher Gitea Version" or "Gitea version > 1.7 required" #519

sciunto commented

2022-12-31 11:26:21 +00:00

A short note just to say that this issue happened to me as well. Two symptoms:

impossible to view files in subfolders
impossible to create files in subfolders

although both possible in the root.

Same message saying that gitea was not up to date. I updated gitea, and gitnex was still saying that it was not up to date. Then, I found this issue.

Changing the apache configuration solved the problem.

I don't know whether a tip must be mentionned in gitea documentation or the error message in gitnex must be improved (perhaps both...), but I hope people will find this issue because gitnex is worth it!

Best

A short note just to say that this issue happened to me as well. Two symptoms: * impossible to view files in subfolders * impossible to create files in subfolders although both possible in the root. Same message saying that gitea was not up to date. I updated gitea, and gitnex was still saying that it was not up to date. Then, I found this issue. Changing the apache configuration solved the problem. I don't know whether a tip must be mentionned in gitea documentation or the error message in gitnex must be improved (perhaps both...), but I hope people will find this issue because gitnex is worth it! Best

mmarif commented

2022-12-31 13:18:07 +00:00

Owner

@sciunto most of the errors and messages you see are part of the API and some of these are very generic. So we provide as many details as possible. In this case, you can always check the server logs OR just open an issue if not created by someone earlier.

Regarding the tip, we recently went through with another user and updated our wiki troubleshoot guide linking to the exact location of the configuration on Gitea docs.

https://codeberg.org/gitnex/GitNex/wiki/Troubleshoot-Guide#i-cannot-browse-directories-inside-file-browser

#1176

Hope these were helpful.

@sciunto most of the errors and messages you see are part of the API and some of these are very generic. So we provide as many details as possible. In this case, you can always check the server logs OR just open an issue if not created by someone earlier. Regarding the tip, we recently went through with another user and updated our wiki troubleshoot guide linking to the exact location of the configuration on Gitea docs. https://codeberg.org/gitnex/GitNex/wiki/Troubleshoot-Guide#i-cannot-browse-directories-inside-file-browser https://codeberg.org/gitnex/GitNex/issues/1176 Hope these were helpful.

👍 1 ❤️ 1

sciunto commented

2022-12-31 13:19:07 +00:00

thanks!

Error when opening files #517

# What do you want to address?

# Describe your matter briefly

Some additional details (Useful, when we are trying to reproduce a bug)

We would appreciate some screenshots or stacktrace's, but this is also not required.

Gites-Log