SMP server fails to get HTTPS credentials, XFTP fine
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, nixos
- Domain
- infrastructure
Research direction
Start by reproducing the shell script and inspect the SMP container's mounted /etc/opt/simplex/config directory alongside the expected /etc/opt/simplex/web.crt and web.key paths. Compare the SMP and XFTP certificate handling; done means the SMP server starts with HTTPS credentials while the XFTP server continues to work.
Written by the indexing model from the issue text.
Description
The script I'm running results in the XFTP server getting up and running, but the SMP server fails with the error: no HTTPS credentials: /etc/opt/simplex/web.crt, /etc/opt/simplex/web.key
OS: NixOS
$ openssl version
OpenSSL 3.0.14 4 Jun 2024 (Library: OpenSSL 3.0.14 4 Jun 2024)
smpdomain=smp.xyz.xy
xftpdomain=xftp.xyz.xy
smprun() {
sudo certbot certonly --standalone -d $smpdomain --key-type rsa --rsa-key-size 4096
docker run \
-e "ADDR=${smpdomain}" \
-p 5223:5223 \
-v $HOME/simplex/smp/config:/etc/opt/simplex:z \
-v $HOME/simplex/smp/logs:/var/opt/simplex:z \
simplexchat/smp-server:latest
}
xftprun(){
sudo certbot certonly --standalone -d $xftpdomain --key-type rsa --rsa-key-size 4096
docker run \
-e "ADDR=${xftpdomain}" \
-e "QUOTA=20gb" \
-p 444:444 \
-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
}
smprun &
xftprun
Any pointers?
- Dominant language
- Haskell
- Stars
- 850
- Forks
- 111
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from simplex-chat/simplexmq
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
simplex-chat/simplexmq#1853 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
simplex-chat/simplexmq#1781 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
simplex-chat/simplexmq#1864 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
simplex-chat/simplexmq#1857 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
simplex-chat/simplexmq#1855 ·
Maintainers usually reply within 2 days
All issues in simplex-chat/simplexmq
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
compiler-explorer/compiler-explorer#9213 ·
Maintainers usually reply within 1 day
-
language/en needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
kubernetes/website#57846 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100