I just recently installed a one click application from the Google Cloud Platform. I installed WordPress as a VM instance , but when I try to access my VM instance via ssh i see that its empty and it doesn't contain any WordPress files. Is there a way to access the WordPress files either via FTP or even better ssh?
One click deployments should come with everything you need “out of the box”.
You can visit your Deployment Manager and click on the Word Press resource to view login options and choose SSH or login to the Word Press admin console from there.
Accessing files through SCP can be done through the GCloud command line as well as another alternative.
Related
How can I change permission for a Web App, so I can actually upload files via FTP to it?
What is it I need to change in order to have permissions to upload via FTP?
I have a running site that runs ASP.Net Core. Everything works.
For debugging purposes on a weird js issue, I need to be able to edit a few js files directly on the site via FTP.
When I connect via FTP (with the credentials from the "publish profile") I can connect just fine and download files - I use Filezilla.
But if I try to upload anything, I get "550 Access is denied."
I have full access to Azure Portal etc for the site, incl. Kudu.
It does not matter if you can upload files via KUDU or some other thing - I specifically need FTP.
Thanks for asking question! Could you please check if your firewall is blocked outgoing FTP writes.
Also, make sure you're not trying to write to a read-only file. For this suggest using the Kudu Console (https://[sitename].scm.azurewebsites.net/DebugConsole) to look at your files and check their permissions (e.g. using 'attrib' command).
For more information about KUDU, please refer to this document
Refer to this document link might be helpful: https://learn.microsoft.com/en-us/azure/app-service/deploy-ftp#get-ftp-connection-information
Try checking the ftp link which is provided by deployment center, For this Go to your web app, click Get publish profile, choose the Publish URL under tag <publishProfile profileName="your-webapp"
I have a WordPress instance running locally on my mac with XAMPP.
It's working fine but when I want to install something I have to login with my ftp username and password.
I've tried to use my username and password which I use to logon to WordPress. Also I used my tried my database credentials. I really have no idea which other logon credentials I should have.
FTP credentials do not refer to your login details, it refers to credentials for File Transfer Protocol, it is given to you when you purchase a web hosting service or setup one yourself on your machine.
An alternative to this would be to download the plugin or theme you want and paste it to your /{website folder}/wp-content/themes or /{website folder}/wp-content/plugins
Try to
Right click to htdocs folder, choose Get info
Click the lock icon, type your MacOS account password to unlock below options.
Allow everyone Read & Write permission, the click the cog icon and choose Apply to enclosed items..., this should apply all r+w permission to sub-folders.
Done
I have a bitnami WordPress instance using AWS lightsail. I need to migrate the site to another identical AWS instance. I created a PHP installer from the first instance using the Wordpress Duplicator plugin.
I then uploaded the file onto the new server to a folder (opt/bitnami/apache2/htdocs/).The instructions I've seen online they say I just need to navigate to the location of the installer in a browser and it will run. However, when I attempt to access the PHP file from a browser I just get an error on the front-end saying:
OOPS! THAT PAGE CAN’T BE FOUND
I have seen suggestions online that the installer be placed into a public folder called html_public but my instance doesn't have a folder like that. I changed the access rights to the folder, and the installer, to be full rw access.
Any ideas how I can get this to work?
You must config the Security Groups firewall to open the HTTP port.
Open the Amazon VPC console at [https://console.aws.amazon.com/vpc/]
On the Inbound Rules tab, choose Edit the port range 80, 443 - Source: Anywhere - IP Address: 0.0.0.0/0 and Save.
I'm pretty new to using amazon web services. I created a new launch instance using WordPress powered by Bitnami and made sure to create a key pair. The key pair I made shows up under the "Key Pair" category however it is not linked to my launch instance. How do I fix this without losing any of the content that's on my current Wordpress site? I want to access the instance through my terminal, however I need the key pair for authentication. Thank you!
It appears that your situation is:
Your EC2 instance with WordPress is operating fine
You did not associate a Keypair with the instance when it was first launched
Therefore you cannot login to the instance
To fix this, you will need to copy a keypair onto the boot volume. This can be done by accessing it via another computer (where you can login).
The basic steps are:
Launch another EC2 instance ("Debug instance")
Stop your WordPress instance
Detach the boot volume of the WordPress instance ("WordPress volume")
Attach the WordPress volume to the Debug instance
Login to the Debug instance, access the WordPress volume and copy a new keypair to /home/ec2-user/.ssh/authorized_keys (If you're not sure what to copy, copy the file from the same location in the Debug instance.)
Unmount and detach the WordPress volume from the Debug instance
Attach the WordPress volume to the WordPress Instance (as /dev/xvda)
Boot the WordPress volume and try to login
Terminate the Debug instance
A similar concept is documented here:
How to Recover an Unreachable Linux Instance
Lost my key with linux authorized_Keys. Now unable to login into the linux
I was wondering if there was a way to customize the nano editor settings in the Debian-based virtual machine instance when you launch the cloud shell.
I already tried going to the root of the instance then cd to etc and editing the nanorc file. but every time i try re-save the nanorc back it says permission denied.
Thanks.
You should be able to customize your nano editor settings by creating $HOME/.nanorc file. While Google Cloud Shell virtual machines are ephemeral (the VM is turned down when idle and a new one is allocated when you are back), the content of your home disk is persistent.