Gitea ; SSH not working correctly for some reason #29

Closed
opened 2023-12-17 15:26:43 -05:00 by sickprodigy · 2 comments
Owner

Here are some logs as backup

2023-12-17T20:07:25.541590460Z 2023/12/17 15:07:25 modules/ssh/ssh.go:285:sshConnectionFailed() [W] Failed authentication attempt from 172.20.0.19:59210

2023-12-17T20:08:46.344451886Z 2023/12/17 15:08:46 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for 172.70.174.130:0, 200 OK in 436201.8ms @ events/events.go:18(events.Events)

2023-12-17T20:08:57.055077533Z 2023/12/17 15:08:57 ...eb/routing/logger.go:102:func1() [I] router: completed GET /sickprodigy/docker-containers2 for 172.70.174.130:0, 200 OK in 8.2ms @ repo/view.go:718(repo.Home)

2023-12-17T20:08:57.143915933Z 2023/12/17 15:08:57 ...eb/routing/logger.go:102:func1() [I] router: completed GET /avatar/db1bafdced7e8e1c77ce64e32434a27f?size=48 for 172.70.174.130:0, 303 See Other in 17.3ms @ user/avatar.go:48(user.AvatarByEmailHash)

2023-12-17T20:09:00.020281474Z 2023/12/17 15:09:00 modules/ssh/ssh.go:283:sshConnectionFailed() [W] Failed connection from 172.20.0.19:53486 with error: ssh: overflow reading version string

2023-12-17T20:09:00.020300951Z 2023/12/17 15:09:00 modules/ssh/ssh.go:285:sshConnectionFailed() [W] Failed authentication attempt from 172.20.0.19:53486

2023-12-17T20:09:00.519401357Z 2023/12/17 15:09:00 ...eb/routing/logger.go:68:func1() [I] router: polling   GET /user/events for 172.70.174.130:0, elapsed 3294.2ms @ events/events.go:18(events.Events)

2023-12-17T20:09:01.507279922Z 2023/12/17 15:09:01 modules/ssh/ssh.go:283:sshConnectionFailed() [W] Failed connection from 172.20.0.19:43616 with error: ssh: overflow reading version string

2023-12-17T20:09:01.507295607Z 2023/12/17 15:09:01 modules/ssh/ssh.go:285:sshConnectionFailed() [W] Failed authentication attempt from 172.20.0.19:43616
Here are some logs as backup ``` 2023-12-17T20:07:25.541590460Z 2023/12/17 15:07:25 modules/ssh/ssh.go:285:sshConnectionFailed() [W] Failed authentication attempt from 172.20.0.19:59210 2023-12-17T20:08:46.344451886Z 2023/12/17 15:08:46 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for 172.70.174.130:0, 200 OK in 436201.8ms @ events/events.go:18(events.Events) 2023-12-17T20:08:57.055077533Z 2023/12/17 15:08:57 ...eb/routing/logger.go:102:func1() [I] router: completed GET /sickprodigy/docker-containers2 for 172.70.174.130:0, 200 OK in 8.2ms @ repo/view.go:718(repo.Home) 2023-12-17T20:08:57.143915933Z 2023/12/17 15:08:57 ...eb/routing/logger.go:102:func1() [I] router: completed GET /avatar/db1bafdced7e8e1c77ce64e32434a27f?size=48 for 172.70.174.130:0, 303 See Other in 17.3ms @ user/avatar.go:48(user.AvatarByEmailHash) 2023-12-17T20:09:00.020281474Z 2023/12/17 15:09:00 modules/ssh/ssh.go:283:sshConnectionFailed() [W] Failed connection from 172.20.0.19:53486 with error: ssh: overflow reading version string 2023-12-17T20:09:00.020300951Z 2023/12/17 15:09:00 modules/ssh/ssh.go:285:sshConnectionFailed() [W] Failed authentication attempt from 172.20.0.19:53486 2023-12-17T20:09:00.519401357Z 2023/12/17 15:09:00 ...eb/routing/logger.go:68:func1() [I] router: polling GET /user/events for 172.70.174.130:0, elapsed 3294.2ms @ events/events.go:18(events.Events) 2023-12-17T20:09:01.507279922Z 2023/12/17 15:09:01 modules/ssh/ssh.go:283:sshConnectionFailed() [W] Failed connection from 172.20.0.19:43616 with error: ssh: overflow reading version string 2023-12-17T20:09:01.507295607Z 2023/12/17 15:09:01 modules/ssh/ssh.go:285:sshConnectionFailed() [W] Failed authentication attempt from 172.20.0.19:43616 ```
sickprodigy self-assigned this 2023-12-19 11:40:08 -05:00
Author
Owner

I have stupid issues with gitea and vscode. On vscode eventually it will pop up saying enter password at the search bar/ command bar thing. Hard to notice sometimes. Be nice if it just stayed logged in.

I have stupid issues with gitea and vscode. On vscode eventually it will pop up saying enter password at the search bar/ command bar thing. Hard to notice sometimes. Be nice if it just stayed logged in.
Author
Owner

well probably because of cloudflare, because once I stopped using it, I've had like 0 issues.

well probably because of cloudflare, because once I stopped using it, I've had like 0 issues.
Sign in to join this conversation.
No description provided.