If you've signed up for the service and did not receive an email, you can request that a temporary password be sent to you. If you don't know your account username or email address, contact us for assistance.

If your site is not appearing on your dashboard, check that you've entered your token correctly on your site and saved it.

Visit "Tag1 Quo" at /admin/settings/tag1quo on your site and enter your API token, then click Save configuration.

If your API token is entered properly, saved, and you receive the following error

Failed to validate token with server. Full details of the transaction are in the system log.

There are two potential causes to rule out:

  1. Do you have a firewall preventing you from making outgoing connection attempts from that server?
    Please check with your network administrator to rule out any firewall or DNS issues. For Tag1 Quo to work properly, you'll need to allow this request to go out.
  2. Are you running an outdated version of OpenSSL?
    We strictly disallow SSL handshakes with older known-insecure ciphers, and that can cause these sorts of failures.

You can test whether or not this is your problem by running the following command from the web server:

curl -I https://quo.tag1consulting.com

If you get an "Unknown SSL protocol error" you are running an insecure version of SSL. If you're unable to upgrade SSL on your server, we provide a legacy endpoint allowing you to use our service. To enable, you'll have to add the following line to the appropriate Drupal settings.php configuration file:

$conf['tag1quo_url'] = 'https://quo-legacy.tag1consulting.com/2.1/site';

The Tag1 Quo service should then operate normally for you.

In most cases, you’ll want to run Tag1 Quo on your production website. Installing it and running it on your live site will allow you to capture update history within Tag1 Quo, which is useful data.

However, if your workflow requires running Tag1 Quo on a non-production instance of your site and you do not have any available site subscriptions, you can work around this limitation by specifying manual overrides via settings.php

If a site on your dashboard is indicating that it has not sent an update in the last 24 hours:

  1. Check that your API token is entered correctly on your site at /admin/settings/tag1quo. Verify that Report enabled module information to Tag1 Consulting, Inc is checked. Click Save configuration
  2. Go to /admin/settings/tag1quo/status. If cron is not running on your site, you will see A heartbeat will be sent to Tag1 the next time cron runs. (See Setting up cron for help on setting up a Drupal cron job).
  3. Click on Send manually at /admin/settings/tag1quo/status. If the page updates with Module status reported to Tag1 Consulting., your site is properly configured for reporting to Tag1 Quo. If you get an error message, make note of that error, and gather some additional information for troubleshooting.

When requesting assistance with an issue, our support team may ask for additional information, including error and debugging logs. Please be prepared to provide them with the following:

Error logs:

  • Go to /admin/reports/dblog and expand Filter log messages.
  • Select Tag1 Quo from the Type column.
  • Provide these logs to Tag1 Quo's support team, if requested.

Debug logs:

  • Go to /admin/settings/tag1quo, expand Advanced, and enable Debug logging.
  • Click on Send manually.
  • Go to /admin/settings/tag1quo/review, scroll to the bottom and expand Raw data.
  • Triple-click into the expanded Raw data field to copy that data and provide this to Tag1 Quo's support team.