Selfhosting filepizza?

[B4T3S]

I'm trying to run my own instance of filepizza, the problem is that transferring files, even in the same network does not seem to work.

I'm assuming that I'm lacking some ENV variables that just aren't documented. The only ones I managed to figure out by snooping around the code were

      - COTURN_ENABLED=true
      - TURN_REALM=<my URL>

which at least stopped RTC errors from popping up in the connections tab, but sending files still doesn't seem to do anything past the "connected" state...

Is there an example .env somewhere that I can use to deploy the service?

[azzaka]

following

[msalmasi]

Same issue here. The connections show up but the download never starts. Been trying to find a fix but not getting anywhere.

[iamdoubz]

Try adding TURN_HOST as well.

[ljrobins]

Does anyone have a working local docker-compose.yml? I am also failing to get it to run locally.

[fabawi]

@B4T3S the issue could be that by default, filepizza is hosted on localhost but you are accessing the link through your local IP. You need to allow origins from which the filepizza server is invoked. You can specify that by uncommenting the API_ORIGINS env variable in the docker compose file and specifying your local ip in that list. You can also try '*' which will accept any origin, although that is not recommended.

This feature is implemented on this fork:

https://github.com/TeXlyre/filepizza