First Configuration

Overview

After successfully installing the Website Access Restriction Tool, you'll need to configure it for your specific needs. This guide will walk you through the basic configuration process, focusing on environments where browser extensions are not available or desired.

Even without browser extensions, our tool provides powerful website blocking capabilities through system-level settings and configuration files. This guide will help you get started with the initial setup.

Version Information
This guide applies to version 4.4 of the Website Access Restriction Tool. If you're using an older version, please refer to our Troubleshooting Guide for upgrade instructions.

Considerations for No Extension Environments

When using the Website Access Restriction Tool without browser extensions, there are a few important considerations to keep in mind:

  • System-Level Blocking Only - Blocking will be implemented at the system level, affecting all browsers and applications
  • No Real-Time Updates - Changes to configuration may require a system restart or application restart
  • Limited Browser-Specific Rules - Rules will apply to all browsers equally
  • Dependency on Hosts File - Blocking heavily relies on the system hosts file modification
Important

Without browser extensions, some advanced features may be limited, but core blocking functionality will still work effectively.

Configuration File Structure

The Website Access Restriction Tool uses a JSON configuration file to define blocked websites and access rules. The default location of this file is:

C:\Program Files\Website Access Restriction Tool\config.json

Here's the basic structure of the configuration file:

{
  "version": "4.4",
  "blocked_sites": [
    {
      "url": "example.com",
      "reason": "Time management",
      "enabled": true,
      "type": "domain"
    }
  ],
  "schedule": {
    "enabled": false,
    "active_hours": {
      "start": "09:00",
      "end": "17:00",
      "weekdays": [1, 2, 3, 4, 5]
    }
  },
  "notifications": {
    "enabled": true,
    "message": "This website is blocked by Website Access Restriction Tool"
  },
  "logging": {
    "enabled": true,
    "level": "info"
  },
  "advanced": {
    "use_hosts_file": true,
    "use_dns_filtering": true,
    "use_network_filtering": false
  }
}

Key Configuration Options

Option Type Description
blocked_sites Array List of websites to block, with optional parameters
schedule.enabled Boolean Enable time-based blocking
schedule.active_hours Object Define active blocking hours and days
notifications.enabled Boolean Show blocking notifications
logging.enabled Boolean Enable logging of blocking events
advanced.use_hosts_file Boolean Enable hosts file modification for blocking
advanced.use_dns_filtering Boolean Enable DNS-based filtering

Initial Setup Steps

Follow these steps to configure your Website Access Restriction Tool for the first time:

  1. Open the Configuration File

    Navigate to the installation directory and open the config.json file in a text editor with administrative privileges.

  2. Add Your First Block Rule

    Edit the blocked_sites array to include websites you want to block:

    "blocked_sites": [
      {
        "url": "facebook.com",
        "reason": "Productivity",
        "enabled": true,
        "type": "domain"
      },
      {
        "url": "twitter.com",
        "reason": "Productivity",
        "enabled": true,
        "type": "domain"
      }
    ]
  3. Configure Schedule (Optional)

    If you want to enable time-based blocking, update the schedule section:

    "schedule": {
      "enabled": true,
      "active_hours": {
        "start": "09:00",
        "end": "17:00",
        "weekdays": [1, 2, 3, 4, 5]  // Monday to Friday
      }
    }
  4. Save the Configuration

    Save the changes to the config.json file.

  5. Restart the Application

    Close and restart the Website Access Restriction Tool for changes to take effect.

  6. Verify Changes

    Open the application and navigate to the "Blocked Sites" tab to verify your changes have been applied.

Testing Your Configuration

After setting up your initial configuration, it's important to test that it's working correctly:

  1. Open a Web Browser

    Launch any web browser installed on your system.

  2. Attempt to Access a Blocked Site

    Try to visit one of the websites you added to the blocked list.

  3. Check for Blocking

    You should see a blocked page or error message indicating the site is restricted.

  4. Test Multiple Browsers

    Repeat the test with different browsers to ensure blocking works across all applications.

  5. Check Logs

    If logging is enabled, check the logs for information about blocked requests.

Success!
If you see the blocked message, your configuration is working correctly. If not, refer to the troubleshooting section below.

Common Issues & Solutions

If you encounter problems with your configuration, try these solutions:

Blocking Not Working

  • Ensure the application is running with administrator privileges
  • Check that the hosts file is not read-only
  • Restart your system after making changes
  • Verify that the URL format is correct in the configuration

Configuration Not Saving

  • Make sure you're editing the correct config.json file
  • Ensure you have write permissions to the file
  • Check that the JSON format is valid
  • Try running the text editor as administrator

Partial Blocking

  • Some websites may use multiple domains - block all relevant domains
  • Check if the website is using HTTPS vs HTTP and ensure both are blocked
  • Consider using wildcard patterns for subdomains

Next Steps

Now that you've completed the basic configuration, you're ready to explore more advanced features:

If you need further assistance, please refer to our Troubleshooting Guide or FAQ section.

Legacy Version Usage Instructions

We are committed to providing users with the best product experience and technical support. With the continuous development of technology, we have had to adjust our support strategy for older versions:

Versions No Longer Supported

Except for versions 1+ and 2+, all other older versions (including but not limited to v0.1-v1.0, v2.0-v2.9, etc.) are no longer supported. This means:

Reasons for Discontinuation

  1. Outdated Technology: Older versions are based on outdated technical architectures and cannot adapt to modern operating systems and browser environments
  2. Security Risks: Older versions have potential security vulnerabilities that cannot be fixed in a timely manner
  3. High Maintenance Costs: Maintaining multiple versions simultaneously diverts development resources, affecting the iteration speed of new versions
  4. Large Function Differences: Older versions have significant functional differences from the current version, resulting in high support costs

Recommended Upgrade Path

If you are still using an unsupported older version, we strongly recommend upgrading to the latest version:

  1. Back up your current configuration data (if any)
  2. Uninstall the old version of the software
  3. Download the latest version from our official website: https://websiteblocker.vercel.app/download
  4. Install the latest version and reconfigure your settings
Important Note

Continuing to use unsupported older versions may cause the software to not work properly, pose security risks, and may be incompatible with new operating systems. Please upgrade to the latest version as soon as possible for the best experience and security.