I’m on Windows client and I’m just starting to use FileZilla to SFTP local files on a remote server .. an Amazon EC2 instance running Ubuntu.
On my windows client I have Putty Pageant running as source of public keys.
Now the problem I’m having must be very basic .. «permission denied» leading to failed transfers
Error: /usr/lib/nx/nxsetup: open for write: permission denied
Error: File transfer failed
I right click the target server directory to check read/write permissionbs.
The directories in both source (localhost) and target (EC2 instance) can be navigated by FileZilla.
I tried to set attributes read/write for the entire target folder
but I get this ..
Status: Set permissions of ‘/usr/lib/nx’ to ‘777’
Command: cd «/usr/lib»
Response: New directory is: «/usr/lib»
Command: chmod 777 «nx»
Error: set attrs for /usr/lib/nx: permission denied
I have tried going to target server to change permissions of target folder /usr/lib/nx
sudo chmd +w /usr/lib/nx/
Also I’ve tried WinSCP but get identical errors ..
Cannot create remote file ‘/usr/lib/nx/nxsetup’
Permission denied
Error code: 3
————————————-
What is the basic configuration I’m missing just to transfer files from A to B using SFTP?
I’ve tried running FileZilla in administrator mode.
Is this probably a problem of permissions at the server end (Ubuntu) rather than in FileZilla?
————————————-
Here is a copy of the log file .. (EC2 path edited)
2011-11-14 21:00:53 3056 3 Status: Connecting to ec2-xx-xxx-xx-xxx.eu-west-1.compute.amazonaws.com…
2011-11-14 21:00:53 3056 3 Response: fzSftp started
2011-11-14 21:00:53 3056 3 Command: open «ubuntu@ec2-xx-xxx-xx-xxx.eu-west-1.compute.amazonaws.com» 22
2011-11-14 21:00:54 3056 3 Status: Connected to ec2-xx-xxx-xx-xxx.eu-west-1.compute.amazonaws.com
2011-11-14 21:00:54 3056 3 Status: Retrieving directory listing…
2011-11-14 21:00:54 3056 3 Command: pwd
2011-11-14 21:00:54 3056 3 Response: Current directory is: «/home/ubuntu»
2011-11-14 21:00:54 3056 3 Command: ls
2011-11-14 21:00:54 3056 3 Status: Listing directory /home/ubuntu
2011-11-14 21:00:54 3056 3 Status: Calculating timezone offset of server…
2011-11-14 21:00:54 3056 3 Command: mtime «.bashrc»
2011-11-14 21:00:54 3056 3 Response: 1317454718
2011-11-14 21:00:54 3056 3 Status: Timezone offsets: Server: 0 seconds. Local: 0 seconds. Difference: 0 seconds.
2011-11-14 21:00:54 3056 3 Status: Directory listing successful
-
mephistop
- Posts: 2
- Joined: Sat Aug 29, 2015 4:13 pm
Permission denied
Добрый день,
Через ftp открываю файл php.ini редактирую то что нужно , но когда заливаю обратно на сервер пишет:
Ошибка: /etc/php.ini: open for write: permission denied
Ошибка: Передача файла потерпела неудачу
Через SSH тоже зашел через root, вбил команду /etc/php.ini в ответ пишет это:
-bash: /etc/php.ini: Permission denied
Как решить проблему? Откуда нужно подправить права?
CentOS 6
Vesta
Спасибо.
-
Alex Connor
- Support team
- Posts: 1047
- Joined: Fri Mar 21, 2014 7:49 am
- Contact:
- Os: CentOS 6x
- Web: apache + nginx
Re: Permission denied
Post
by Alex Connor » Sat Aug 29, 2015 8:04 pm
используйте sftp подключение дя пользователя root, либо
-
mephistop
- Posts: 2
- Joined: Sat Aug 29, 2015 4:13 pm
Re: Permission denied
Post
by mephistop » Sat Aug 29, 2015 8:31 pm
Alex Connor wrote:используйте sftp подключение дя пользователя root, либо
Большое спасибо. Через SSH сделал.
-
Alex Connor
- Support team
- Posts: 1047
- Joined: Fri Mar 21, 2014 7:49 am
- Contact:
- Os: CentOS 6x
- Web: apache + nginx
Re: Permission denied
Post
by Alex Connor » Sat Aug 29, 2015 8:48 pm
Обращайтесь 😉
I have created a user and a group only for SFTP and when I try to transfer a file with Filezilla in /var/www I have this error:
Open for write: permission denied
I have configured sshd_config like this :
#Subsystem Sftp /usr/libexec/openssh/sftp-server
Subsystem sftp internal-sftp
Group sftp_only Match
ChrootDirectory /var/www
ForceCommand internal-sftp
X11Forwarding No
AllowTcpForwarding No
/var/www and sub directories are chown root:root and chmod 755
SELinux is disabled.
Any idea ?
![]()
masegaloeh
18.1k10 gold badges56 silver badges105 bronze badges
asked Mar 3, 2015 at 16:08
1
The permission of /var/www does not permit the chrooted-user to create files in it.
That is correct and by design.
You must create a folder inside of /var/www with the proper rights of the user.
/var/www can not be writeable for the user.
answered Mar 3, 2015 at 16:20
fakerfaker
17.4k2 gold badges61 silver badges69 bronze badges
Best Ways to Fix Permission Denied in Word Press When Uploading a File Using Filezilla Or Any Other FTP Client

How to fix the Permission denied error in Word Press When Uploading a File Using Filezilla Ftp or any other FTP client,
Fix Open to Write: Permission denied in WordPress using LEMP or LAMP (Nginx or Apache servers).
It can be so frustrating whenever you try to upload files via FTP and only to get the annoying message that says open write: permission denied.
Filezilla is an easy-to-use file transfer protocol that makes it easy for you to access your files and folders within minutes
other than using the CLI (Command Line Interface).
The Write: Permission denied or permission denied message you get whenever you try to upload files to your server(s)
is a sign that you don’t have the correct user permissions assigned to your user account.
In most cases, you face these issues when you try to do things like creating a folder, uploading files, or even deleting items.
Prosthetic-Tailed Dolphin Winter Dies at 16

If there is the case for you, then this article will be walking you through the steps on how to fix the Write: Permission
denied in WordPress using LEMP or LAMP (Nginx or Apache servers).
It is good to know that your WordPress site is been hosted on a computer usually referred to as a server by a hosting company.
These server uses special software usually Nginx or Apache to manage your files and serve them to browsers.
At this point folder and file, permissions tell the server who can read, write, or modify available files hosted under your account.
These are because WordPress requires permission to be able to read, write or modify files.
Using incorrect permissions can restrict WordPress the ability to create folders, upload media items, images, and more.
Installing Multiple Bootable Operating Systems on a USB Stick Can Be Easier Than You Think
When encountered with such problems, in most cases, WordPress will try to inform you that it is unable to edit a file,
create a folder, or cannot write to disk.
However, in some cases, you may not see any proper error messages describing the issue.
What is the correct File Permission for WordPress?
If your file and folder permission is correctly set, then it already has the numbers below in place else they may look something different:
755 or 777 for all folders and sub-folders.
644 for all files.
How to Download Microsoft Word for Free
These allow WordPress to create files and folders.
Fixing File Permission in WordPress Using FTP (In our case we will be using Filezilla)
First, you will need to connect to your WordPress site server using Filezilla or any other FTP client suitable for you. You can download Filezilla here.
Once you are connected, locate the root folder of your WordPress site
After that select all folders in the root directory and then right-click to select File Permissions.

How to Upgrade to Windows 11 for Free
After this action, a dialog box will pop up on your screen, kindly enter the correct figures 777 in the Numeric field provided.
Once this is done, go ahead and click on ‘Recurse into subdirectories’ click the checkbox and then select the ‘Apply to directories only’ option.

Now click on the OK button. At this point, your FTP Clint will begin setting file permissions to your folders and sub-folders.
This process will take some minutes or even more if you have a slow network so you will have to be patient a bit, wait for the process to complete.
After the above process completes, select all files and folders in the root folder of your site, right-click to select file permissions just like we did before.

But this time, when the dialog box appears, enter 644 in numeric value and click the OK button.

Your Ftp Client will now begin to set file permission for your WordPress site.
In case the above option did not work for you, then try the next option below that worked like magic for me.
Of course, that is why I have to make these posts should in case the above method does not do the trick for you, then the next step is for sure.
Though you will be needing a little knowledge working with the Command Line Interface (CLI). This article will not cover how to use the CLI.
Git is a good CLI tool, if you already have it installed login using ssh e.g. ssh username@127.0. 0.1 substitute the username for your own username and the IP address for your own IP address.
You will be asked to enter your password do so and hit the enter key.

SpaceX’s Crew-3 mission to the International Space Station What You Should Know
Once you are logged in to your account with Sudo privileges you will need to add your user “username” to the group www-data (since www-data is a group)
To add user “username” to group “www-data” follow the steps below remember to replace username with your own username.
sudo usermod -a -G www-data username
Then set permissions for user group www-data
sudo chgrp -R www-data /var/www/html
Followed by
sudo chmod -R g+w /var/www/html
Now you can read, write, and modify files as “username” via SFTP and your WordPress installation can modify files without requesting credentials
Hope this was helpful please leave your comments below.
Like us on Facebook
Business News
Cars
Computers
Crypto
Finance News
Gadgets
Games
Jobs Application
Reviews
Scince
Social Media
Softwares
TECH
Technology News
Tips
Windows
World Research