Versions Compared

Old Version 1

changes.mady.by.user David Walend

Saved on

compared with

New Version 2

changes.mady.by.user Keith Dwyer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: First revision pass

Summary

The SHRINE Hub hub did not receive a response from the remote site's Adapteradapter.

Explanation

"Connection timed out" indicates that the Shrine : The SHRINE hub did not receive a response from a remote adapter in time. Check firewalls and URLs for sites on both ends.. This is typically indicative of either a firewall issue or a mistyped URL in the configuration.

"Connection refused": The SHRINE hub was able to reach the remote host, but there is nothing running on the port it was told to connect to. Typically, this means that SHRINE's Tomcat server is not running.

Resolution

"Connection timed out": Site admins should check firewalls openings on both ends. The hub administrator should verify that the URL for that site in shrine.conf's downstreamNodes block is correct.

"Connection refused": Inform the site admin for the site reporting this error. They should ensure that SHRINE is running, and report which port it is running on. The hub administrator should verify that the port for that site in shrine.conf's downstreamNodes block is correct"Connection refused" indicates that nothing is running on the remote port. Ensure that Shrine is running, and check what port it is configured to use.