Hosting using an existing proxy manager

[dalekcoffee]

Hello!

Bit of a newbish question here

I have succesfully deployed the application as-is, but found that it is only accessible on port 80 on localhost, and I cannot access it on other machines on my network.

I saw another post where it was mentioned that a old release enabled the use of "DEV_WEBSERVER_PORT" but I don't quite see this in documentation or in the docker compose prebuilts for CPU

Can someone advise as to how I can go about deploying this on docker with a custom port, say, 7483 (idk random) so that I can then use my existing ngix proxy manager on a diferent host and properly map http/https traffic to this tool?

Many thanks ahead!

[JeffreyCA]

Hi, can you try setting NGINX_PORT to the desired port in your .env file?

[dalekcoffee]

I created a .env file and added NGINX_PORT=456 (just gonna go with that)

Placed it within the spleeter web folder

Do I then need to run

docker-compose -f docker-compose.yml -f docker-compose.prod.yml -f docker-compose.prod.selfhost.yml up as-is or do I need to add it to the command?

Im not familiar with using an ENV file I apologize. Doing some research but the format looks odd

Do I run this:

docker-compose -f docker-compose.yml -f docker-compose.prod.yml -f docker-compose.prod.selfhost.yml --env-file .env up

[JeffreyCA]

Yeah just run it as is, no need to explicitly specify the .env file in the command

[dalekcoffee]

So this works locally

But when accessing from another host on LAN it seems to still fail

When I setup my proxy manager to this host and port, it is accessible from WAN with domain, but once again I get an HTTP 400 response

[dalekcoffee]

I also disabled firewall on the host machine out of curiosity, and here's a ping to that host with docker desktop where it shows I can see the host.

Was there some other variable needed?

And to fix, do I just need to delete all containers, volumes, images, and redeploy with appended variable?

[JeffreyCA]

Oh, so in your .env you'll need to also set APP_HOST to the host (or hosts, separated by commas) that you want the app to be accessible from, like:

APP_HOST=192.168.1.3

No need to include localhost itself. And no need to delete anything, just restart the containers afterwards

[dalekcoffee]

Ah ok, do I need to also specify my domain somewhere so it will accept the WAN connections through my ngix proxy manager or is that not necessary?

[dalekcoffee]

The above did work for accessing from another host!

That said, I registered with ngix proxy manager using my domain and on WAN it still has an error claiming: Bad Request (400)

[dalekcoffee]

According to this it states domains or IPs, separated by commas, I did try that and re-deployed.

No luck unfortunately, still bad request when accessed by domain

My env file contains:
NGINX_PORT=456
APP_HOST=192.168.1.3, subdomain.domain.com

(Domain sanitized for privacy)

[dalekcoffee]

Self resolved! I assumed I needed a space after the comma on APP_HOST, removed same

It is now working thank you again!

[JeffreyCA]

Glad it worked!

[dalekcoffee]

Resolved!