gogs: Cannot start builtin SSH server
- Gogs version (or commit ref): 0.11.66
- Git version: 2.18.0
- Operating system: linux manjaro
- Database (use
[x]
):- PostgreSQL
- MySQL
- MSSQL
- SQLite
- Can you reproduce the bug at https://try.gogs.io:
- Yes (provide example URL)
- No
- Not relevant
- Log gist (usually found in
log/gogs.log
): 2018/09/23 16:20:54 [TRACE] Log Mode: File (Trace) 2018/09/23 16:20:54 [ INFO] Gogs 0.11.66.0916 2018/09/23 16:20:54 [ INFO] Cache Service Enabled 2018/09/23 16:20:54 [ INFO] Session Service Enabled 2018/09/23 16:20:54 [ INFO] Git Version: 2.18.0
Description
panic: SSH: Fail to parse private key
goroutine 1 [running]:
github.com/gogs/gogs/pkg/ssh.Listen(0xc000481661, 0x7, 0xbd4, 0xc000080360, 0x6, 0x6)
/home/wyx/go/src/github.com/gogs/gogs/pkg/ssh/ssh.go:182 +0x3a9
github.com/gogs/gogs/routes.GlobalInit()
/home/wyx/go/src/github.com/gogs/gogs/routes/install.go:93 +0x233
github.com/gogs/gogs/cmd.runWeb(0xc0003012c0, 0x0, 0xc0003012c0)
/home/wyx/go/src/github.com/gogs/gogs/cmd/web.go:171 +0x6b
github.com/gogs/gogs/vendor/github.com/urfave/cli.HandleAction(0xe51700, 0xfe8cf8, 0xc0003012c0, 0xc0000b2a00, 0x0)
/home/wyx/go/src/github.com/gogs/gogs/vendor/github.com/urfave/cli/app.go:483 +0xad
github.com/gogs/gogs/vendor/github.com/urfave/cli.Command.Run(0xf9886d, 0x3, 0x0, 0x0, 0x0, 0x0, 0x0, 0xfab313, 0x10, 0x0, ...)
/home/wyx/go/src/github.com/gogs/gogs/vendor/github.com/urfave/cli/command.go:193 +0x98e
github.com/gogs/gogs/vendor/github.com/urfave/cli.(*App).Run(0xc0003349c0, 0xc0000b6000, 0x2, 0x2, 0x0, 0x0)
/home/wyx/go/src/github.com/gogs/gogs/vendor/github.com/urfave/cli/app.go:250 +0x647
main.main()
/home/wyx/go/src/github.com/gogs/gogs/gogs.go:40 +0x273
my user:wyx
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 18 (8 by maintainers)
Commits related to this issue
- pkg/ssh: print actual error in panic (#5435) — committed to gogs/gogs by unknwon 6 years ago
- pkg/ssh: print actual error in panic (#5435) — committed to pkgr/gogs by unknwon 6 years ago
+1 This is happening for me on Fedora 28, but not two other servers running CentOS 7
I have also tried deleting the ssh keys. Same error after they regenerated. ssh-keygen verifies they seem valid.