Skip to main content

Connecting Files.com

This guide walks you through connecting a Files.com storage destination to Pluton.

Prerequisites

Before connecting Files.com, you need:

  1. A Files.com account - Sign up here
  2. Your site subdomain and either an API key or username/password credentials

About Files.com

Files.com is a cloud storage service that provides secure file storage, sharing, and automation. It supports multiple authentication methods including API keys and username/password. Files.com offers enterprise-grade features such as audit logging, compliance tools, and advanced access controls.

Getting Your Credentials

  1. Log into your Files.com account
  2. Navigate to SettingsAPI Keys (or follow the API Keys documentation)
  3. Click Create API Key
  4. Give the key a descriptive name (e.g., "Pluton Backups")
  5. Set appropriate permissions and expiration
  6. Copy the generated API key
  7. Important: Save the API key immediately — it may only be shown once

Option B: Username/Password Authentication

  1. Note your Files.com username
  2. Have your account password ready
  3. This method works but API key authentication is recommended for automated systems

Note Your Site Subdomain

  1. Your Files.com site subdomain is the part before .files.com in your URL (e.g., if your URL is mysite.files.com, the subdomain is mysite)
  2. If you use a custom domain (e.g., myfiles.customdomain.com), use the full custom domain instead

Connecting to Pluton

Pluton Files.com

Step 1: Add Storage

  1. In Pluton, navigate to Storages
  2. Click Add Storage button
  3. Select Files.com from the provider list

Step 2: Configure Connection

Fill in the required fields:

  • Storage Name: A friendly name (e.g., "Files.com Backups")
  • Site Domain: Your site subdomain (e.g., mysite) or custom domain (e.g., myfiles.customdomain.com)
  • API Key: Your Files.com API key

If using username/password authentication instead:

  • Username: Your Files.com username
  • Password: Your Files.com password

Step 3: Advanced Options (Optional)

No additional advanced options are required for standard usage.

Step 4: Test and Save

  1. Click Test Connection to verify credentials
  2. If successful, click Save
  3. Your Files.com storage is now ready for backup plans

Authentication Methods

API Key (Recommended):

  • Most secure for automated systems like Pluton
  • Can be scoped with specific permissions
  • Can be revoked independently without changing your password
  • Set an expiration date for additional security

Username/Password:

  • Simpler setup
  • Uses your account credentials directly
  • Password changes will require updating the Pluton configuration

You can provide both an API key and username/password, but the API key takes precedence.

Checksums and File Integrity

Files.com supports CRC32 and MD5 checksums for file integrity verification. To use this feature:

  1. Log into your Files.com account
  2. Go to Data GovernanceFile Integrity
  3. Enable the checksum algorithms you want (selecting at least MD5 is recommended)
  4. This allows Pluton to verify end-to-end file integrity during backups

Common Issues

Authentication Failure: Verify your API key is correct and hasn't expired. If using username/password, ensure your credentials are current.

Site Not Found: Double-check your site subdomain. It should be just the subdomain (e.g., mysite), not the full URL (mysite.files.com).

Permission Denied: Ensure your API key or user account has read and write permissions for the directories you want to back up to.

Checksum Mismatch: If you see integrity errors, enable MD5 checksums in your Files.com File Integrity settings.

Best Practices

  • Use API key authentication for automated backup systems
  • Set an expiration date on API keys and rotate them periodically
  • Enable MD5 checksums in Files.com for end-to-end file integrity verification
  • Create a dedicated folder in Files.com for Pluton backups
  • Monitor storage usage and access logs through the Files.com dashboard
  • Use the minimum required permissions when creating API keys