simplexmq icon indicating copy to clipboard operation
simplexmq copied to clipboard

SMP or XFTP server address avoiding it ends with the port number

Open nicfab opened this issue 2 years ago • 10 comments

I had to set up SMP and XFTP servers on a different port instead of the default ones because the default (especially 443 is already taken by another service). Thus, the server (SMP or XFTP) address finishes with @domain:portnumber. Is there any way to avoid the server address finishing as mentioned below, with @domain:portnumber? I mean, modifying some parameters somewhere.

nicfab avatar Jun 04 '23 18:06 nicfab

I would also love to see the ability to change ports. 443 is very commonly reverse proxies for many.

Death-Pact avatar Jun 24 '23 16:06 Death-Pact

Hello, It would be really interesting to be able to specify a port other than 443 for the xftp protocol. Thanks in advance!

Frereneo avatar Jun 28 '23 13:06 Frereneo

If you are using docker compose, just specify:

version: "3"
services:
  simplexchat-xftp:
    ...
    ports:
      - "5233:443"
    ...

and add this portnumber=5233 @domain:5233

webstudiobond avatar Jul 14 '23 07:07 webstudiobond

If you are using docker compose, just specify:

version: "3"
services:
  simplexchat-xftp:
    ...
    ports:
      - "5233:443"
    ...

and add this portnumber=5233 @Domain:5233

Can you please clarify what is this portnumber=5233 and where it should be added?

EsEnZeT avatar Oct 05 '23 15:10 EsEnZeT

This is if port 443 is already occupied on the server, you can specify any other one for xftp in the docker compose. Added to yaml and then to the app for xftp

webstudiobond avatar Oct 05 '23 15:10 webstudiobond

Ah understood, I thought it was something additional (except docker-compose + entry in app).

Unfortunately doesn't look like app accepts currently xftp with custom port (looks like it's ignored)

EsEnZeT avatar Oct 05 '23 15:10 EsEnZeT

I have added a port and it works

webstudiobond avatar Oct 05 '23 15:10 webstudiobond

I have added a port and it works

You are right looks like it works, but the android app is just showing red X sign it doesn't somehow

EsEnZeT avatar Oct 05 '23 17:10 EsEnZeT

For me both the Desktop GUI client as well as the Android client still act up if I try to add a xftp server on a non-standard port. To reproduce just copy the xftp:// string from a preset server (xftp2.simplex.im) and add a port descriptor so it looks like: xftp://[email protected]:443,jk6jybnel5hin2am5omd7g3hyvb4tfkyl7ea4vx5ldi7gpvz5ogqtcqd.onion

port 443 is the default port for xftp so it should be reachable at that port even though specifying a port in this case is redundant of course. When I add the:443 part the "Test Server" button immediately gets greyed out and I cannot establish a connection to the server even though it is reachable at the same port when the :443 is omitted. Same for my own xftp server that I host at a non-standard port: I cannot enter the connection details because the client considers them invalid.

systemling32 avatar Dec 13 '23 16:12 systemling32

@systemling32 Try putting the port after the onion address. See https://github.com/simplex-chat/simplexmq/issues/849#issuecomment-1773997094

vecna13 avatar Jan 25 '24 03:01 vecna13