Can't Open File to Read on Amazon Lightsail - nginx

I have an Amazon Lightsail Nginx server installation and am attempting to read from a JSON file on the server.
File permissions are set to 777 and I set my owner to bitnami:daemon but am still unable to read the file. I will need to write to it as well. What are the correct permissions/ownership that needs to be set to read/write files on Lightsail?

The correct permissions required are bitnami:daemon on the web folder as well as any affected children items.

Related

Couldn't setup an existing drupal site on local server

imported database, copied drupal site files to wamp/www folder, changed database configuration files, but got "Drupal already installed" error.
Tried by increasing packet size on mysql configuration file.While trying with an empty database , through the setup steps, site being installed. Is there any solution to use the existing database
Drupal version:8.9.20
Php: 7.4.26
apache: 2.4.51
mysql:5.7.36
This message can happen for several different reasons, so here is a start to help you trouble shoot:
MySQL max_allowed_packet, innodb_buffer_pool_size, innodb_lock_wait_timeout
Adding this to verify that this is the packet setting you updated in my.ini
Try updating the innodb_buffer_pool_size & innodb_lock_wait_timeout settings as well
Be sure to restart MySQL after the update is made
drupal.org source
Verify Permissions settings.local.php & MySQL DB user
Make sure the file permissions on your /sites/default/ folder is correct, and settings.local.php file (or whichever settings file you are using)
Make sure the DB user you have configured in the settings file has the correct permissions to the DB as well
Check log files
Check all log files in your WAMP log folder to see if there is any additional information

Chmod specific directories using Phing FtpDeploy task

I've recently setup a Phing build step to deploy a Wordpress website to an external FTP server.
The actual transfer works fine, but I'm trying to figure out a way to set the permissions on the uploads directory to allow users to upload files.
I notice on the FtpDeploy task in Phing that you can specify dirmode, but that seems to set permissions for all directories that are being deployed.
Can anybody tell me if it's possible to set the directory permissions and upload in a single step (task) or would I have to either do 2 FtpDeploy tasks (one for the bulk of the Wordpress site and a second for the uploads directory alone with the required permissions) or perform an ssh chmod after the deploy task.
If I have to do it in 2 stages, are there any benefits of doing a separate deploy with permissions over the ssh method?
Thanks in advance for any suggestions,
Phil
You set the permissions correctly on your local system, and use the dirmode="inherit" attribute.

Media won't upload on Wordpress via EC2 instance

I have install Wordpress have it all working on an EC2 instance and RDS.
One small problem I am having is uploading images through the media/image uploader on the wp-admin it keeps saying the following:
'“FC1.jpeg” has failed to upload due to an error
The uploaded file could not be moved to /var/www/html/wp-content/uploads/2012/06.'
I think it's most likely the permissions of the folder, because I used it yesterday and it worked, but after i sort of messed around with the chmod command on ssh.
I know the wp-content folder should be 775 and I have tried that but it doesn't work.
Any help?
Thanks
The permissions you used gave full privileges to the owner so they should work. Check to see who the owner and group are (ls -l on a *nix system).
You will need to know the webserver user and group. Check with your sysadmin (or in /etc/passwd). On *nix systems it is often ww-data or apache.
The owner and group should be set to the webserver. If they are not, run sudo chown webserverUser:webserverGroup.

Unable to upload themes to my WordPress installation

I am unable to upload themes to my WordPress installation via WordPress admin. I am getting the following error:
The uploaded file could not be moved to /home/debiprasad/webapps/wordpress/wp-content/uploads/2011/09
The permission of wp-contents directory and all sub directories are: 0755. Some people may suggest to make it 0777. This may work, but I don't think this is the correct solution. Because, all the folders should be have permission 0755 and this is secure. 0755 is the default and it works in other installations.
I want to know what's the reason of this error and what is the perfect and secure solution?
Assuming you use Apache, is your uploads folder owned by www-data? (or whatever user apache/php run as?)
If you have access to change ownership, 0755 should work as long as the upload folder (and subdirectories within) are owned by the same "user" that the web server runs as - so in most cases, that'll be www-data.
If this doesn't work, what method do you use to install themes? ftp, ftps or ssh2?

Files reappearing on server even after getting deleted

I am deleting files (wordpress theme files )of my website to the server using cPanel, but still the files are reappearing. The files have a 000 permissions set.
It is strange that files have proper permissions ( i.e. 777) when they are on my local machine, but on uploading they are getting changed to 000. Do you think the site is infected by virus ? I run an Anti-Virus scan, and found none.
Any reason why this may be happening?
chmod 000 denies read, write, and execute permission to yourself, your group, and everyone else.
How are the files uploaded to the server? Your FTP program might me screwing up the files when they are uploaded.
If you have root access you should be able to remove using $ rm -rf filename
Edit
The Umask settings on your server are not right. Setting Umask to 777 will make permissions 000.
If you have shell access you can check for 777 Umask values by running: grep 'umask 777' /etc/skel/.bashrc
If you find anything change the Umask to 022. If you don't have shell access your host should be able to fix this for you.
Instead of using the cpanel uploader use a an FTP program like Transmit for Mac or Core FTP Pro for windows and make sure to always use SFTP which is encrypted instead of FTP.
If you have the option, use FTP to manage your server files. It's more reliable than any web-based client.
If not, try changing permissions through cPanel to 777 before deleting them. If you are unable to do that, then contact the server administrator to resolve the issue (since it looks like a server/cpanel misconfiguraiton).
This is caused by the server recreating folders because you have subdomains or email addresses still attached to the domains related to those folders. Delete the subdomains and emails related to them and those folders will stay deleted.Happened to me before :)
Tim
backup other files in folder then delete folder.
create new folder with previous folder name (that was you deleted) and copy backuped files to it.
This may just work for other users who don't know how to do the techies, or who don't have shell access:
Check to see whether what you want to delete is a FOLDER or a FILE
If it is a FOLDER, check the permissions on that FOLDER and change to 755, do the same if it a FILE and simply delete
The issue here is that you have to open the FOLDER and CHANGE ALL SUBFOLDERS and FILES inside it to permission settings 755.
Delete the files from the inside of the SUBFOLDERS out then to the FOLDERS
This should perhaps help someone.

Resources