Experience Builder (Developer Edition) Deployment and startup of shared remote instance

Question

Hello dear ESRI Community,

I have a question regarding Experience Builder (Developer Edition) deployment. It is clear how to make it up and running on local PC by URL like  https://localhost:3001/,   but how to make it work from remote PC by url like https://my.domain.com:3001/  and make it available to the team of developers?  For instance, WAB goes with startup.bat file with pointing of ports and URLs (I have one instance of WAB working this way) and it just starts up and connects all necessary components and it is available remotely by URL (https://my.domain.com:portnumber). When I startup Experience Builder it runs locally by https://my.domain.com:3001 but not from remote PC in the same network. Is there any examples for Experience Builder running on dedicated server and accessible remotely? I was thinking about URL Rewrite module in IIS, but I'm pretty sure you guys could propose more elegant solution.

Thank you in advance!

Leonidas · Answer

Hello, I was curious to see if you came up with a solution for this.  I am in a similar situation where I would like to have ExB accessible to other computers on our network.  I tried adding an Inbound Firewall Rule but that did now work.    Runs fine on the server but will not run using IPaddress:3001.  If I only use the IP address from another computer, I get the ISS Welcome screen.

Thanks

RamaniGanason · Answer

Yes, that correct. The limitation will be on the machine that running and the network. Nothing on the application side of things.

Sergio · Answer

Hi,

Thanks for you input.

You mean that there are no intearnal reasons for started npm and Experience Builder to be accessed from remote PC rather than network limitations?

Thanks!