simplex-chat / simplex-chat/simplexmq
DigitalOcean droplet server does not work
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 847
- Forks
- 111
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 9
Description
Summary
smp-server binary from the release page with BuildID cd99e16fec87f49fbfc352350b688e9f90f36e56 DOES work.
smp-server binary from the DigitalOcean droplet with BuildID 9dcbeeef5875acc615c486a4c55be8b125592628 DOES NOT work.
What i did
I used the simplex digital Ocean droplet and run it.
Then i downloaded the simplex-chat (client application) and tried to connect it to my new server (running on digital ocean).
unfortunately this did not work. I got the following error message:
me@mybox:~$ simplex-chat -s smp://tXC4IMc1KUOAEYfXwX+S9ACu2EEitBlSxqCObdKDBEU=@simplex.scusi.io
option -s: @: Failed reading: satisfyWith
How i found out
When i tried the same thing with one of the offical server, it works.
I downloaded the server binary from the release page and started it locally on my computer.
I connected to my local instance, did work, as seen below.
me@mybox:~/$ simplex-chat -s smp://h9ZEZW7uiweKkT6DtExxo5JI9mgyGjc1vSp8wBHaGaE=@127.0.0.1
SimpleX Chat v1.0.0
db: /home/me/.simplex/simplex_v1_chat.db, /home/me/.simplex/simplex_v1_agent.db
type "/help" or "/h" for usage info
[...]
Next thing i did was to check if the local server binary is the same as the one in the digital ocean droplet.
Turns out it is not.
root@simplex:~# file /opt/simplex/bin/smp-server
/opt/simplex/bin/smp-server: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=9dcbeeef5875acc615c486a4c55be8b125592628, stripped
The local server binary (downloaded from the release page) is different from the above.
me@mybox:~/Downloads$ file smp-server-ubuntu-20_04-x86-64
smp-server-ubuntu-20_04-x86-64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=cd99e16fec87f49fbfc352350b688e9f90f36e56, stripped
After finding out that the binaries from the release page and the droplet are different i just uploaded the release binary into my droplet and overwrote /opt/simplex/bin/smp-server.
After replacing the smp-server binary from the droplet with the one from the release page it also works for me with my digital ocean droplet. I think the digital ocean droplet needs some love and a binary to be updated.
P.S. Thank you for that software project, i like it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the release-page smp-server binary with /opt/simplex/bin/smp-server on the DigitalOcean droplet, using the BuildIDs and the reported simplex-chat connection behavior. Check how the droplet obtains and installs its binary; done means the deployed binary matches the intended release and the reported server connection succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell, linux
- Domain
- devops, infrastructure, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100