No Connection to the Web Interface

Bridge Cannot be Started

Problem

The Bridge cannot be started in the browser.

Solution 1

The Windows service (E2E Console) respectively the E2E Console background daemon has not been started yet (see section Bridge Web Page cannot be displayed).

Open the Windows Services tool and start the Bridge service E2E Console manually, respectively start the Bridge background daemon E2E Console.
Change the status of the Bridge service to automatic.

Solution 2

The E2E Console background daemon does not start.

On UNIX systems, the Bridge system user needs a shell to start the E2E Console background daemon. Change the Bridge system user as to have a shell.

Solution 3

You are using current versions of Chrome, Firefox, or Internet Explorer with a Bridge version 6.0.52.5 or lower and get one of the following error messages:

Browser	Error Message
Chrome	"Your connection is not private."
Firefox	"Secure connection failed."
Internet Explorer	"This page can't be displayed."

The JRE 1.6 of the Bridges version 6.0.52.5 or lower cannot generate keys that are good enough for a secure SSL communication. Upgrade to a Bridge version 6.0.53.1 or higher.

In Firefox, you have the possibility to enable the weak options:

Enter about:config in the Firefox location bar.
Accept the next security warning.
Enter security.ssl3.dhe_rsa_aes in the search field. You get two entries.
Change both entries with a double click to false. You do not have to restart Firefox.

Please note: This is a global option in Firefox and applies to all connections.

Solution 4

You updated your Bridge installation to version 6.0.53 or higher without deleting file e2e_bridge_prog/servlets/server.xml (see E2E Bridge Release Notes).

Browser	Error Message
Chrome	`SSL connection error` `ERR_SSL_PROTOCOL_ERROR` `Hide details` `Unable to make a secure connection to the server. This may be a` `problem with the server, or it may be requiring a client` `authentication certificate that you don't have`.
Firefox	`Secure Connection Failed` `An error occurred during a connection to abc.your.domain:8080.` `SSL received a record that exceeded the maximum permissible length.` `(Error code: ssl_error_rx_record_too_long)` `The page you are trying to view cannot be shown because the` `authenticity of the received data could not be verified. Please` `contact the website owners to inform them of this problem.`

Stop the Bridge, delete file e2e_bridge_prog/servlets/server.xml, and re-run the same update.

Solution 5

The browser is not supported. The Bridge supports the latest versions of the following browsers:

Google Chrome
Mozilla Firefox
Microsoft Edge

Additionally, Microsoft Internet Explorer 11 is still supported.

Bridge not Opened in Browser

Problem 1

The URL https://localhost:8080 does not open the Bridge.

Solution 1

The proxy is not bypassed for localhost.

Browser	Error Message
Firefox (Mozilla)	Make sure that you have chosen Direct connect to the Internet or no proxy for: localhost in the browser settings.
Internet Explorer	Make sure that no proxy is used for local addresses. Choose Bypass proxy server for local addresses in the browser settings.

Instead of localhost you can also write the IP address or the full computer name (see in the Windows system properties: right mouse click on My Computer, Properties). For instance https://e2ebridge.e2e.ch:8080.

Problem 2

The Bridge cannot be started in the browser resp. no security alert relating the installed default certificate has been displayed.

Solution 1

The browser's security policy does not allow displaying the web site without a certificate whose certifying authority is trusted.

Check the browser's security or privacy settings.

Solution 2

If you are connecting the web site via a proxy or a firewall, the content may be filtered due to the default certificate whose certifying authority is not trusted.

Ask your network administrator to not filter content for the used Bridge URL.

Related Pages:

Troubleshooting the Bridge and Related Problems