Extension Conflicts

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:

Intel Driver & Support Assistant

May not load or function correctly with CORS fix enabled.

Box Tools Website

Can experience authentication or loading issues.

If you discover other websites that conflict with Page Assist, please report them on GitHub so they can be documented.

Solution: Disable Automatic CORS Fix

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

Open Page Assist

Click on the Page Assist icon in your browser toolbar.

Navigate to Settings

Click on the Settings icon (gear icon).

Open Ollama Settings

Click on the Ollama Settings tab.

Expand Advanced Configuration

Find and expand the Advanced Ollama URL Configuration section.

Disable Automatic CORS Fix

Turn off the Enable or Disable Automatic Ollama CORS Fix option. Disable CORS Fix

Save Changes

Click the Save button to apply your changes.

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

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.

Windows
macOS
Linux
Docker

Open Environment Variables

Open the Start menu and search for “Environment Variables”
Click “Edit the system environment variables”

Add New Variable

Click the “Environment Variables” button
Under “System Variables”, click “New”

Configure OLLAMA_ORIGINS

Set Variable name: OLLAMA_ORIGINS
Set Variable value: *
Click OK to save

Restart Ollama

Restart the Ollama service for changes to take effect.

Open Terminal

Launch the Terminal application.

Set Environment Variable

Run the following command:

launchctl setenv OLLAMA_ORIGINS "*"

Restart Ollama

Restart the Ollama service for changes to take effect.

Set Environment Variable

Run the following command in your terminal:

export OLLAMA_ORIGINS="*"

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

Restart Ollama

Restart the Ollama service for changes to take effect.

For systemd Users

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

[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:

sudo systemctl daemon-reload
sudo systemctl restart ollama

If you’re running Ollama in Docker, add the environment variable to your configuration:Docker run command:

docker run -d \
  -e OLLAMA_ORIGINS="*" \
  -p 11434:11434 \
  ollama/ollama

Docker Compose:

version: '3'
services:
  ollama:
    image: ollama/ollama
    ports:
      - "11434:11434"
    environment:
      - OLLAMA_ORIGINS=*

After updating your configuration, restart the container:

docker restart <container-name>

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 *.

Alternative: Selective Disabling

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

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
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

Website still not working after disabling CORS fix

If disabling the CORS fix doesn’t resolve the issue:

Clear browser cache: The website may have cached the modified headers
Hard refresh: Press Ctrl+Shift+R (or Cmd+Shift+R on Mac)
Disable Page Assist entirely: Temporarily disable the extension to confirm it’s the cause
Check other extensions: Another extension might be causing the conflict

Getting 403 errors after setting OLLAMA_ORIGINS

If you still see 403 errors after configuring the environment variable:

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

Need both CORS fix and website compatibility

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

Security concerns with OLLAMA_ORIGINS=*

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

Reporting New Conflicts

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

Open an issue on GitHub
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.

Connection Issues

Troubleshoot Ollama connectivity problems

Common Problems

Solutions to other frequent issues

Get Started

Core Features

AI Providers

Configuration

Troubleshooting

Resources

Known Conflicts

Intel Driver & Support Assistant

Box Tools Website

Solution: Disable Automatic CORS Fix

Fix 403 Errors After Disabling CORS Fix

For systemd Users

Alternative: Selective Disabling

Troubleshooting Extension Conflicts

Reporting New Conflicts

Connection Issues

Common Problems

Build docs developers (and LLMs) love

Get Started

Core Features

AI Providers

Configuration

Troubleshooting

Resources

​Known Conflicts

Intel Driver & Support Assistant

Box Tools Website

​Solution: Disable Automatic CORS Fix

​Fix 403 Errors After Disabling CORS Fix

​For systemd Users

​Alternative: Selective Disabling

​Troubleshooting Extension Conflicts

​Reporting New Conflicts

​Related Resources

Connection Issues

Common Problems

Build docs developers (and LLMs) love

Known Conflicts

Solution: Disable Automatic CORS Fix

Fix 403 Errors After Disabling CORS Fix

For systemd Users

Alternative: Selective Disabling

Troubleshooting Extension Conflicts

Reporting New Conflicts

Related Resources