Putting port in URL with colon notation makes login get stuck/fail #355

New Issue

Closed

opened 2020-06-04 03:08:02 +00:00 by 6543 · 11 comments

6543 commented

2020-06-04 03:08:02 +00:00

Member

Created By: @overflyer

Description - describe the bug / feature / suggestion in brief :

Initial login gets stuck at "Login" button changing to gray "Processing" button presumably because I use the colon notation to specify port 3000 after my Gitea server's URL.

Expected behaviour - describe what should be the expected result :

GitNex version : 2.4.1

Gitea version : 1.12.0+dev-60-g3f0cb8b33 built with GNU Make 4.2.1, go1.14.1

Android version : 9

Screenshots - if any:

Attached

Logs - if any :

Created By: @overflyer #### Description - describe the bug / feature / suggestion in brief : Initial login gets stuck at "Login" button changing to gray "Processing" button presumably because I use the colon notation to specify port 3000 after my Gitea server's URL. #### Expected behaviour - describe what should be the expected result : Login to my Gitea instance is succcessful. #### GitNex version : 2.4.1 #### Gitea version : 1.12.0+dev-60-g3f0cb8b33 built with GNU Make 4.2.1, go1.14.1 #### Android version : 9 #### Screenshots - if any: Attached #### Logs - if any :

6543 added the

🐛 Bug

✨ Duplicate

labels 2020-06-04 03:08:02 +00:00

6543 closed this issue

2020-06-04 03:08:02 +00:00

6543 commented

2020-06-04 03:08:43 +00:00

Author

Member

Created By: @overflyer

To specify this further: I tried both with and without additional https:// in front of the URL.

Created By: @overflyer To specify this further: I tried both with and without additional https:// in front of the URL.

mmarif commented

2020-06-04 03:09:03 +00:00

Owner

Do you by any change using self signed certificate?

6543 commented

2020-06-04 03:09:23 +00:00

Author

Member

Do you use http on your inctance? @overflyer

6543 commented

2020-06-04 03:09:43 +00:00

Author

Member

Created By: @overflyer

No HTTPS with Letsencrypt certificates. (So they are fully signed)

Created By: @overflyer No HTTPS with Letsencrypt certificates. (So they are fully signed)

6543 commented

2020-06-04 03:10:03 +00:00

Author

Member

Ok I havent tested a valid-cert + custom port ...

opyale commented

2020-06-04 03:10:23 +00:00

Member

@overflyer

Are you able to check if this issue still persists when using the latest changes of Gitnex (since you are using version 2.4.1)? A fairly similar issue was fixed recently.

You can download a self-compiled APK here or compile it yourself.

@overflyer Are you able to check if this issue still persists when using the latest changes of Gitnex (since you are using version 2.4.1)? A fairly similar issue was fixed recently. You can download a self-compiled APK [here](https://we.tl/t-fiOedhgfex) or compile it yourself.

6543 commented

2020-06-04 03:10:44 +00:00

Author

Member

Created By: @overflyer

Holy shoot you guys are fast.

I chose HTTPS and put my URL in WITHOUT https://

<mygitea.instance.de>:3000

I entered the username and my password and clicked the Login button.

I had so trust an unkown certificate, confirm and boom I can see all my repos.

Thanks a lot guys!

Created By: @overflyer Holy shoot you guys are fast. I chose HTTPS and put my URL in WITHOUT https:// <mygitea.instance.de>:3000 I entered the username and my password and clicked the Login button. I had so trust an unkown certificate, confirm and boom I can see all my repos. Thanks a lot guys!

opyale commented

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

Member

@overflyer I'm glad that this worked out for you.

6543 commented

2020-06-04 03:11:24 +00:00

Author

Member

and @anonTree1417 thanks for helping :)

@overflyer I think it has to do with hostname missmatch since letsencrypt certs should be valid. the error my go away If you host your gitea instance on port 443

and @anonTree1417 thanks for helping :) @overflyer I think it has to do with hostname missmatch since letsencrypt certs should be valid. the error my go away If you host your gitea instance on port 443

6543 commented

2020-06-04 03:11:44 +00:00

Author

Member

Similar/Dublicate to #357

I'll close it for now. However If you need more help @overflyer you can get in touch with us on Discord.

GitNex: https://discord.gg/FbSS4rf
Gitea: https://discord.gg/Gitea

Similar/Dublicate to #357 I'll close it for now. However If you need more help @overflyer you can get in touch with us on Discord. * GitNex: https://discord.gg/FbSS4rf * Gitea: https://discord.gg/Gitea

opyale commented

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

Member

I think it has to do with hostname missmatch since letsencrypt certs should be valid. the error my go away If you host your gitea instance on port 443

No. Usally it takes some time after a certificate was signed to get recognized as valid.

> I think it has to do with hostname missmatch since letsencrypt certs should be valid. the error my go away If you host your gitea instance on port 443 No. Usally it takes some time after a certificate was signed to get recognized as valid.