Install the connector module

Do I need it?

It depends on what you want to see:

You want…	Use
Exact module versions only	Connect GitHub. Nothing to install.
PHP version, config drift, and the permissions and security-settings audit	The connector module
Everything	Both. They work well together.

• 1. Download
• 2. Install
• 3. Connect
• 4. Confirm
• Troubleshooting
• What it sends
• Uninstalling

1. Download the module

In the dashboard, open a site and click Download connector (.zip). You can also download it directly.

2. Install it on your site

Unzip it into your site's modules/custom/ folder, so this file exists:

modules/custom/drubix_connector/drubix_connector.info.yml

Then enable it:

drush en drubix_connector -y

Not using Drush? Go to Extend, find Drubix Connector under the Drubix group, tick it and click Install.

3. Connect it with your connection key

1. Generate a keyIn the Drubix dashboard, open the site, click Connector not installed → Set up, then Generate connection key.
2. Run the command it showsRun this on the Drupal site:

   drush drubix:connect drbx1_…

   Or paste the key into the module's settings at Configuration → Web services → Drubix Connector (/admin/config/services/drubix-connector) and click Save.
3. Check the resultA first report is sent straight away, and you see a success message or the reason it failed.

4. Confirm it's reporting

Within a minute, the site switches to Connector active in your dashboard, showing its PHP version and any config drift. After that the module reports during cron, at most once an hour, so make sure cron runs on the site.

To send a report now:

drush drubix:report

On the Drupal site, Reports → Status report also shows the connector's last report and any error.

Troubleshooting

What you see	What to do
The settings page says "Page not found"	The module isn't enabled yet. Run drush pm:list --filter=drubix. If it isn't "Enabled", run drush en drubix_connector -y, then drush cr.
drush en fails with "The module X does not exist"	That's a different module your site thinks is installed but whose code is missing. Restore it (composer require drupal/X) or uninstall it, then enable the connector.
The module isn't on the Extend page	Check the folder isn't nested twice after unzipping. drubix_connector.info.yml must be directly inside modules/custom/drubix_connector/.
"Invalid key" or a 401 error	The key was regenerated, or wasn't copied in full. Generate a new one and connect again.
Plan error (402)	The account is on the Free plan. Start the trial or subscribe.
Couldn't connect, or timed out	The server can't make outgoing HTTPS requests. Ask your host to allow traffic to app.drubix.com on port 443.
It worked once, then stopped	Cron isn't running on the site. Set up cron, or run drush drubix:report from a scheduled task.

What the connector sends

• Drupal core and module versions, exactly as installed
• PHP version
• Config drift: which configuration items differ from your last export
• Permissions: whether the Anonymous or Authenticated role holds a dangerous permission
• Security settings: for example, whether settings.php is writable, development modules are on, untrusted users can post unfiltered HTML, or upload fields accept executable files
• Admin accounts: for accounts that can administer the site only, the username, user ID, creation date, last login and whether two-factor login is set up
• File integrity, once a day: the paths of core and contrib files that differ from the official drupal.org release, code files that aren't part of it, and any PHP files in the public files folder (paths only, never file contents). Run it now with drush drubix:integrity

It never sends content, email addresses, passwords or database data. Every report is signed, so Drubix can tell it really came from your site. See the Privacy Policy for details.

Uninstalling

Uninstall it like any module (drush pmu drubix_connector -y) and delete the folder. Reports stop, and the history already in your dashboard stays.

Next steps