simplex-chat / simplex-chat/simplexmq
xftp-server: no key port in section TRANSPORT
Open
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 847
- Forks
- 111
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 9
Description
Testing out simplex server via docker on debian 12:
docker run -d \
-e "ADDR=simplex.zaggy.nl:443" \
-e "QUOTA=10G" \
-p 443:443 \
-v $HOME/simplex/xftp/config:/etc/opt/simplex-xftp:z \
-v $HOME/simplex/xftp/logs:/var/opt/simplex-xftp:z \
-v $HOME/simplex/xftp/files:/srv/xftp:z \
simplexchat/xftp-server:latest
xftp-server doesn’t start?
sudo docker logs -f 0a39a2593aad
SimpleX XFTP server v1.0.1
Fingerprint: sO2YvijAQzsf6apAg1vdlqjHLES1PVp5Nu-OYL6dQ_8=
xftp-server: no key port in section TRANSPORT
CallStack (from HasCallStack):
error, called at src/Simplex/Messaging/Server/CLI.hs:161:14 in simplexmq-5.3.0.1-inplace:Simplex.Messaging.Server.CLI
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 with src/Simplex/Messaging/Server/CLI.hs around line 161 and the mounted xftp configuration used by the Docker command. Reproduce the startup failure from the reported logs and inspect how the TRANSPORT section is read; done means the container starts without the “no key port” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, haskell
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100