Successfully installed sliver c2c tool but i cant connect its server about sliver HOT 9 OPEN

I rm -rf every sliver thing before running the install script again. 😢
Shouldn't the user be asked to clean everything up first? And do it automatically.

from sliver.

We ditched ECC in v1.5.40 afaik, make sure you're on the latest version with a clean $HOME/.sliver directory @n3rada.

from sliver.

$HOME/.sliver

yep!
that was magic

from sliver.

Seems like the server did not properly start. What does systemctl status sliver say?

from sliver.

Seems like the server did not properly start. What does systemctl status sliver say?

it is saying enabled still it is getting same error

from sliver.

-🖥️ Linux version 6.3.0-kali1-amd64 ([email protected]) (gcc-12 (Debian 12.3.0-4) 12.3.0, GNU ld (GNU Binutils for Debian) 2.40.50.20230611) #1 SMP PREEMPT_DYNAMIC Debian 6.3.7-1kali1 (2023-06-29)

I'm joining this thread to say that I have the same problem: sliver won't start.

• sudo systemctl status sliver

● sliver.service - Sliver
     Loaded: loaded (/etc/systemd/system/sliver.service; disabled; preset: disabled)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2023-08-31 11:44:57 CEST; 1s ago
    Process: 84338 ExecStart=/root/sliver-server daemon (code=exited, status=99)
   Main PID: 84338 (code=exited, status=99)
        CPU: 36ms

• sudo /root/sliver-server daemon

stacktrace from panic:
goroutine 1 [running]:
runtime/debug.Stack()
        runtime/debug/stack.go:24 +0x65
github.com/bishopfox/sliver/server/cli.glob..func5.1()
        github.com/bishopfox/sliver/server/cli/daemon.go:46 +0x72
panic({0x17d41e0, 0xc000422140})
        runtime/panic.go:884 +0x213
github.com/bishopfox/sliver/server/cryptography.ECCServerKeyPair()
        github.com/bishopfox/sliver/server/cryptography/cryptography.go:303 +0xe5
github.com/bishopfox/sliver/server/cli.glob..func5(0xa424fc0?, {0x1a244c9?, 0x0?, 0x0?})
        github.com/bishopfox/sliver/server/cli/daemon.go:54 +0x298
github.com/spf13/cobra.(*Command).execute(0xa424fc0, {0xa50b620, 0x0, 0x0})
        github.com/spf13/[email protected]/command.go:944 +0x847
github.com/spf13/cobra.(*Command).ExecuteC(0xa424ce0)
        github.com/spf13/[email protected]/command.go:1068 +0x3bd
github.com/spf13/cobra.(*Command).Execute(...)
        github.com/spf13/[email protected]/command.go:992
github.com/bishopfox/sliver/server/cli.Execute()
        github.com/bishopfox/sliver/server/cli/cli.go:145 +0x25
main.main()
        github.com/bishopfox/sliver/server/main.go:43 +0x17

That'll help you better I think. Given the nature of the panic, there may be an issue with a cryptography library or related package, no?

from sliver.

I rm -rf every sliver thing before running the install script again. 😢 Shouldn't the user be asked to clean everything up first? And do it automatically.

Yeah, I think that sliver installer from https://sliver.sh/install should ask user to remove .sliver folder from home directory of the user running the script. This issue blocked me from updating server with some stacktrace spewing after manually starting server in terminal. This problem appeared since 1.5.40 version, while all the lower were working without an issue. Removing .sliver directory caused issue to disappear.

from sliver.

@LongWayHomie That's probably a good idea, we should also add an option to auto-start on boot. I think some folks don't realize the server daemon by default doesn't start on boot.

from sliver.

@LongWayHomie That's probably a good idea, we should also add an option to auto-start on boot. I think some folks don't realize the server daemon by default doesn't start on boot.

Why not adding a systemctl enable sliver?

from sliver.