Now if I click on supporto.XXXXXX.it, the customer user is automatically redirected on agent page. I’d like automatically redirect the customer on customer page (otobo/customer.pl).
I have tryed to change FQDN in otobo system but doesn’t works fine.
we are thinking about making this easier, especially as AFAIK this was a simple SysConfig setting in OTRS 6. Fpr now we recomment a bit more convoluded way. The default page can indeed be set in the nginx configuration. Doing this in the running works, but your changes would be lost after a restart of the container. Therefore the config should be changed in a volume, which will persist when the container is stopped and started again.
from the screenshots I gather that you have created a volume and that you have adapted the custom config file. Did you also adapt the file .env ? If yes, you can check your Nginx container.
bes:~/devel/OTOBO/otobo-docker (rel-10_0)$ docker exec -it otobo_nginx_1 bash
root@e1ce50e91562:/etc/nginx# more /etc/nginx/config/template-custom/otobo_nginx.conf.template
more: stat of /etc/nginx/config/template-custom/otobo_nginx.conf.template failed: No such file or directory
root@e1ce50e91562:/etc/nginx# exit
exit
bes:~/devel/OTOBO/otobo-docker (rel-10_0)$
In my installation I don’t have a custom config installed. But you should see your adapted config. If the custom config looks fine and the redirect still does not work you can try first to restart the container.
After setting up the volume, the adapted configuration must be activated. The new volume is set up in docker-compose/otobo-nginx-custom-config.yml. Therefore this file must be added to COMPOSE_FILE. Then Nginx must be directed to use the new config. This is done by setting NGINX_ENVSUBST_TEMPLATE_DIR in the environment. In order to achieve this, uncomment or add the following lines in your .env file:
one thing I noticed in your config is that the redirect is set up for a prefix match on ‚/‘. It propably should be an exact match as set up by location = / { ... }.
Also I’m not sure how the problem manifests itself. Is nginx not starting up? Or is only the redirect not working? Are there error messages in the nginx log. The log can be inspected with docker-compose logs nginx.
Ah, this time you need to run the command on the Docker host, not in the Docker image. Specifically you must run docker-compose logs nginx in the directory otobo-docker. as that command needs the information from the file .env.
OK, we are getting closer. The service nginx is not running. This means that access via https://localhost/otobo/index.pl should not work. I just saw that in your first mail you mention http://www.supporto.XXXXX.it. But because you mentioned nginx I just assumed that you are running with SSL support.
The first question is whether you need, or want, SSL support. Both scenarios are supported.
SSL support is wanted: your .env file seems to be strange. Could you run diff .env .docker_compose_env_https and mask out the sensitive parts?
SSL support is not wanted: nginx is not needed at all. Replace ‚otobo/index.pl‘ with ‚otobo/customer.pl‘ around line 445 in the file /opt/otobo/bin/psgi-bin/otobo.psgi which is available in the container web. As a sanitiy check you can also do a diff .env .docker_compose_env_http
this clarifies things. As you are not using SSL in your test installation, you are also not using nginx there. Subsequently, any changes to the nginx config won’t have any effect.
It makes perfect sense to test config changes first in the test system. This can be achieved by using nginx in the test system as well. This can be achieved by basing the .env in your test system on .docker_compose_env_https and to activate a custom nginx config. You can choose whether you want to add certificates to your test installation. The alternative would be to change the listen directives in otobo_nginx.conf.template in order to support only HTTP.
Our website uses cookies. Cookies are tiny text files which are saved in your web browser or by your web browser on your device when you access websites. They contain a characteristic character sequence allowing to clearly identify your browser upon your next visit to the website.
You can prevent the setting of cookies at any time by making the appropriate setting in your internet browser. Cookies that have already been set can be deleted manually or automatically at any time. This is possible in all common internet browsers. If the setting of cookies is deactivated in the browser, not all functions of the website may be fully usable.
We deliberately use very little cookies.
Detailed information can be found in section 4 of our Privacy Policy.
Necessary cookies
Essential Cookies are necessary to deliver this website and some of its features correctly.
For this reason, we do not provide any opportunity here to disable them.
Notwithstanding this, you can deactivate all Cookies in your Browser Settings at any time. Please be aware, however, that this might have an impact on the functionality of this website.
More information about the cookies to be set and how long they will be stored can be found in section 4 of our Privacy Poliy: Privacy Policy.
Google Analytics' Cookies
When you visit this website, Google Analytics sets cookies on your system. This will help us analyse how you use our website ans tailor it to the needs of our visitors. Your IP address will be automatically anonymised (IP anonymisation and deactivation of your User ID). Therefore, we cannot trace which data a certain user is accessing. The data are not saved together with any other personal user data.
You can deactivate tracking in your browser if you do not want us to be able to track your visit on our website.
Privacy Policy
Detailed information on the usage of cookies as well as our Privacy Policy can be found here: