| 22 Sep 2023 |
|  computersalat_19189 joined the room. | 19:44:23 |
 isboyjc#0 | You are right. I changed the internal port to 22, and container 2222 was mapped to the internal 22 port. Then, I listened to the domain name's 22 port and forwarded it to the container's 2222 port through nginx.but SSH clone prompted me to enter the password. After entering the password, it displayed Permission denied, please try again.
Why is this? Normally, linking SSH does not require entering a password, right
I seem to have taken a step closer | 20:57:23 |
| isboyjc#0 | 
Download code.png | 21:15:47 |
| 23 Sep 2023 |
|  Arya [aryak.me] joined the room. | 06:04:34 |
 prologic1071 | Hey team π Can we please consider adding an Admin UI option to auto-generate a GPG Signing key for the server and just make that a thing? I really don't want to get in there and do this by hand, and honestly don't feel like that's really necessary. | 06:15:28 |
|  @aryak:projectsegfau.lt left the room. | 07:34:22 |
|  Caesar joined the room. | 12:34:36 |
|  @0xmrtt:projectsegfau.lt removed their profile picture. | 12:39:23 |
| @0xmrtt:projectsegfau.lt removed their display name 0xMRTT. | 12:48:05 |
| @0xmrtt:projectsegfau.lt left the room. | 12:57:21 |
 ehuelsmann | In reply to @_discord_997379648621133935:t2bot.io
You are right. I changed the internal port to 22, and container 2222 was mapped to the internal 22 port. Then, I listened to the domain name's 22 port and forwarded it to the container's 2222 port through nginx.but SSH clone prompted me to enter the password. After entering the password, it displayed Permission denied, please try again.
Why is this? Normally, linking SSH does not require entering a password, right
I seem to have taken a step closer Maybe the SSH server does not find your public key? That's when it normally asks for a password, if it's configured to allow passwords at all. (Which you probably shouldn't...) | 13:39:51 |
| ehuelsmann | One solution would be to regenerate the "authorized_keys" file. I'm sure there's a command or screen in Gitea which allows you to do that (haven't needed that functionality myself yet, so can't tell you where it is). | 13:40:52 |
|  a1012112796 joined the room. | 17:41:04 |
| isboyjc#0 | yesοΌI have tried everything you said.
1.Key does not have a password
2.Authorized_ Keys have already attempted to update | 17:47:01 |
| isboyjc#0 | The current configuration is: SSH_ PROT configuration is 22, external port 2222 forwards container port 22, nginx listens to secondary domain name port 22 and forwards to container port 2222 | 17:51:50 |
|  generaltao725 joined the room. | 18:34:13 |
| ehuelsmann | Then I'm at a loss too. | 18:51:22 |
|  im_ninooo joined the room. | 23:06:36 |
| im_ninooo | hello! I don't see a general support channel. am I missing something? | 23:06:38 |
 techknowlogick | Feel free to ask in here or the #configuration channel π | 23:22:43 |
| im_ninooo | thank you!
I'm noticing a weird behavior with verifying GPG keys and I was wondering if that would be critical enough to send an email vs opening a githug issue. | 23:26:14 |
| im_ninooo | because of: NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue. | 23:26:45 |
| 24 Sep 2023 |
| techknowlogick | Probably better to err on the side of caution and send an email. Thanks for asking about it and checking π | 00:28:58 |
| im_ninooo | alright, thanks! | 00:29:22 |
| im_ninooo | sent π | 01:04:43 |
| im_ninooo | btw, I really appreciate the work you guys are doing. Gitea is an incredible project π₯ | 01:07:35 |
| techknowlogick | thanks so much!
I can confirm I got the email. I won't be able to respond tonight as I'm about to head to sleep, but you'll certainly get a response. | 01:16:40 |
| im_ninooo | please take your time π | 02:23:18 |
 jungby.exe | i got auth0 and after they sign up with a specific domain, they have to set an ID and their email, is there a way to use the ones provided by auth0? | 04:55:16 |
 lunny | please submit an issue | 05:39:15 |
