wrknight

Here’s the situation. 2FA was activated about a year ago and I have been using the Google Authenticator app on my cell phone to log in successfully since that time. However, I purchased a new cell phone and installed the Google Authenticator app on it only to find out that it won’t work because it has to scan the QR Code which is not available.

I deactivated all other plugins with no effect.

There is no step 1 under Login > Two Factor Authentication. 2FA is shown to be active. My only option is to deactivate it.

After solving the FTP problem I installed the Display Posts widget which is currently at the bottom of the widget area and is displaying 10 posts. But like the Recent Posts above, it’s not doing what I want. What I really want is a block about 4 inches long that contains a list of all my blog posts (about 60) that you can scroll through. If I could modify the Recent Posts widget, by renaming it to Posts, increasing the number to include all posts on the site, limiting the size and adding a scroll bar to browse through all the titles, that would be terrific.

Alternatively, if I could style the Display Posts to do the same (sans bullets), that would work as well.

I haven’t solved the first problem, but the FTP access problem was solved by adding

define( ‘FS_METHOD’, ‘direct’ );

to sp-config.php.

I have run into another problem.

“Failed to connect to FTP Server musingsofamaverick.org:21”

I can’t install plugins, update or download themes as I don’t don’t have a username or password that works with FTP.

As background info, I migrated my website to new hardware, operating system (Ubuntu 20.04) latest versions of all LEMP stack software and wordpress. The site is up and running, but now requires FTP access to do anything and I don’t have that access.

The previous build did not have this problem.

• This reply was modified 3 years, 12 months ago by wrknight.
• This reply was modified 3 years, 12 months ago by wrknight. Reason: Related problem

RESOLVED

In addition to the configuration files shown above, it is also necessary to increase the file sizes in the nginx server block for the site by changing the default setting:

client_max_body_size 2M

to a larger value. For my site I changed it to

client_max_body_size 200M

and now all files upload perfectly, even the updraftplus backup files.

I’m not sure why so many configuration files are involved in what should be a simple modification.

So far I have identified 5 configuration files that can effect limits on uploading files. They are
nginx.conf – in /etc/nginx
php.ini – in /etc/php/7.4/fpm/php.ini
php.ini – in /etc/php/7.4/cli/php.ini (I have no idea why there are 2)
wp-conf.php – in /var/www/wordpress/content
functions.php – in /var/www/wordpress/content/themes/twentyfifteen

In all configuration except nginx.conf files I have set
upload_max_filesize = 200M
post_max_size = 256M
memory_limit = 256M

In nginx, I set
client_max_body_size 200M

Files and images less than 2M load successfully

Uploading image files larger than 2M get error message:
Post-processing of the image failed likely because the server is busy or does not have enough resources. Uploading a smaller image may help. Suggested maximum size is 2500 pixels.

Uploading pdf files larger than 2M sometimes gets error message:
Unexpected response from the server. The file may have been uploaded successfully. Check in the Media Library or reload the page.
and other times gets message:
413 Request Entity Too Large – nginx/1.18.0 (Ubuntu)
Error message is not consistent – but the file doesn’t upload in either case.

More details:
System motherboard: Gibabyte GA Z79X-SLI
System CPU: Intel I5
System memory: 32GB
OS Linux version: Ubuntu 20.04 (Mate desktop environment)
Nginx version: 1.18.0 (Ubuntu)
Mariadb version: 15.1 Distrib 10.3.22-MariaDB, for debian-linux-gnu (x86_64)
PHP-FPM version: 7.4
Wordpress version: 5.5.1

What am I doing wrong?

Yes, you are right, but your answer doesn’t help. I own my own host and am not using a commercial hosting service for this site. There is no cPanel and I don’t use ftp for uploading as everything is controlled from the console attached directly to my computer.

I can set my server to anything I want and have set the file upload limit to 200M in every configuration file I am aware of (see above) and cannot find where the 2M restriction is hiding.

Problem solved. Incorrect premissions set on wordpress files. Corrected problem with

sudo chown -R www-data:username <path>wordpress
sudo chmod -R 755 <path>wordpress

Problem disappeared.

• This reply was modified 4 years, 1 month ago by wrknight.

Subsequent to this, I attempted to set up an error log by setting

define( ‘WP_DEBUG’, true ); and
define( ‘WP_DEBUG_LOG’, true );

and there appears to be no wordpress error log in my system.

So how am I suppose to debug these installation problems?

I am still at a loss.

Being a WordPress blog with the 2015 theme, a template is used to display the home page and each of the blog posts. The theme header file is the only place that I know of to place the recommended text. That file presently contains the following:

<head>
	<meta charset="<?php bloginfo( 'charset' ); ?>">
	<meta name="viewport" content="width=device-width">
	<link rel="profile" href="https://gmpg.org/xfn/11">
	<link rel="pingback" href="<?php echo esc_url( get_bloginfo( 'pingback_url' ) ); ?>">
	<!--[if lt IE 9]>
	<script src="<?php echo esc_url( get_template_directory_uri() ); ?>/js/html5.js"></script>
	<![endif]-->
	<?php wp_head(); ?>
</head>

The code I am advised to add is:

 <meta property="og:title" content="Example Page">
<meta property="og:image" content="https://example.com/images/image.jpg">
<meta property="og:description" content="This is just an example page.">
<meta property="og:url" content="https://example.com/page.html">
<meta name="twitter:card" content="summary_large_image">

At this point, I don’t see how I can put in a fixed title, image, description or url as those should vary depending on the page (post) the viewer is linking to.

This worked perfectly for me also. Many, many thanks.

I might add that I was somewhat confused about where to put this function.php file or whether to include it in one of the many existing function.php files in the wordpress directory. I ended up adding the function at the end of the function.php file located in the /themes/twentyfifteen/ directory that contains functions for the theme that I use for my website. I suspect this will no longer work if I change themes and I have no idea where to put it to make it universally applicable.

Here’s another piece of information.
when I attempt to get to wordpress dmesg gives the following:

[Wed Jul 24 19:19:50 2019] [UFW BLOCK] IN=enp4s0 OUT= MAC=01:00:5e:00:00:01:20:c0:47:13:01:15:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=56518 DF PROTO=2

Something similar happened to me awhile back and it turned out that my system clock had been set back to zulu time and therefore the encryption failed and the access was blocked.

At some point in this installation, the system clock was set back to zulu time again. I’ve been told mysql, php and certbot all maintain clocks and I’m wondering if they could be out of synch. But I have no idea how to check each of them.

For me, this started a few weeks ago. My workaround consists of deactivating the email subscribers & newsletters plugin, reactivating it only when posting a new blog and then deactivating it immediately afterwards. So it is open for 2 to 3 minutes max during which the post notice goes out and at most only one bot mail enters.

Unfortunately, this workaround disallows new subscription requests. To handle those, I added a text widget that tells interested people to send me an email requesting that I add them to the subscribers’ list which I do manually. It’s not good, but so far it has worked OK.

I am still looking for a better way to solve this problem and I hope the developers come up with one soon.

Rosemond, This thread indicates that your issue with receiving emails is resolved. I have the same issue, but the three answers above only apply to SMTP configuration. SMTP is a SEND MAIL protocol and does not apply to receiving email. Standard email receive protocols are POP3 and IMAP, so the answers above don’t help. If your problem is truly resolved, please email the solution to me at [email protected].

wrknight