[Eduardo Madrazo]

Hi there,

I`m new to Otobo and also to this commuity. I’m testing Otobo on a development envoroment in order to put it on production as soon as posible. I managed to create, queues, user, customer, dynamic field, ACLs… but I’m strugling with a trouble.

Using the internal network everything works fine, but in order to give external service and enable users to open a ticket from the web I put my Otobo server behind a ningx proxy server. After googleing a reader the forum I get the main page correctly proxied, but I get a too many redirections error.

Here is my nginx proxy config:

location /otobo-web/ {
proxy_pass http://172.20.0.23/otobo-web/;
# proxy_pass http://172.20.0.23/;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
# WebSocket support
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
# Aumentar los timeouts para conexiones largas
proxy_read_timeout 3600s;
proxy_send_timeout 3600s;
# Buffering
proxy_buffering off;

}

location / {
proxy_pass http://172.20.0.23/otobo/index.pl;
# proxy_pass http://172.20.0.23/;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
# WebSocket support
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
# Aumentar los timeouts para conexiones largas
proxy_read_timeout 3600s;
proxy_send_timeout 3600s;
# Buffering
proxy_buffering off;
}

I am not able to find where the error is and also I don’t know if I`ve to change something in the Otobo configuration.

Could you help me?

Thanks in advance

[Arnold]

Hi Eduardo,

I strongly recommend to use the Rother OSS docker compose stack: https://doc.otobo.org/manual/installation/11.0/en/content/installation-docker.html

It also comes with a preconfigured nginx proxy.

I am sure that everybody who wants to help, needs the following information:

1. What errors do you get and where?
2. What are you trying to achieve specifically?

Best,
Arnold

[Eduardo Madrazo]

Hi there,

thanks Arnold for your answer. I’m going to try ti explain more detailed my problem and what I’m trying to achieve.

I’m on a development stage with a new ticketing system. I’m running Otobo on a dedicated server based on Debian 13. I’ve install and configured the server without any issue and everything is working correctly when I use Otobo from inside my corporate network (using the intenal dns name or ip). On my roadmap the next point is to give access to the server from the internet. To achive this goal I use my webserver, that is exposed to the internet, to act as proxy for the Otobo server, because I cant expose Otobo server to internet. I’ve  configured the proxy server as I post on a previous message.

Whenever I acces the server from the internet (both customer portal or agent portal) I get the main page, but when I insert user and password  I get an error message: „too many redirects“. I know that the problem is related to the proxy, but I have other apps proxied in the same way and they do work correctly. So the proxy config lacks something that is a must to redirecto correcty. At this point I am unaware of how the internally designed application is performing and what would do I need to put it working.

What I need is to know which parameters or which config do  I need to adjust on Otobo or in the proxy server to get Otobo working from internet. Also I would like to get ride of /Otobo/ part on the url.

Thanks in advance for your help

[Arnold]

Hi Eduardo,

these are not questions related to OTOBO but the nginx reverse proxy.

However, OTOBO knows it’s own FQDN. If you proxy OTOBO, you have to adjust the system configuration accordingly. Maybe, this will solve the error?

Best,
Arnold

[Mike Thumes]

Hi Eduardo,

not a nginx expert here, but looking at your nginx conf I noticed you set

proxy_set_header Host $host;

If I read the docs correctly, the $host variable would normally point to your nginx instance, not otobo running on your internal host.
That overrides ngninx’s default behaviour of setting the Host Header to the value of $proxy_host . Which probably is what you want.

Something that you can try is leaving out the line(s) setting the host header alltogether, as suggested here and here 
As Arnold has pointed out there is a docker based installation method avail for Otobo that comes with its own nginx and it is definitely known to be working. Looking up the ngix conf on my local docker install does not set Host header as well.

Since you are setting up your own nginx you might also want to look up the nginx docs here and there.

Hope this might help you?

kind regards,
-mike

[Eduardo Madrazo]

Than for your response!

You both were right. All the problem was related to Nginx configuration (wrong configuration parameters + configuration not applied after changing on the nginx admin panel). After adjusting them I get the site proxied correctly.

My site, now is accesible from internet network and correctly proxied to the internet.

Thanks again!

 

[Autor]

Beiträge