Port battle for 8090

Post any problems / bugs / issues that are Mylar-related in here.
Post Reply
jefftr66
Posts: 4
Joined: Sun Jan 13, 2019 8:38 pm

Port battle for 8090

Post by jefftr66 » Sun Jan 13, 2019 8:43 pm

Using sab...vpn and mylar in docker and they are battling over port 8090. I've tried multiple times to change the port in .env but after I run ds -c no matter which I change they always revert back to 8090. I even tried deleting 8090 from sab as 8080 works but it just added it back.

What is going on? Any help would be greatly appreciated.

Thanks

barbequesauce
Posts: 45
Joined: Fri Feb 03, 2017 3:59 pm

Re: Port battle for 8090

Post by barbequesauce » Mon Jan 14, 2019 12:42 am

Why not try changing Mylar’s port in config.ini? Make sure Mylar isn’t running when you edit it...

jefftr66
Posts: 4
Joined: Sun Jan 13, 2019 8:38 pm

Re: Port battle for 8090

Post by jefftr66 » Mon Jan 14, 2019 1:47 am

Yeah, I'm a total noob with linux - does that work if I'm running it in docker?

barbequesauce
Posts: 45
Joined: Fri Feb 03, 2017 3:59 pm

Re: Port battle for 8090

Post by barbequesauce » Mon Jan 14, 2019 2:00 am

I don’t see why not - you’re telling Mylar to run on a different port. There might be Docker overhead to connect or allocate the new port to Mylar, I can’t really say...

jefftr66
Posts: 4
Joined: Sun Jan 13, 2019 8:38 pm

Re: Port battle for 8090

Post by jefftr66 » Tue Jan 15, 2019 1:42 am

Yeah editing the .ini file for Mylar does not work - it just reverts back to 8090 like with .env edits

barbequesauce
Posts: 45
Joined: Fri Feb 03, 2017 3:59 pm

Re: Port battle for 8090

Post by barbequesauce » Tue Jan 15, 2019 1:52 am

Gonna have to defer to a docker expert then, it’s clear local config edits are getting overridden somehow.

Post Reply