Docker Globaleaks v4.15.4 ignore --ip=0.0.0.0 cli parameter

[RrOoSsSsOo]

What version of GlobaLeaks are you using?

v4.15.4

What browser(s) are you seeing the problem on?

All

What operating system(s) are you seeing the problem on?

Linux

Describe the issue

When Globaleaks v4.15.4 is executed inside a Docker container is possible to access via web browser only if globaleaks.db > config > hostame is set to "" , not if it is https://my-public-domain.example.

The output of the command /usr/bin/python3 /usr/bin/globaleaks --working-path=/var/globaleaks/ -n inside the container at the first run shows

...
[stdout#info] GlobaLeaks is now running and accessible at the following urls:
[stdout#info] - [HTTPS]: https://0.0.0.0
...

because globaleaks.db > config > hostame = "" and you can access via browser at address https://my-local-ip:my-port/#/ . You can set platform details, create users, etc. in the normal way.

But when you set the hostmane to https://my-public-domain.example the next execution of the command /usr/bin/python3 /usr/bin/globaleaks --working-path=/var/globaleaks/ -n inside the container shows

...
[stdout#info] GlobaLeaks is now running and accessible at the following urls:
[stdout#info] - [HTTPS]: https://my-public-domain.example
...

and now you can't access via browser anymore.

Even setting the --ip=0.0.0.0 (solution that works on v4.12.7 inside a container with hostname set) you can't access. The command /usr/bin/python3 /usr/bin/globaleaks --ip=0.0.0.0 --working-path=/var/globaleaks/ -n inside the container continues to shows (only)

...
[stdout#info] GlobaLeaks is now running and accessible at the following urls:
[stdout#info] - [HTTPS]: https://my-public-domain.example
...

Tested in both Windows and Linux.

Proposed solution

Executing the command /usr/bin/python3 /usr/bin/globaleaks --working-path=/var/globaleaks/ -n is correct that it shows

...
[stdout#info] GlobaLeaks is now running and accessible at the following urls:
[stdout#info] - [HTTPS]: https://my-public-domain.example
...

But executing the command /usr/bin/python3 /usr/bin/globaleaks --ip=0.0.0.0 --working-path=/var/globaleaks/ -n should shows

...
[stdout#info] GlobaLeaks is now running and accessible at the following urls:
[stdout#info] - [HTTPS]: https://0.0.0.0
[stdout#info] - [HTTPS]: https://my-public-domain.example
...