Hi Giordano,

reassigning only the ports should be easy as you are running OTOBO in Docker containers. The ports within the containers can stay as they are. Only the mappings to the ports that are visible on the Docker host must be adapted. The can be done with the variables OTOBO_WEB_HTTP_PORT and OTOBO_WEB_HTTPS_PORT in your .env file.

Another possibility is to  run OTOBO  only with HTTP on e.g. Port 81. Then you can do your SSL-termination on the the Apache running on the Docker host. In the Apache-config you can then set up a ProxyPass to OTOBO. An example, for a slightly different case, is in https://github.com/RotherOSS/otobo/blob/rel-10_1/scripts/apache2-httpd-plack-proxy.include.conf .

Best regards.

Bernhard

Hi Giordano,

changing the ports is documented in https://doc.otobo.org/manual/installation/10.1/en/content/installation-docker.html#choosing-non-standard-ports.  But that documentation is fairly concise. So, here is an example. In the file  otobo-docker/.env I have the following declarations:

# HTTP options
# In the HTTPS case http:// redirects to https://
# Set OTOBO_WEB_HTTP_PORT when the HTTP port is not 80
OTOBO_WEB_HTTP_PORT=81

# HTTPS options# set OTOBO_WEB_HTTPS_PORT when the HTTPS port is not 443
OTOBO_WEB_HTTPS_PORT=543

This changes the ports that are occupied on the Docker host:

$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
...
d9dce0e1a262 otobo-nginx-webproxy:local-10.1.x "/docker-entrypoint.…" 21 minutes ago Up 21 minutes (healthy) 80/tcp, 0.0.0.0:<strong>81</strong>->8080/tcp, 0.0.0.0:<strong>543</strong>->8443/tcp otobo_nginx_1

...

Therefore when fetching http://localhost:81/otobo/index.pl I get a redirect to HTTPS. When fetching https://localhost:543/otobo/index.pl  then OTOBO can be accessed.

When trying this in my local installation I noticed that the redirect to HTTPS still uses the default port 443. This will be fixed in one of the next releases, see https://github.com/RotherOSS/otobo/issues/1892.

Best regards,

Bernhard

Hi Giordano,

your changed .env file looks fine. But I see that the old ports 80 and 443 are still exposed on the Docker host. Did you restart the containers after the config change?

docker-compose down

docker-compose up -d

Best regards,

Bernhard

Hi Giodano,

the ports 8443 for NginX and 3306 for MaraDB are per default only used  internally in the OTOBO container network. They should not conflict with ports on the Docker hosts or with ports in other container networks. A conflict can only occur with the exposed ports that are reported by docker-compose ps.

However, during development, I often expose the MariaDB port so that I can use a GUI for inspecting the database. There I map port 3306 to 3307 so that it doesn’t conflict with a locally running database.

$git diff
diff --git a/docker-compose/otobo-base.yml b/docker-compose/otobo-base.yml
index 875df06..d634d99 100644
--- a/docker-compose/otobo-base.yml
+++ b/docker-compose/otobo-base.yml
@@ -29,8 +29,8 @@ services:
# like MySQL Workbench is used. Uncomment the following lines for making MariaDB available
# on port 3307 on the Docker host. A non-standard port is chosen here, because 3306 is
# often already used on the Docker host.
- # ports:
- # - "3307:3306"
+ ports:
+ - "3307:3306"

# Set the db root password which has to be entered when running otobo/installer.pl.
# The passwort is secret and can be stored in the file .env.