Problems with SMP Server and Reverse Proxy

Open
#1,399 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, nginx
Domain
devops, infrastructure, networking

Research direction

Start by inspecting the SMP Docker container's handling of certificate files under /etc/opt/simplex/ and how the status page is enabled. Then review the Port 5223 reverse-proxy setup in nginx and the use of self-generated certificates. Done means the container behavior and supported proxy configuration are documented or adjusted for deployments without status-page certificates.

Written by the indexing model from the issue text.

Description

Not necessarily an issue, but at least uncertainties regarding setup.

The SMP Docker Container does crash when there's no SSL certificate files in /etc/opt/simplex/.
But if i got that right, this will only be used for Status page, so it would be better not to require these files to be present, so people can point their reverse proxy to it, or disable the status page if not needed.

As for Port 5223, the only way is to open a TCP forwarding stream on that Port in nginx, correct? Is that considered save, only using the self generated certs?

Dominant language
Haskell
Stars
847
Forks
111
Avg merge
3d 11h
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from simplex-chat/simplexmq

All issues in simplex-chat/simplexmq

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.