Non bare-metal setup with existing proxy and ports 80/443/9000 already taken

[arminus]

I'd like to test this, but I need to install it on a box where ports 80, 443 and 9000 are already used by something else. 80 and 443 by nginx proxy manager (I assume 80 and 443 are typically "already taken" on most servers...)

So, I've modified Caddyfile like so:

http://my.domain.com:85 {
	reverse_proxy filesync:80
}

http://my.domain.com:9900 {
	reverse_proxy peerjs:9000
}

and compose like so:

services:
  caddy:
    image: caddy
    container_name: filesync-caddy
    ports:
      - "85:80"
      - "9900:9000"
    volumes:
      - ./Caddyfile:/etc/caddy/Caddyfile:ro
      - filesync:/data
    restart: unless-stopped
...

But http://my.domain.com:85 times out, event though I see docker listening on :85 - what am I missing?

Eventually and for production I would need to put this behind an existing nginx proxymanager...

[arminus]

1 step further, compose needs to map like this:

    ports:
      - "85:85"
      - "9900:9900"

Then I can connect, but I get a "Lost connection to server." after a couple of seconds:

apparently, it tries to connect to

ws://my.domain.com:9000/peerjs?key=peerjs&id=svb-jlwt-zoz&token=bvcbe0xek57&version=1.5.5

probably because of

web/js/modules/webrtc/file.js
139:        port: 9000,

web/js/modules/webrtc/user.js
67:        port: 9000,

[arminus]

Yep, works when I change both to my 9900 in my own image in the js files. However, I think this should configurable (with an env var etc.)? Generally relying on ports being free is IMHO problematic.

[arminus]

nginx proxy manager with a share.my.domain.com -> http://my.domain.com doesn't work though. I can proxy filesync-app through npm but then again, it can't connect to peerjs, because it needs to be on the same (sub-)domain.

So in a nutshell: The current setup is IMHO not flexible enough to fit into a server which runs already other services and/or its own proxy (which is IMHO a quite common scenario).

[badmotorfinger]

How can I change the config so that web socket address requested in the web app is not port 9000, like 12345?

ws://filesync.lan:12345/peerjs?key=peerjs&id=ae000172-3f24-4ecf-bf7f-5fcef566f8d2&token=34wv90ntfv4&version=1.5.5

[polius]

Hi @arminus and @badmotorfinger ,

Thanks for your interest in this project.

I've just released version v3.2.0, which addresses your concerns. You no longer need to worry about handling Port 9000, as it is now managed internally and does not need to be exposed anymore.

This update includes changes to the docker-compose.yml and Caddyfile. Please make sure to grab the latest files from the deployment folder and redeploy FileSync.

@arminus, could you let me know if this release addresses your issue with deploying FileSync using Nginx Proxy Manager rather than Caddy? If you're still experiencing issues, please let me know, and I can share a docker-compose.yml file configured to work with NPM.

For reference, here is the Commit that introduces these changes.

[arminus]

Thanks for the quick update, either I miss something, or this is not yet fully working. Here's what I changed:
Caddyfile:

http://asterix.xxx.xxx:85 {
	reverse_proxy filesync:80
}

(I'm not running this on localhost).

docker-compose.yml:
Using your changes except

services:
  caddy:
    image: caddy
    container_name: filesync-caddy
    ports:
      - "85:85"
    volumes:
      - ./Caddyfile:/etc/caddy/Caddyfile:ro
      - filesync:/data
    restart: unless-stopped
    networks:
      - npm

Ports 80 and 443 are blocked by npm - using 85 to see if it's working w/o npm first - this is my usual work flow for new stuff.

But - it still tries to load peerjs via ws://asterix.xxx.xxx/peerjs/peerjs?key=peerjs&id=cyi-fmkc-nvq&token=levgsk17cj&version=1.5.5
(in this config, it should load peers on port 85 ?)

Once I define an npm proxy for http://filesync-app:80 I can however completely remove the caddy service from the compose file and all is fine.

So - IMHO 90% done because I think it should also work in "non localhost mode" with an http caddy? But my problem is solved, so thanks again!

[badmotorfinger]

This sort of works for me now. Port 9000 is no longer required which is fantastic, however, it only works on desktop web browsers.

If I scan the QR code on a mobile device and open my default web browser (Brave), then the mobile browser does not connect.

I am strictly on a LAN

[polius]

Thanks @arminus and @badmotorfinger for your continuous feedback.

I've updated the Caddyfile to enable FileSync over LAN. I tested it on my mobile using Brave, and it worked perfectly after scanning the QR code from my PC (http://192.168.1.10/...). @badmotorfinger, could you download the latest Caddyfile and test it again over LAN?

@arminus, as you noticed during your tests, if you are already using a proxy manager like NPM, the Caddy service is no longer required in the Docker Compose setup. In that case, you can connect to FileSync via http://filesync-app:80 (as you are currently doing). Caddy is included in this project primarily to simplify deployment, providing an easy reverse proxy setup and automatic SSL certificate management.

Commit: 707536b