-
Beiträge
-
-
Hello.
After installing Otobo on an Ubuntu server with Docker compose, we are able to navigate through the interface of the web application.
All seems work correctly and we are making first configurations and we find some troubles to set the correct FQDN and navigate to the web application througth it, we are making this because our porpuse is to set Otobo and many features will not work with only the IP.
In system configuration we search FQDN and found the setting for define it, we set for example „otobo.domain.local“,
and we aspect that digiting the URL with the domain name it should bring us to the local istance.
This is not working and becuase of that we are asking for help. What we are forgetting to setup?
Should the Otobo FQDN istance work directly after setup the OTOBO_CONFIG_FQDN variable?
-
Hi Duck duck,
the FQDN variable tells Otobo where it is served from, so that for example links are rendered with the correct domain part. Setting FQDN should work out of the box provided that DNS resolution for whatever you set FQDN to works correctly. Please check where otobo.domain.local (or whatever you set for FQDN) points to, and that it actually matches the IP where your Otobo instance is installed.
Use for example nslookup (or dig) command line tools to check DNS resolution. Try this on the Desktop Device from where you want to open Otobo in your browser:
https://en.wikipedia.org/wiki/Nslookup
https://en.wikipedia.org/wiki/Dig_(command)hope that helps!
kind regards,
-mike -
Hi Duck Duck,
in the DNS server we have set a host entry for the otobo server IP.
Example: otobo-ticket01 (ip= 192.168.2.22)
Then in the resolv. conf we have set the search domain. sudo nano /etc/resolv.conf
Example: mydomain.local
FQDN in Otobo is set to: otobo-ticket01.mydomain.local
Our real Ubuntu Server Hostname is different. You can check your setting with „nano /etc/hostname“
Greetings
Marcel
-
- Du musst angemeldet sein, um auf dieses Thema antworten zu können.