1. What are the pre-requisite for installing and using a Bridge in Qntrl? 

• Ensure administrative privileges for installation.
  
• Java Runtime Environment (JRE) is required. If not available, the bundled Java with Bridge Agent can be used.
  

2. What are the system requirements to install and use Qntrl Bridge?   

**Storage refers to the amount required for Bridge installation and operation logs.

3. Which operating systems are supported for Qntrl Bridge installation?   

Qntrl Bridge is supported on:

Windows:

• Windows 8, 10, 11

• Windows Server 2012, 2016, 2019

Linux:

• Ubuntu 18+

• CentOS 7+

• Red Hat 6+

Other OS versions may work, but performance is not guaranteed.

4. How do I download and install the Bridge?   

• Navigate to (settings) >> Advanced >> Bridge >> Downloads.
• Choose the appropriate OS and download the Bridge ZIP.
• Extract and follow the installation steps provided in the help page.

5. How do I start or stop the Bridge?   

You can start or stop the Bridge by running the following commands in the terminal.

Linux/Mac:

sh <Bridge-path>/bin/bridge.sh start     # Start
sh <Bridge-path>/bin/bridge.sh stop      # Stop

Windows:

<Bridge-path>\bin\bridge.bat start       # Start
<Bridge-path>\bin\bridge.bat stop        # Stop

6. How do I restart the Bridge in Linux/Mac OS?  

By running the following commands in the terminal:

sh <Bridge-path>/bin/bridge.sh restart

7. How do I restart the Bridge in Linux/Mac OS?  

You can restart the bridge by running the following command in the terminal:

<Bridge-Path>\bin\bridge.bat restart

or

Goto settings(settings) >> Services >> Qntrl Bridge, and restart the service

8. My Bridge isn’t working. How do I reinstall it? 

In your terminal, go to bridge terminal and execute the below commands.  

Linux/Mac:

sudo sh bin/bridge.sh remove
sudo sh bin/bridge.sh installstart

Windows:

sudo bin\bridge.bat remove
sudo bin\bridge.bat installstart

9. The Bridge is inactive. What should I check?   

• Make sure the Bridge has started and is running on the correct port.
• If not running, use sh<Bridge-path>/bin/bridge.sh start
• If the bridge is running on the correct port but still inactive, check the log files in the <Bridge-path>/logs directory - especially logs.txt and wrapper.log for errors.

10.  What should I do if my bridge did not start after system reboot (Windows)  ?

• Go to Services, check if Qntrl Bridge is running.
  
• If not, manually start the bridge by running the given command in your windows terminal: <Bridge-path>\bin\bridge.bat start .
• If it fails, check the Bridge logs for errors.

11. How do I uninstall the Bridge?   

Windows:

You can uninstall the bridge by running the following command in the terminal:

<Bridge-path>\bin\bridge.bat remove

To manually remove all bridge files, use the following command in Command Prompt (cmd):

rd /s /q <Bridge-path>    # (CMD)
Remove-Item -Recurse -Force <Bridge-path>   # (PowerShell)

Linux/Mac:

You can uninstall the bridge by running the following command in the terminal:

sh <Bridge-Path>/bin/bridge.sh remove

If you want to remove all bridge files manually, use the following command:

rm -rf <Bridge-Path>

Ensure you have the necessary permissions before executing these commands.  

12. Can I install multiple bridges in one org?

13. Can multiple bridges run on the same machine?

14. Why am I getting certificate errors when calling local domains or IPs from the Bridge?   

This usually occurs if you're calling a non-public domain without a trusted certificate.

To resolve:

1. Extract the Certificate

• openssl s_client -connect <domain:port> -showcerts

• Copy only the certificate section and save it as .pem file.

• Alternatively, export it via browser.

2. Upload to Bridge

• Go to /account/ssl in the Bridge Agent UI.

• Upload the .pem file to the Truststore section.

15.  Bridge installed and started, but not visible in Bridge section?  

• Confirm if the machine has network access to the Qntrl domain.

• If using a proxy, make sure proxy settings are correctly configured in the Bridge.

• Refer to logs for debugging.