ComfyUI is a powerful and flexible interface for running Stable Diffusion workflows, but security features can sometimes prevent users from performing certain actions. One of the most common issues users encounter is the message: “This action is not allowed with this security level configuration.” While this error may seem confusing at first, it is typically related to restricted file access, node permissions, or server configuration settings. Fortunately, it can be resolved with a few straightforward adjustments.
TLDR: The “This action is not allowed with this security level configuration” error in ComfyUI usually appears due to restricted file access, security settings, or server launch parameters. Fixing it often involves adjusting the –listen flag, modifying security levels in settings, updating ComfyUI, or correcting folder permissions. Users running ComfyUI remotely may also need to tweak firewall or access configurations. With the right steps, the issue can be resolved in minutes.
Why This Error Appears in ComfyUI
ComfyUI includes built-in security controls to prevent unauthorized actions, especially when the interface is exposed to a network. These protections are useful, but they can block legitimate actions such as:
- Saving or loading workflows from custom directories
- Accessing external drives
- Using specific custom nodes
- Running ComfyUI remotely
- Executing scripts that require extended permissions
This error most commonly appears when there is a mismatch between the action being performed and the current security level set in ComfyUI’s configuration.
6 Easy Solutions to Fix the Security Configuration Error
1. Launch ComfyUI with the Right Command-Line Flags
One of the most frequent causes of this issue is running ComfyUI without the proper launch parameters. By default, ComfyUI prioritizes safety, especially if accessed over a network.
If running ComfyUI locally, users can try starting it with:
python main.py –listen
If more flexibility is needed, especially when accessing files outside default directories, adding specific trusted settings may help depending on the version being used.
Tip: Always double-check the documentation for updated security flags, as newer versions may modify how permissions are handled.
2. Adjust Security Level Settings in Configuration Files
ComfyUI may restrict actions based on internal configuration settings. Users should inspect configuration files located in the project directory.
Steps:
- Navigate to the ComfyUI root folder.
- Open relevant configuration files in a text editor.
- Look for security or access parameters.
- Adjust them carefully and save changes.
Important: Lowering security settings can expose users to risk, especially if the system is accessible over the internet. Always ensure proper firewall or network protections are in place.
3. Update ComfyUI to the Latest Version
Outdated versions of ComfyUI may contain stricter security bugs or compatibility issues with new custom nodes.
To update:
- Open a terminal in the ComfyUI directory.
- Run git pull to fetch the latest version.
- Restart ComfyUI.
Updating often resolves unexpected permission errors, especially when they are caused by version mismatches between the core interface and custom nodes.
4. Check Folder and File Permissions
Operating system-level permissions frequently trigger this error. If ComfyUI cannot read or write to certain directories, the security system may block the action.
Users should verify:
- The input folder has read access.
- The output folder has write permissions.
- External drives are properly mounted.
On Windows, right-click the folder and check Properties > Security. On macOS or Linux, inspect permissions via terminal using ls -l.
5. Review Custom Node Behavior
Some custom nodes attempt to access directories or run scripts that exceed default security levels. If the error started after installing a new node, that node may be responsible.
To troubleshoot:
- Temporarily disable recently added nodes.
- Restart ComfyUI.
- Check if the error disappears.
If the problem is confirmed, check the node’s documentation. Some developers provide instructions for safe configuration adjustments.
6. Adjust Firewall or Remote Access Settings
If ComfyUI is being accessed from another device, security layers outside the software may be interfering. This is especially common when using remote hosting, shared servers, or port forwarding.
Users should verify:
- Firewall rules allow proper access.
- Port forwarding is configured correctly.
- No VPN is restricting local actions.
Running ComfyUI locally for testing can help determine whether the issue is network-related.
Quick Comparison of the 6 Solutions
| Solution | Difficulty | Best For | Risk Level |
|---|---|---|---|
| Launch with proper flags | Easy | Local users with command-line access | Low |
| Edit configuration files | Moderate | Advanced users needing flexibility | Medium |
| Update ComfyUI | Easy | Users running older versions | Low |
| Fix folder permissions | Moderate | Users accessing custom directories | Low |
| Review custom nodes | Moderate | Those using community extensions | Medium |
| Adjust firewall settings | Advanced | Remote or network users | Medium to High |
Best Practices to Avoid the Error in the Future
Preventing this security configuration message is easier than repeatedly fixing it. A few proactive steps can help:
- Keep ComfyUI consistently updated.
- Install custom nodes from trusted sources only.
- Organize input and output directories clearly.
- Avoid lowering security settings unless necessary.
- Test workflows locally before deploying remotely.
Balancing security and usability is critical. While it may be tempting to disable restrictions entirely, doing so can introduce vulnerabilities—especially if ComfyUI is exposed to the public internet.
When to Seek Community Support
If none of the above solutions resolve the issue, users may need to consult community forums or issue trackers. When asking for help, it is important to provide:
- The ComfyUI version number
- Operating system details
- The exact error message
- Recent changes made to settings or nodes
Clear, detailed information significantly increases the likelihood of a fast solution.
Frequently Asked Questions (FAQ)
1. Is it safe to lower ComfyUI’s security level?
Lowering the security level can make certain actions easier, but it may introduce risks—especially if ComfyUI is accessible from outside the local machine. It is safest to adjust settings only as much as necessary.
2. Why did this error appear suddenly?
This often happens after installing a new custom node, updating ComfyUI, or changing folder locations. Even minor configuration changes can trigger security checks.
3. Does this error mean ComfyUI is broken?
No. The error is typically a protective measure, not a malfunction. It indicates that ComfyUI is preventing an action that conflicts with current security settings.
4. Can antivirus software cause this issue?
Yes. In some cases, antivirus or security software may restrict file access, causing ComfyUI to interpret the action as disallowed.
5. What is the fastest fix for most users?
The quickest fix is often launching ComfyUI with the appropriate command-line flags or ensuring folders have correct read and write permissions.
6. Should remote users configure additional protections?
Absolutely. Anyone running ComfyUI on a server or shared network should use firewalls, strong passwords, and secure access methods to prevent unauthorized use.
By understanding what triggers the “This action is not allowed with this security level configuration” message and applying the appropriate solution, users can quickly restore full functionality to ComfyUI. In most cases, the problem is minor and easily resolved with careful review of permissions and settings.