Platform/OS
Cross-platform
Category
Media & Video Tools

QScan

QScan is a simple scanning tool that lets regular people check files and folders for problems without needing to be a tech expert. It works like a helpful security guard that quickly looks through your documents, photos, and other files to spot anything suspicious or broken. It uses S3-compatible object storage as a giant, secure digital warehouse where all your files are safely kept and easily reached whenever a scan needs to happen. Because S3 storage is cheap and scales up automatically, QScan can check millions of files without slowing down or costing a fortune. This combination means regular users get fast, reliable scans of their important stuff while only paying for the storage they actually use.

Connection / Setup

  1. Create an account and log in to DiskSpace
  2. Click I'm ready to set up my storage
  3. Enter Bucket Name following the instructions
  4. Click Create Bucket and wait for it to be generated
  5. Find your Endpoint URL, Access Key, and Secret Key in the S3 Client Configuration section for use below

Connect QScan to DiskSpace.sh (S3-compatible storage)

QScan supports DiskSpace.sh through its fully S3-compatible API. Follow the steps below to configure the connection.

Connection Steps:
  1. Open QScan and navigate to the S3 storage configuration section.
  2. Select "Custom S3 Provider" or "Add New Endpoint".
  3. Enter the following connection details:
Region: Leave empty or use us-east-1
Important: Path-Style Requests Required

DiskSpace.sh requires path-style URLs (not virtual-hosted style). QScan will automatically use the correct format:

https://s3.diskspace.sh/bucket-name/key
Example Configuration
Endpoint: https://s3.diskspace.sh
Access Key: AKIAXXXXXXXXXXXXXXXX
Secret Key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Region: us-east-1 (optional)
Path Style: Enabled (required)
Troubleshooting
  • Ensure you are using path-style requests. Virtual-hosted style is not supported.
  • Double-check that your Access Key and Secret Key are correct.
  • If connection fails, try setting Region to us-east-1.
  • Verify your DiskSpace.sh bucket exists and you have proper IAM permissions.
  • Make sure the Endpoint URL does not include a trailing slash.