Issue¶

Content Hub isn't connecting.

Resolution¶

There are several ways to check to ensure your site is setup properly to connect to Content Hub, outlined below.

Important Note 

Status page¶

Check the /admin/reports/status page for any errors or warnings regarding Content Hub.

Known Issues and Release Notes¶

Check the Known Issues and Release Notes for any incompatibility issues:

• https://docs.acquia.com/contenthub/release-notes/
• https://docs.acquia.com/contenthub/known-issues/

Modules¶

Use drush pml to ensure the Content Hub and any other associated modules are installed on all sites, for example:

@sitename.prod drush --uri=mysite.com pml | grep hub

Acquia Content Hub           Acquia Content Hub (acquia_contenthub)                                          Module  Enabled    8.x-1.40

 Acquia Content Hub           Acquia Content Hub Diagnostic Tool (acquia_contenthub_diagnostic)               Module  Not installed  8.x-1.40

 Acquia Content Hub           Acquia Content Hub Status (acquia_contenthub_status)                            Module  Not installed  8.x-1.40

 Acquia Content Hub           Acquia Content Hub Subscriber (acquia_contenthub_subscriber)                    Module  Enabled   8.x-1.40

Acquia Content Hub            Acquia Content Hub (acquia_contenthub)                          Enabled

  Acquia Content Hub            Acquia Content Hub Diagnostic Tool (acquia_contenthub_diagnostic)   Enabled

Alternatively, you can check the Drupal admin interface at /admin/config/services/acquia-contenthub.

Check that the hub has content¶

Ensure the site is connected to the Content Hub services by running drush ach-list against the website. No errors should return:

@sitename.env drush ach-list --uri=www.example.com 

Array
(
    [success] => 1
    [total] => 5522
    [data] => Array
        (
            [0] => Array
                (
                    [uuid] => abcdefg-123456-765432hijk
                    [origin] => 9n4f-nbgft67-kjnbgft67-uikjhgtyui
                    [modified] => 2020-02-02T13:57:04-05:00
                    [type] => node
....
            [999] => Array
                (
                    [uuid] => 8f48fc0d-7479-4e6d-8086-90c5668ff79b
                    [origin] => 9n4f-nbgft67-kjnbgft67-uikjhgtyui
                    [modified] => 2020-02-02T10:02:17-05:00
                    [type] => your_product
                )
        )
    [next] => https://us-east-1.content-hub.acquia.com/entities?limit=1000&start=1000
)
1   5524    Array https://us-east-1.content-hub.acquia.com/entities?limit=1000&start=1000

If you see 0 entities, that indicates the site is connected to Content Hub properly, but no entities have been exported to Content Hub. 

API and secret key values¶

Sites connected to the same hub should have the same API and secret keys. If not, the sites are not "talking" to the same hub, and therefore cannot syndicate between each other.

drush -l <site url> cget acquia_contenthub.admin_settings --include-overridden

Expected output:

• Subscribing sites should return a webhook. Without a webhook, a site cannot import syndicated content. 
• Publisher sites do not return webhooks.
• No two sites should have the same origin UUID. If they do, start enforcing the config using https://docs.acquia.com/lift/developer/settings-php/.

"Signature not valid" error message¶

If the shared_secret stored in the Drupal site's DB and/or hardcoded in its settings.php is wrong, the validation will fail and the webhooks hit will result in the "Signature not valid" error message. You can use Drush command acquia-contenthub-update-secret (i.e. ach-upsec) to retrieve and update your shared_secret value. Make sure your config value overrides and config management is not overriding your newly updated value.