> ## Documentation Index
> Fetch the complete documentation index at: https://mintlify.com/n4ze3m/page-assist/llms.txt
> Use this file to discover all available pages before exploring further.

# Extension Conflicts

> Resolve issues when Page Assist conflicts with other websites

Page Assist rewrites the Origin header to avoid CORS issues when communicating with the Ollama API. While this feature is essential for the extension to work properly, it can sometimes cause issues with other websites.

## Known Conflicts

The following websites are known to have issues when Page Assist's automatic CORS fix is enabled:

<CardGroup cols={2}>
  <Card title="Intel Driver & Support Assistant" icon="microchip">
    May not load or function correctly with CORS fix enabled.
  </Card>

  <Card title="Box Tools Website" icon="box">
    Can experience authentication or loading issues.
  </Card>
</CardGroup>

<Note>
  If you discover other websites that conflict with Page Assist, please [report them on GitHub](https://github.com/n4ze3m/page-assist/issues/new) so they can be documented.
</Note>

## Solution: Disable Automatic CORS Fix

If Page Assist is causing issues with other websites, you can disable the automatic CORS fix feature.

<Steps>
  <Step title="Open Page Assist">
    Click on the Page Assist icon in your browser toolbar.
  </Step>

  <Step title="Navigate to Settings">
    Click on the **Settings** icon (gear icon).
  </Step>

  <Step title="Open Ollama Settings">
    Click on the **Ollama Settings** tab.
  </Step>

  <Step title="Expand Advanced Configuration">
    Find and expand the **Advanced Ollama URL Configuration** section.
  </Step>

  <Step title="Disable Automatic CORS Fix">
    Turn off the **Enable or Disable Automatic Ollama CORS Fix** option.

    ![Disable CORS Fix](https://pub-35424b4473484be483c0afa08c69e7da.r2.dev/Screenshot%202025-02-17%20185214.png)
  </Step>

  <Step title="Save Changes">
    Click the **Save** button to apply your changes.
  </Step>
</Steps>

<Warning>
  Disabling the automatic CORS fix will prevent Page Assist from automatically rewriting the Origin header. This may cause Ollama to start throwing 403 errors.
</Warning>

## Fix 403 Errors After Disabling CORS Fix

Once you disable the automatic CORS fix, you'll need to configure Ollama to accept connections from browser extensions. You can do this by setting the `OLLAMA_ORIGINS` environment variable.

<Tabs>
  <Tab title="Windows">
    <Steps>
      <Step title="Open Environment Variables">
        1. Open the Start menu and search for "Environment Variables"
        2. Click "Edit the system environment variables"
      </Step>

      <Step title="Add New Variable">
        1. Click the "Environment Variables" button
        2. Under "System Variables", click "New"
      </Step>

      <Step title="Configure OLLAMA_ORIGINS">
        * Set Variable name: `OLLAMA_ORIGINS`
        * Set Variable value: `*`
        * Click OK to save
      </Step>

      <Step title="Restart Ollama">
        Restart the Ollama service for changes to take effect.
      </Step>
    </Steps>
  </Tab>

  <Tab title="macOS">
    <Steps>
      <Step title="Open Terminal">
        Launch the Terminal application.
      </Step>

      <Step title="Set Environment Variable">
        Run the following command:

        ```bash theme={null}
        launchctl setenv OLLAMA_ORIGINS "*"
        ```
      </Step>

      <Step title="Restart Ollama">
        Restart the Ollama service for changes to take effect.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Linux">
    <Steps>
      <Step title="Set Environment Variable">
        Run the following command in your terminal:

        ```bash theme={null}
        export OLLAMA_ORIGINS="*"
        ```

        <Note>
          To make this permanent, add the line to your shell configuration file (`~/.bashrc`, `~/.zshrc`, etc.).
        </Note>
      </Step>

      <Step title="Restart Ollama">
        Restart the Ollama service for changes to take effect.
      </Step>
    </Steps>

    ### For systemd Users

    If you're managing Ollama with systemd, you can add the environment variable directly to your service file:

    ```bash theme={null}
    [Unit]
    Description=Ollama Service
    After=network-online.target

    [Service]
    Environment="OLLAMA_HOST=192.168.4.67:11434"
    Environment="OLLAMA_MAX_LOADED_MODELS=4"
    Environment="OLLAMA_ORIGINS=*"
    ExecStart=/usr/local/bin/ollama serve
    User=ollama
    Group=ollama
    Restart=always
    RestartSec=3
    Environment="PATH=/usr/local/sbin:/sbin:/usr/sbin:/root/bin:/usr/local/bin:/bin:/usr/bin:"

    [Install]
    WantedBy=default.target
    ```

    After editing the service file, reload systemd and restart Ollama:

    ```bash theme={null}
    sudo systemctl daemon-reload
    sudo systemctl restart ollama
    ```
  </Tab>

  <Tab title="Docker">
    If you're running Ollama in Docker, add the environment variable to your configuration:

    **Docker run command:**

    ```bash theme={null}
    docker run -d \
      -e OLLAMA_ORIGINS="*" \
      -p 11434:11434 \
      ollama/ollama
    ```

    **Docker Compose:**

    ```yaml theme={null}
    version: '3'
    services:
      ollama:
        image: ollama/ollama
        ports:
          - "11434:11434"
        environment:
          - OLLAMA_ORIGINS=*
    ```

    After updating your configuration, restart the container:

    ```bash theme={null}
    docker restart <container-name>
    ```
  </Tab>
</Tabs>

<Info>
  Setting `OLLAMA_ORIGINS=*` allows Ollama to accept requests from any origin. This resolves CORS issues but is less restrictive. For production environments, consider specifying exact origins instead of using `*`.
</Info>

## Alternative: Selective Disabling

If you only experience issues on specific websites, you can:

1. **Temporarily disable Page Assist** on those websites:
   * Right-click the Page Assist icon
   * Look for "Disable on this site" or similar option
   * The extension won't run on that specific website

2. **Use different browser profiles**:
   * Create a separate browser profile for websites that conflict
   * Keep Page Assist disabled in that profile
   * Use your main profile with Page Assist for normal browsing

## Troubleshooting Extension Conflicts

<AccordionGroup>
  <Accordion title="Website still not working after disabling CORS fix" icon="circle-xmark">
    If disabling the CORS fix doesn't resolve the issue:

    1. **Clear browser cache**: The website may have cached the modified headers
    2. **Hard refresh**: Press `Ctrl+Shift+R` (or `Cmd+Shift+R` on Mac)
    3. **Disable Page Assist entirely**: Temporarily disable the extension to confirm it's the cause
    4. **Check other extensions**: Another extension might be causing the conflict
  </Accordion>

  <Accordion title="Getting 403 errors after setting OLLAMA_ORIGINS" icon="lock">
    If you still see 403 errors after configuring the environment variable:

    1. **Verify the variable is set**: Check that `OLLAMA_ORIGINS` is actually set in your environment
    2. **Confirm Ollama restart**: Make sure you restarted Ollama after setting the variable
    3. **Check Ollama logs**: Look for CORS-related messages in the logs
    4. **Try alternative syntax**: Some systems may require `OLLAMA_ORIGINS="*"` with quotes
  </Accordion>

  <Accordion title="Need both CORS fix and website compatibility" icon="scale-balanced">
    If you need Page Assist to work while also using conflicting websites:

    **Option 1: Toggle as needed**

    * Disable CORS fix when using conflicting websites
    * Re-enable when you need to use Page Assist
    * Keep `OLLAMA_ORIGINS=*` set permanently

    **Option 2: Use browser profiles**

    * Create one profile with Page Assist enabled (with CORS fix)
    * Create another profile without Page Assist for conflicting websites
    * Switch between profiles as needed

    **Option 3: Configure Ollama globally**

    * Set `OLLAMA_ORIGINS=*` on your system
    * Disable Page Assist's CORS fix permanently
    * Both Page Assist and other websites will work
  </Accordion>

  <Accordion title="Security concerns with OLLAMA_ORIGINS=*" icon="shield-halved">
    Setting `OLLAMA_ORIGINS=*` allows any origin to connect to your Ollama instance:

    **For local-only use:**

    * This is generally safe if Ollama only binds to localhost (127.0.0.1)
    * Other machines on your network cannot access it

    **For network-accessible Ollama:**

    * Consider specifying exact origins instead of `*`
    * Example: `OLLAMA_ORIGINS="chrome-extension://your-extension-id,https://your-app.com"`
    * Use a reverse proxy with authentication for production deployments
    * Implement firewall rules to restrict access
  </Accordion>
</AccordionGroup>

## Reporting New Conflicts

If you discover a website that conflicts with Page Assist, please help the community by reporting it:

1. [Open an issue on GitHub](https://github.com/n4ze3m/page-assist/issues/new)
2. Include:
   * The website URL that's affected
   * What functionality breaks
   * Browser and version
   * Page Assist version
   * Whether disabling the CORS fix resolves it

This helps improve Page Assist and build a comprehensive list of known conflicts.

## Related Resources

<CardGroup cols={2}>
  <Card title="Connection Issues" icon="link" href="/troubleshooting/connection-issues">
    Troubleshoot Ollama connectivity problems
  </Card>

  <Card title="Common Problems" icon="circle-question" href="/troubleshooting/common-problems">
    Solutions to other frequent issues
  </Card>
</CardGroup>