I have a WordPress Multisite running on a relatively new Amazon Web Services (AWS) Lightsail instance, based on a Bitnami image (provided through AWS Lightsail) running a LAMP stack, based on Debian.
Until recently, plugins installed through the WordPress multisite Administrator Dashboard installed and ran good. Worked great before, no problems. Now, for some reason, attempting to install any WordPress plugin surfaces a dialog requiring FTP credentials be provided. There's a screenshot of the WordPress multisite dialog asking for FTP credentials at the end of this message.
I'm thinking this - new - demand to provide FTP credentials when adding a WordPress plugin is happening due to permissions. Naturally, I'd rather not need to install WordPress plugins using FTP.
So, I have two questions:
What settings were accidentally - somehow - changed to cause WordPress to now produce this new requirement asking for FTP credentials when installing any WordPress plugin?
How to I fix WordPress so that plugins can be installed without FTP?
I did see many solutions for fixing permissions on the Internet, except since I'm new to AWS, Linux (Debian) & WordPress I'd like to use this opportunity to learn how this situation happened, while learning how to fix the hiccup. Other than using a few new plugins, which installed & ran fine without FTP, I have not made any edits to any internal WordPress files.
The only chance to change permissions might - maybe - have happened when setting-up users within my AWS account, including setting-up of a Yubico key with key-pairs --> I don't think that security change would influence the LAMP stack running the WordPress multisite, but I wanted to offer information that might - maybe - related to security changes influencing why, now, adding WordPress plugins requests FTP credentials.
Thanks in advance, everybody. Thank you. :)
WordPress multisite dialog asking for FTP credentials
I tried to add many, many WordPress plugins to confirm that every WordPress plugin now asks for FTP credentials for any new plugin.
I have looked at many Internet posts explaining how to change WordPress & Linux permissions, along with posts explaining how to change WordPress configuration files to not ask for FTP when installing new plugins. I have not acted on these many suggestions since I'm cautious & careful --> I'm ready to study months & months becoming a Linux, WordPress, and supporting technologies expert, but at this stage since I'm new to all-of-the-above, I'm reluctant to make any changes until I fully understand the technologies (after making this post, I will make copies of WordPress configuration-files to test changes that can be undone, but I wanted to see whether StackOverflow might help me learn what happened in the first place, while learning how to correctly fix these issues.
I pay for AWS Premium Support --> I've sent a message to AWS Premium Support, but so far have not heard back from AWS.
Related
I hired a developer to stand up my website. I had already created a WordPress install on AWS lightsail. The developer says he needs cpanel in order to finish the work (header/footer code, configuration etc...). I was hoping to do this as cheaply as possible and it seems like cpanel would add $15 a month. Is it really needed? Any alternatives?
Looked at AWS docs on alternatives but didn't find anything.
cPanel is a hosting control panel to manage a website and server. It seems that you have already hosted and configured your server without cPanel. For developers, they should be able to manage and customize your website using FTP and WordPress admin details and it does not require from Development point of view.
Even if you are planning to add cPanel to your server, you will have to reinstall your server from scratch because cPanel requires a fresh server without any software, data or website.
I have a live newspaper WordPress website with about 10 users updating it daily with about 2000+ unique visitors a day. I have a sum of about 30 posts a day added to my db and i host my own pictures.
My goal is to change my theme that has been used for over 4 years so smoothly that I don't experience much hiccup for my viewers.
I want a dev environment somewhere in my server that I can test my new theme with my current posts.
A solution I have in my head is to create a subdomain for example "dev.example.com" and deploy the new theme there and have two working wordpress themes with one database.
Is this even possible? I need to have my new theme that is in a dev environment have access to my live database.
What is the best practice for this situation?
for people looking into this like me, I will post my findings below and if you like you can comment to guide me or tell me what I'm doing wrong or right.
there is a wp-staging plugin that can be used but it seems to be paid if you want to push changes from staging version to production version of your website.
I have also figured out that another wp website can be installed on a subdomain that you can create through cpanel and install a brand new wordpress environment that is completely separate from your live site with its own db and config.
Since most of us don't have unlimited server resources its going to be pretty heavy to clone everything from live site to staging site and I figured they cant share a db because changes made to staging site can effect live site if they share a database.
So I looked over a very well summarized easy youtube video which basically explained the whole process for cloning your wordpress on your subdomain and using a new db, but this solution can be good if you have the server space and resources, for a website like mine i would guess that a local installation of wordpress would work.
One of the comments on that video was very usefull as well:
Just create a subdomain, install WordPress with Softaculous on the subdomain, install the All In One WP Migration Plugin on both the main site and the subdomain, export the file in All In One WP Migration on the main site and import it to the subdomain and vice versa, you have your staging.
As you can see from the image above. I am experiencing some sort of error message but i have no idea what it means.
I am using wordpress 4.1 with a default theme. Every time i tried to add a menu to the menu structure i get the following message:
Gateway Anti-Virus Alert
This request is blocked by the Firewall Gateway Anti-Virus
Service. Name: Mailer.S (Trojan)
Things that i have already tried:
Using different theme
Installing and re-installing wordpress
Delete everything and start from beginning
And none of this work!
Please help me.
Thank you
You probably got infected with malware, and a service running on your hosting is blocking some malicious code. At best you can contact your hosting provider and ask them how to resolve. Malware on a WordPress site is pretty common by using outdated plugins, themes or having insecure rights on folders and files.
It's pretty hard to get rid of, you have to search trough every file to check for malicious code and check every folder for files that shouldn't be there.
Goal: We have a Magento installation which contains a lot of sensitive data. We're looking to host a Wordpress installation.
Problem: Since we're installing third-party modules on Wordpress, we don't want any security issues in Wordpress to be able to compromise Magento.
I've spoken to a couple of my friends, and also had a think back to how it's been implemented in the past, but I wanted another opinion.
Since the wordpress directory will reside inside of the magento directory, would it be sufficient to chown the files inside of wordpress to a new user ("user-wp"), and then to chroot the user-wp user to the wordpress directory? Magento would then still have access to all of the Wordpress files, but not vice-versa.
Any other suggestions on how to go about implementing this would be more than appreciated! Somebody also suggested configuring a separate vhost.
Using a subdomain like blog.site.com would probably be the easiest way to set this up. All you would have to do is add a new VHost for the WordPress installation.
I don't think Chrooting would provide much security. You may also run into WordPress Plugin issues with such a configuration.
The setup is tricky. You would have to go and modify the PHP-fpm process pool and users it runs with. Then assign one pool to Magento and another to WordPress. Additionally you will also want to serve static assets & uploads from the Webserver itself.
And when you change this config you have to retest your Magento install to make sure things you didn't break anything accidentally.
Too much hassle, just use the subdomain. :)
I'm working on a project on my localhost for sometime now, and i've recently tried to make it online. My project works perfectly on my localhost, and I can post new articles to wordpress blogs with no problem.
The problem is, after uploading my project to a online web server ( Hostgators Baby Plan ) , I tried to add a new post to one of my wordpress blogs and I got the following error :
faultCode 500 faultString You are not allowed to do that.
The thing is, I've searched everywhere in the past few days in-order to solve this problem and had no luck.
Do you guys think this problem is caused because i'm using a webserver and not a VPS? If you have any other solutions I'll be glad to hear them out.
It might be related to file permissions or something like that.
There is no need to use VPS. I manage my website on a shared server and I've tested WordPress on free hosting services too.
This is probably due to incorrect permissions either on the file structure or the mySQL DB user or something like that. Take a look at this article on the WP codex about file permissions.
Big services like Hostgater usually have an "auto-install" feature for common software like Wordpress (via Softaculous or something similar). I don't know how you migrated your site from your local version to the server but it may be worth installing a fresh Wordpress instance through Hostgator and then simply loading in the wp-content folder and your development database on top of that.