v3.8.x

Connector Connection Issues

This page summarized 'know' solution for connector connection troubleshooting

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, localhost, 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

  • Your (custom) DNS server does not contain resolution for localhost and t1c.t1t.io

You can easily test if the connector is running correctly using the following URL:

https://t1c.t1t.io:51983/info

Depending on the connector (partner related) the port can be different, make sure to verify on which port your connector should be running

Solve the DNS Rebind Issue or DNS server not resolving T1C domains

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 succeeded, 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

Other than DNS rebind, a DNS server not containing the necessary resolutions for localhost or t1c.t1t.io can cause the same issues as a DNS rebind problem.

There are 2 approaches to fix DNS rebind issues:

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

  2. update the local router which enforces the DNS Rebind

And 2 for when the configured DNS server does not contain the name resolutions;

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

  2. Ask the network administrator to update the DNS server to include name resolutions for localhost and t1c.t1t.io

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 these line
127.0.0.1       t1c.t1t.io
127.0.0.1       localhost

Save the file, restart the browser and test the url below

Depending on the connector (partner related) the port can be different, make sure to verify on which port your connector should be running

[WINDOWS]

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

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

The contents will look like this 

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host
# localhost name resolution is handle within DNS itself.
#       127.0.0.1       localhost
#       ::1             localhost

We need to add an additional line to this file:

// add these line
127.0.0.1       t1c.t1t.io
127.0.0.1       localhost

Select File > Save to save your changes. Restart your browser and test the url below

Depending on the connector (partner related) the port can be different, make sure to verify on which port your connector should be running

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

PreviousTroubleshootingNextMac OSX Sonoma

Last updated