extremeleadprogramcom

I use the plugin with PHP 8.1.27 and have no issues like that at all.

Got it, installed it, and this does appear to indeed fix the issue, thanks.

Done, I’ll give this a try, thanks.

Rolling back to V2.5.9.3 does NOT fix the issue.

Looking at my logs, here is everything else I updated when I upgraded:

WordPress 6.3 – 6.3.1
All in One SEO 4.4.4 – 4.4.5.1
AutomateWoo 6.0.2 – 6.0.3
Kadence Blocks – PRO Extension 2.0.11 – 2.0.12
Post SMTP 2.5.9.3 – 2.5.9.4
Spectra 2.7.6 – 2.7.7
WooCommerce 8.0.2 – 8.0.3

After disabling the “All in One SEO” plugin the issue seems to go away so it seems like this would be on their end. I’ll post to them, thanks.

Sure here you go:

Mailer: postsmtp
HostName: xndur02esu-staging.wpdns.site
cURL Version: 7.87.0
OpenSSL Version: OpenSSL/1.1.1p
OS: Linux ash17.onrocket.com 4.18.0-477.13.1.lve.el8.x86_64 #1 SMP Thu Jun 1 16:40:47 EDT 2023 x86_64
PHP: Linux 8.1.22 C.UTF-8
PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=No, zlib_encode=Yes
WordPress: 6.3.1 en_US UTF-8
WordPress Theme: Kadence Child
WordPress Plugins: Advanced Custom Fields, Affiliates Enterprise, Affiliates WooCommerce Integration, All in One SEO, AutomateWoo, Blog2Social: Social Media Auto Post & Scheduler, PublishPress Capabilities, CartFlows Pro, CartFlows, Code Snippets, Custom Order Status for WooCommerce, Yoast Duplicate Post, Enable Media Replace, Head, Footer and Post Injections, Imagify, Itthinx Updates, Kadence Blocks - PRO Extension, Kadence Blocks – Gutenberg Blocks for Page Builder Features, Kadence Cloud, Kadence Custom Fonts, Kadence Pro - Premium addon for the Kadence Theme, Kadence Reading Time, Kadence Starter Templates, Kadence Shop Kit, Metricool, Modern Cart for WooCommerce, Post SMTP, ProveSource, Sticky Block, SupportCandy, Temporary Login Without Password, TrueROAS, Spectra, Ultimate Blocks, UpdraftPlus - Backup/Restore, User Switching, Verfacto, WooCommerce Stripe Gateway, PDF Invoices & Packing Slips for WooCommerce, Sequential Order Numbers for WooCommerce, WooCommerce Subscriptions, WooCommerce, Wordfence Security, SupportCandy - Automatic close tickets, SupportCandy - Canned Reply, SupportCandy - Satisfaction Survey, SupportCandy - WooCommerce
WordPress wp_mail Owner: /home/xnduree/public_html/xndur02esu-staging.wpdns.site/wp-content/plugins/post-smtp/Postman/PostmanWpMailBinder.php
WordPress wp_mail Filter(s): wp_staticize_emoji_for_email, WPO\WC\PDF_Invoices\Main->set_phpmailer_validator, PostsmtpMailer->get_mail_args
WordPress wp_mail_from Filter(s): wordfence::fixWPMailFromAddress
WordPress phpmailer_init Action(s): PostsmtpMailer->phpmailer_smtp_init
Postman: 2.5.9.4
Postman Sender Domain (Envelope|Message): extremeleadprogram.com | extremeleadprogram.com
Postman Prevent Message Sender Override (Email|Name): Yes | Yes
Postman Active Transport: SMTP (smtp:tls:plain://email-smtp.us-east-2.amazonaws.com:587)
Postman Active Transport Status (Ready|Connected): Yes | Yes
Postman Deliveries (Success|Fail): 379334 | 3424
Postman TCP Timeout (Connection|Read): 15 | 60
Postman Email Log (Enabled|Limit|Transcript Size): Yes | 500 | 512
Postman Run Mode: log_only
Postman Stealth Mode: Yes

This is a staging server. There isn’t really any traffic or anything to monitor at all over time.

It only seems to make sense to monitor it while I’m actually doing things in the backend or running a test load?

Is there nothing simple to check in the configs or what I provided that would clue us in to an issue?

This is a bare metal server with no major support so I am on my own for the most part here.

I found some helpful pages searching google… here is a test run with some commands running on the server: https://nimb.ws/H0v3ye

Here is the output of the info command when this is all done:

# Server
redis_version:3.2.12
redis_git_sha1:00000000
redis_git_dirty:0
redis_build_id:7897e7d0e13773f
redis_mode:standalone
os:Linux 3.10.0-1127.13.1.el7.x86_64 x86_64
arch_bits:64
multiplexing_api:epoll
gcc_version:4.8.5
process_id:1373
run_id:2f258f78b586e4d97d42d399704dd01308b8df8a
tcp_port:6379
uptime_in_seconds:2576833
uptime_in_days:29
hz:10
lru_clock:8805063
executable:/usr/bin/redis-server
config_file:/etc/redis.conf

# Clients
connected_clients:1
client_longest_output_list:0
client_biggest_input_buf:0
blocked_clients:0

# Memory
used_memory:4730608
used_memory_human:4.51M
used_memory_rss:10207232
used_memory_rss_human:9.73M
used_memory_peak:223054352
used_memory_peak_human:212.72M
total_system_memory:50465189888
total_system_memory_human:47.00G
used_memory_lua:37888
used_memory_lua_human:37.00K
maxmemory:268435456
maxmemory_human:256.00M
maxmemory_policy:allkeys-lru
mem_fragmentation_ratio:2.16
mem_allocator:jemalloc-3.6.0

# Persistence
loading:0
rdb_changes_since_last_save:141486
rdb_bgsave_in_progress:0
rdb_last_save_time:1650395398
rdb_last_bgsave_status:ok
rdb_last_bgsave_time_sec:-1
rdb_current_bgsave_time_sec:-1
aof_enabled:0
aof_rewrite_in_progress:0
aof_rewrite_scheduled:0
aof_last_rewrite_time_sec:-1
aof_current_rewrite_time_sec:-1
aof_last_bgrewrite_status:ok
aof_last_write_status:ok

# Stats
total_connections_received:6704
total_commands_processed:715918
instantaneous_ops_per_sec:0
total_net_input_bytes:30046973656
total_net_output_bytes:34998383404
instantaneous_input_kbps:0.00
instantaneous_output_kbps:0.00
rejected_connections:0
sync_full:0
sync_partial_ok:0
sync_partial_err:0
expired_keys:443
evicted_keys:0
keyspace_hits:472173
keyspace_misses:74804
pubsub_channels:0
pubsub_patterns:0
latest_fork_usec:0
migrate_cached_sockets:0

# Replication
role:master
connected_slaves:0
master_repl_offset:0
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0

# CPU
used_cpu_sys:1114.31
used_cpu_user:446.39
used_cpu_sys_children:0.00
used_cpu_user_children:0.00

# Cluster
cluster_enabled:0

# Keyspace
db0:keys=3200,expires=199,avg_ttl=346706741

How do I do that?

Afer I let it sit and run through it again here are the metrics: https://nimb.ws/5uAoia

Much slower it seems. These numbers are more indicative of what I noticed previously.

A little background on the server. The Redis server is on the same server as the Apache server. It is a dedicated server on a 24 core, Intel(R) Xeon(R) CPU X5670 @ 2.93GHz with 48GB of Ram.

It’s running ISPconfig and I have a dozen or so low traffic sites and my 1 main mid traffic site. The server typically runs at a very low load.

I am testing this on the staging site on the same server so the only load I can do is just go through the back end several times and show you metrics.

Here is a 5-minute video of me doing just that while including the server stats via the TOP command: https://nimb.ws/XBDtQH

I go to the Redis metrics a couple of times in the video but here is a quick screenshot of those: https://nimb.ws/7QrCWF

Will do that.

I think this may have actually been my mistake when I reset my browser settings…

I put the option back and subscribed a new browser.

I sent a notification but ONLY that new browser got it, the old 2 did not… that means NONE of my original subscribers are getting anything, what happened???

Great and agreed!

Ok, so I just realized that the “test” email returns the error… However, as stated by @unexploded – my normal messages from the site are working just fine.

The same was happening for me in the auto-detect settings as well.

This leads me to believe there is some issue in the test portion?

Anything on this?