Odd binding problem

Get Help
1

Metabase 0.50.16
I'm launching a dev environment from a batch file in Windows.
I have

SET MB_JETTY_PORT=3000
SET MB_DB_HOST=192.168.3.157
SET MB_JETTY_SSL=false

plus all the other options you'd expect.
For some reason, it fails to launch as there's a conflict on port 443. I also have IIS running on 443. If I stop that, Metabase launches correctly AND it's using port 3000 as expected! I can then restart IIS and everything works correctly.

Any ideas what could be going on?

2

you can't have 2 apps running on the same port :frowning: Metabase and IIS can't be run together if they use the same port. Would you mind sending us a diagram of what you want to achieve so we can help?

3

They're not on the same port! Metabase is just running on 3000. That's what's so very odd.
If I start Metabase while IIS is off, I can then start IIS and they both work together.
It's as though Metabase is trying to bind to 443 during startup. Makes no sense to me.

I want Metabase on 3000
IIS on 443.
I'm not trying to do anything clever - this is a dev environment.