If Pure-FTPd returns “permission denied” for SITE CHMOD, check the daemon policy before changing Unix permissions. The failure normally comes from one of four places: Pure-FTPd may have disabled CHMOD, the account may not own the target, a parent directory may block traversal, or you may be trying to change an existing file when you really need different permissions for future uploads.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
Work through the checks below in order. Use a privileged shell for filesystem inspection and repairs, and make the narrowest change that solves the problem.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What a Pure-FTPd chmod error means
Pure-FTPd exposes Unix permission changes through the FTP SITE CHMOD extension. When the feature is enabled, an authenticated user can change the permissions of files they own. A successful FTP login alone does not grant that right: the server still applies its own policy and the operating system’s ownership, mode-bit and directory rules.
There are three separate decisions to identify:
- Daemon policy: whether Pure-FTPd allows the CHMOD command at all.
- Object authorization: whether the logged-in account is permitted to modify this file or directory, and whether it can traverse every parent directory.
- Timing: whether you are repairing an object that already exists or setting the creation mask for objects uploaded later.
Fixing the wrong layer can create a security problem without making the command work. For example, changing a file’s mode cannot help if the daemon was started with CHMOD disabled, and changing an upload mask will not alter a file that is already on disk.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
1. Check whether Pure-FTPd disabled SITE CHMOD
The first check is the Pure-FTPd startup policy. The -R option disables use of CHMOD for all users, including authenticated non-anonymous users. Debian’s pure-ftpd(8) manual describes it as: “Disallow users (even non-anonymous ones) usage of the CHMOD command.” If -R is active, the client may show a command-not-allowed or permission-style error regardless of the file owner.
Find the active server options
Inspect the command line used by the running daemon or the service-manager configuration that launches it. A practical first check is:
Free tools Windows power users keep installed
One-click scans. No signup required.
ps -ef | grep '[p]ure-ftpd'Look for -R in the effective options, not merely in an unused configuration file. On systems using a service manager, inspect the unit’s start command and any included option files, then reload the service configuration and restart Pure-FTPd using your platform’s normal administrative procedure.
Decide whether enabling CHMOD is appropriate
Remove or change -R only when users genuinely need to manage permissions on their own files. Enabling SITE CHMOD gives users control over mode bits on objects they are authorized to change; it does not make them owners of other users’ files. If the server is deliberately locked down, leave -R in place and perform permission changes through an administrator-controlled deployment or file-management process instead.
After changing the policy, reconnect the FTP session. Long-lived sessions or pooled connections can retain the old server state until the client logs in again.
2. Confirm the account, path and target object
FTP paths are interpreted inside the user’s FTP root or chroot. The path displayed to the client is therefore not necessarily the same absolute path an administrator sees in the shell. Before changing permissions, establish exactly which object the command addresses.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Verify the logged-in identity
Confirm the username in the FTP client and make sure it is the account that owns the upload. If several virtual users map to one Unix account, inspect the mapped Unix identity rather than relying on the name shown by the client. A user can normally use SITE CHMOD for its own files when the feature is enabled, but not for an unrelated account’s files.
Verify the target from both viewpoints
- In the FTP client, list the directory and copy the exact relative name, including capitalization and spaces.
- Resolve that name to the server-side path using the account’s FTP-root or chroot configuration.
- From an administrator shell, inspect the corresponding object and its parent directories.
- Retry with a disposable test file whose ownership and path are unambiguous.
A common mistake is issuing SITE CHMOD against a directory name that exists in the administrator’s filesystem but is outside the FTP user’s visible tree. Another is changing a similarly named file in a different directory.
3. Inspect Unix ownership, mode bits and parent traversal
Once the daemon permits CHMOD and the path is correct, ordinary Unix rules determine whether the operation can succeed. Inspect the target and every directory leading to it:
stat -c '%A %a %U:%G %n' -- /srv/ftp/example/file.txt
namei -l /srv/ftp/example/file.txtstat shows symbolic permissions, numeric mode, owner and group. namei -l, where available, displays permissions for each path component so you can spot a parent directory that blocks traversal.
Recommended Free Tools
Ownership and group authorization
The account normally needs to own the target object to change its mode through SITE CHMOD. If the file belongs to another account, changing the group or adding write permission for “other” is not a safe substitute for correcting ownership. An administrator can verify and, when justified, repair ownership with commands such as:
chown ftpuser:ftpgroup -- /srv/ftp/example/file.txt
chmod 0640 -- /srv/ftp/example/file.txtUse the actual service account and group for your installation. Do not run a recursive chown or chmod on an entire FTP tree unless you have audited every object; recursive changes can damage private files, executable directories and application-owned data.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Execute permission on every parent directory
Directory execute permission means “traverse.” A user can fail to access or modify a file even when the file’s own mode looks correct if one parent directory lacks execute permission for that user, its group or everyone. For a path such as /srv/ftp/example/file.txt, check /srv, /srv/ftp and /srv/ftp/example, not just file.txt.
Grant only the needed traversal right. For example, adding group execute permission to a parent directory may be sufficient:
chmod g+x -- /srv/ftp/exampleDo not make a private parent directory world-writable merely to get one FTP operation working. If the account should not see sibling names, consider a directory layout that gives it traversal without broad listing rights, and test the result with the actual account.
Read and write are not interchangeable with traversal
Directory read permission controls listing names; execute permission controls entering the directory and accessing known names. A user may be able to upload to a directory while being unable to list it, or may see a name but be unable to reach the file because a higher directory blocks traversal. Diagnose each path component separately instead of assuming that a successful upload proves all permissions are correct.
4. Repair an existing file or directory safely
If the goal is to change an object that already exists, use the administrator shell after confirming ownership and the intended mode. Typical examples are:
# User read/write; group read; no access for others
chmod 0640 -- /srv/ftp/example/report.csv
# User read/write/execute; group read/execute; no access for others
chmod 0750 -- /srv/ftp/example/scripts
Choose a mode based on who must read, modify or traverse the object. A regular file usually does not need execute permission; a directory generally needs execute permission for users who must enter it. Preserve special bits only when you understand why they are present.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Using SITE CHMOD from an FTP client
When policy and ownership allow it, issue the command in the client’s raw-command or console feature:
SITE CHMOD 640 report.csvSome graphical clients expose the same operation under a file-properties dialog. The client may display a generic “permission denied” for several distinct server responses, so check the server log or an FTP transcript if the command still fails. Test one file first, then verify the resulting mode with stat.
Why changing the file may still not solve an upload workflow
Changing an existing file affects only that inode. A later upload creates a new inode and receives permissions calculated from the server’s creation settings and the client’s requested mode. If the complaint is that every new upload is too open or too restrictive, skip to the -U section instead of repeatedly running CHMOD after each transfer.
5. Set permissions for future uploads with -U
Pure-FTPd’s -U option controls creation masks for new files and directories. It does not repair existing objects. Current Pure-FTPd project documentation describes default masks of 133 for files and 022 for directories. The effective mode also depends on the base mode requested by the upload operation, so verify the result with a disposable upload.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems| Setting or example | What it controls | Illustrative result with common base modes |
|---|---|---|
Default file mask 133 |
Permissions removed from newly created regular files | 0666 minus the mask commonly yields 0644 |
Default directory mask 022 |
Permissions removed from newly created directories | 0777 minus the mask commonly yields 0755 |
-U 177:077 |
More private defaults for new files and directories | 0666 commonly yields 0600; 0777 commonly yields 0700 |
The Debian manual documents -U 177:077 as making new files readable only by the user and new directories accessible only to the user. Treat these as masks, not absolute modes: the client’s requested base mode and the daemon’s handling determine the final result.
Change the mask deliberately
- Record the current Pure-FTPd startup options and the permissions of several recent uploads.
- Choose the collaboration model: private user-only files, user-and-group files, or a deliberately shared directory.
- Adjust the file and directory masks in the service configuration.
- Restart or reload Pure-FTPd according to your service manager.
- Upload a disposable file and directory, then check them with
stat. - Confirm that downloads, application access and any backup process still work.
Do not assume that a mask change retroactively fixes files already on disk. Apply a separate, reviewed migration with find and targeted chmod rules if existing data must be brought into the new policy.
6. Handle shared directories with the sticky bit
Shared writable directories create a different problem: deletion. Under standard Unix behavior, the owner of a directory can delete entries in it even when those entries belong to other users. The Pure-FTPd FAQ recommends the sticky bit for a public shared directory:
chmod 1777 publicThe leading 1 is the sticky bit; the remaining 777 grants read, write and execute to user, group and others. With the sticky bit set, users can generally delete or rename only entries they own (or entries they are otherwise privileged to manage), while still being able to create files in the shared directory.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallUse this pattern only for a directory that is intentionally public. It does not make files private, does not grant SITE CHMOD, and does not replace correct ownership or group design. For a team-only drop folder, a dedicated group, setgid directory and a restrictive umask may provide better isolation than world-writable permissions.
7. Account for Pure-FTPd’s home-directory safety rules
Pure-FTPd advertises safety restrictions on user home directories. As a result, an account may be able to change modes on ordinary files it owns but be prevented from applying dangerous permissions to the home-directory root itself. This is expected protection, not proof that the daemon is malfunctioning.
When a command fails only on the home root or another protected boundary, compare it with a test file in a normal subdirectory. Keep the home directory’s ownership and restrictive traversal settings intact, and make changes inside dedicated data directories instead of weakening the account boundary.
8. A complete diagnostic procedure
Use this sequence when the cause is unclear:
- Capture the exact FTP response. Record whether the server says the command is unavailable, the operation is denied, or the path cannot be found.
- Check the effective daemon options. Confirm whether
-Rdisables CHMOD. If it does, decide whether policy should change before touching filesystem modes. - Reconnect after policy changes. Start a fresh FTP session so the test uses the current daemon configuration.
- Identify the Unix account. Verify the FTP login-to-Unix mapping and the owner and group shown by
stat. - Resolve the chroot-relative path. Make sure the client’s filename maps to the intended server-side object.
- Inspect every path component. Check owner, group, mode and execute permission on each parent directory.
- Test a user-owned disposable file. This separates a policy problem from an ownership or path problem.
- Repair only the required object. Use a targeted
chownorchmod, then verify withstat. - Separate future-upload requirements. If new files are wrong, review
-Umasks and test a new upload instead of repeating CHMOD. - Review shared-directory behavior. Add the sticky bit only where shared deletion semantics require it.
- Check protected home boundaries. If only the home root fails, preserve Pure-FTPd’s safety restriction and work in a subdirectory.
Common symptoms and the most likely layer
| Symptom | Likely cause | Targeted check |
|---|---|---|
| Every account receives “CHMOD not permitted.” | Pure-FTPd was started with -R. |
Inspect the effective daemon command line and service configuration. |
| One user cannot change a file created by another account. | Ownership or group authorization does not match the request. | Compare stat owner/group with the FTP account mapping. |
| The file mode looks correct, but the operation still fails. | A parent directory lacks execute (traverse) permission. | Inspect each component with namei -l or equivalent. |
| Existing files are fixed, but every new upload is wrong. | Creation masks, not the existing file mode, need changing. | Review -U, upload a test object and measure its mode. |
| Only the home directory itself rejects the command. | Pure-FTPd’s home-directory safety restrictions apply. | Test a normal child file and leave the home boundary protected. |
| Users can upload but can delete one another’s files. | A shared writable directory lacks the sticky bit. | Use a deliberate shared-directory design; for a public directory, consider chmod 1777 public. |
Security rules that prevent recurring permission errors
- Keep daemon policy and filesystem policy separate. Enabling SITE CHMOD does not require making directories world-writable.
- Prefer ownership and groups over “other” permissions. Give a team access through a controlled group and directory layout.
- Grant directory execute permission intentionally. It is required for traversal, but it also determines which paths an account can reach.
- Avoid recursive emergency fixes. A blanket
chmod -R 777can expose uploads, break application assumptions and make later diagnosis harder. - Test with disposable objects. Verify both an existing-file CHMOD and a newly created upload after every policy change.
- Log administrative changes. Record which account, path and mode were changed so a future error can be traced without broadening permissions again.
When you do not have administrator access
Changing -R, ownership, parent-directory traversal or -U masks requires control of the Pure-FTPd service or the filesystem. If you administer only an FTP account, you can verify the visible path, test a file you own and provide the exact server response to the hosting administrator, but you cannot safely repair a daemon policy or another account’s ownership from the FTP session alone.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Ask the administrator to check the effective Pure-FTPd options, the Unix owner and group, every parent directory’s execute bit, and the creation masks for future uploads. Supplying the filename, timestamp and FTP response is more useful than requesting a blanket permission change.
Quick Recap
Final checklist
- Is
-Rdisabling SITE CHMOD? - Does the FTP login map to the Unix account you expect?
- Are you addressing the correct chroot-relative path?
- Does that account own the target or have an explicitly designed group-based access path?
- Can it traverse every parent directory?
- Are you repairing an existing object rather than trying to change future-upload defaults?
- Do
-Umasks produce the intended modes on a new test upload? - Does a shared writable directory need the sticky bit?
- Are you leaving the home-directory safety boundary intact?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
