Hey there Hugo!
The most recent thread discussed this.
Someone provided these instructions which seemed to satisfy the person
Also, to note, I remember asking this same question a few years ago, and
it may be helpful to know that folks from OWS responded directly, and at
the time they were only making signal-server available for
development/transparency/auditability/etc purposes, rather than
furnishing it with the expectation that folks would run their own
The above instructions should hopefully be helpful enough for getting a
testing instance running, as you are seeking.
Their opinion was that the backend URI should be locked-in at the
application client level, because the security, stability, etc issues of
users being able to connect to other server instances than the official
OWS one were too great.
So, just so you know, you may have trouble getting the off-the-shelf
application clients to communicate with your test instance. Also, if you
are plannuing on using it behind a firewall, note that there is an open
ticket regarding communication over :443 - i think it uses :8443 because
of a self signed certificate or something as such?
Possibly there have been new developments with this stance on the OWS
end of things?
Post by Hugo Cosme
Hello, is it possible to create a private server for the signal? I
need to test a tool for internal communication of the company where I
work, and I liked the Signal proposal!