Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

How to fix FTP permission denied errors on Google Cloud

by | May 19, 2021

Don’t know how to fix FTP permission denied errors on Google Cloud? We can help you.

We may receive “Permission denied” errors while trying to edit Google Cloud Platform files via FTP.

As part of our Google Cloud Platform Services, we assist our customers with several Google Cloud queries.

Today, let us see how to fix errors while trying to save and upload changes to Google Cloud Platform files that we have downloaded and edited over FTP.

 

How to fix FTP permission denied errors on Google Cloud

In order to begin, our Support Techs suggest configuring an FTP client to work with the website on Google Cloud Platform.

There are different steps to fix “Permission denied” errors.

  • Identify Error

Suppose, we attempt to save changes to the website’s wordpress.conf file via FTP.

However, if we do not have the required permissions to save changes to wordpress.conf file, the FTP console will show:

How to fix FTP permission denied errors on Google Cloud

  • Connect to VM Instance

In order to fix the problem, we need to edit the file’s permissions in Google Cloud Platform. To do so, we need to connect to the VM instance via an SSH terminal.

  1. Initially, we go to the Google Cloud homepage, click the hamburger menu in the upper left-hand corner.
  2. Go to our Compute Engine, then to VM instances.
  3. Then we click on the SSH button to connect to our website via SSH.
  • Check File Permissions

Once we connect to the website via SSH, we need to check the permissions of the file we wish to edit.

For example, suppose the user is checking the permissions of wordpress.conf file.

In such a case, we execute:

stat -c “%a %n” /path/to/file
stat -c “%a %n”“ /etc/apache2/sites-available/wordpress.conf

This is to check the permissions of wordpress.conf file. If the permission of the file is 644, it will show as output.

  • Edit File Permissions

Since the file’s permission is 644, we may not have sufficient permissions to edit the file via FTP.

To fix this, we change the file’s permissions from 644 to 777, thereby granting all permissions:

sudo chmod 777 /path/to/file
sudo chmod 777 /etc/apache2/sites-available/wordpress.conf

We execute this command to change the permissions of wordpress.conf file from 644 to 777.

  • Restart Apache

We need to restart our Apache server for these changes to reflect.

$ sudo service apache2 graceful
[ OK ] Reloading web server: apache2

For most Apache configurations, the above command is to restart the Apache server.

However, for Bitnami Apache configurations, we run:

$ sudo /opt/bitnami/ctlscript.sh restart apache
  • Retry File Upload

Then we go back to our FTP Client and retry to upload the saved file.

Since the file has the permission of 777, we will be able to upload it to our server successfully via FTP.

However, this permission means that it is readable, writable, and executable by all users. Thus may pose a huge security risk.

So, after uploading the file, we change the permissions back to 644.

[Need help with the upload? We’d be happy to assist you]

 

Conclusion

In short, with chmod 777, we should be able to avoid Permission denied errors when uploading files via FTP.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF