Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WEBUI_PORT not sticking within iptables #6

Open
Tr4il opened this issue Jan 11, 2019 · 0 comments · May be fixed by #9
Open

WEBUI_PORT not sticking within iptables #6

Tr4il opened this issue Jan 11, 2019 · 0 comments · May be fixed by #9

Comments

@Tr4il
Copy link

Tr4il commented Jan 11, 2019

Hi!

Changing the WEBUI_PORT_ENV variable for the docker container doesn't change the port from 8080 to the set port. I believe this is because the docker container variable is set as WEBUI_PORT _ENV within the docker container's /etc/environment, but the iptables script uses ${WEBUI_PORT}, without the _ENV added. This makes it impossible to access the webui from the set port when the VPN connection is enabled. After I building this on my own and changing the hardcoded port 8080 to the port of my choice (that matched with the port mapping on my docker-compose) it works fine!

thanks for the container though, its awesome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant