Connector Connection Issues

Can't Connect to the connector after installation

The connector is using a DNS (depending on the connector partner), with a default value of:

https://t1c.t1t.io

The given URL is registered with DNSSEC enabled, and resolves to a 'localhost' domain.

Although the connector can run in a different mode (http, localost, custom domain name, etc.), to solve the above issue, the following causes are probable:

• DNS Rebind is enforced from your router

• The domain name is not whitelisted in your internal network

• A local proxy is running and prevents the internal connector communication

• An antivirus is blocking the connector communication

Solve the DNS Rebind Issue

Modifying your hosts file enables you to override the domain name system (DNS) for a domain on a specific machine.

Modifying your hosts file causes your local machine to look directly at the Internet Protocol (IP) address that you specify.

Modifying the hosts file involves adding an entries to it. The entry contains the IP address to which you want the DNS to resolve and a version of the Internet address.

When the connector is not reacting, but the installation has succeded, a DNS Rebind policy can forbid the communication form a web application to the connector's domain name. The default domain name used is: https:t1c.t1t.io

There are 2 approaches to fix the issue:

• update the 'host' file of the device (needs admin rights)

• update the local router which enforces the DNS Rebind

Update the 'host' file on the device

[MAC OSX]

// open the host file (write enabled)
// use your own editor of choice
sudo nano /etc/hosts

The admin password will be asked in the command line. If you open the file with another editor, a pop-up will ask you for the administrator password.

The file will be shown (the example can be different from what is configured on your device)

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1             localhost

We need to add an additional line to this file:

// add this line
127.0.0.1       t1c.t1t.io

Save the file, and test if the connection is working:

[WINDOWS]

Open Notepad or an editor of choice and run as administrator the following file:

c:\Windows\System32\Drivers\etc\hosts

We need to add an additional line to this file:

// add this line
127.0.0.1       t1c.t1t.io

Select File > Save to save your changes and test using the following URL in your browser

Update the local router which enforces the DNS Rebind

Solve the domain name whitelisting

The issue happens typically when the device is owned by an administrator in a controlled environment. Any router or firewall, sitting in between the connector and the internet, must comply to whitelist the following domain names by default:

• t1c.t1t.io

• ds.t1t.io

The latter is a central distribution service, which provides user with installation packages or updates. No personal data ever leaves the local device without explicit user consent.

Solve the local proxy issue

A local proxy can redirect or capture communciation using a 'localhost' URL. Many proxy solutions exists, so to solve the issue please read the documentation of the specific proxy and configure it to allow or exclude the connector from the applied policies.

Solve the antivirus issue

An anti-virus has functionalities to protect you from malicious software components. When an anti-virus is present on your device, please allow the connector processes to be trusted.

More information on 'known' solution for anti-virus services can be found: Troubleshooting