Eric Adams
Forum Replies Created
-
I replied here on 12/13 asking what to send and didn’t receive a reply. I don’t know what you mean about replying from technical support. In any event, the new plugin I am using is receiving the response from Mailgun as expected. In case it is helpful, here is what I see in their log.
{ "id": "<20231215221437.0c51702aabda81e7@mg.somedomain.com>", "message": "Queued. Thank you." }And for a failed message:
{ "code": 400, "message": "cURL error 28: Resolving timed out after 10000 milliseconds", "errors": [ "cURL error 28: Resolving timed out after 10000 milliseconds" ] }I appreciate you trying to help but I have decided to move to another solution. Best of luck in the upcoming new year.
I am happy to share whatever you need but I’m not sure which logs you are referring to. I noticed an option under Settings to enable error logging to the WordPress debug log which I hadn’t been using but have now enabled. Maybe that will catch something useful. Please let me know what else to include. Thanks.
I have followed the instructions and notice that I have had many fewer failures which is great however ‘View details’ still does not show anything for the ones that have failed. Is this feature just broken or there still something the matter with my setup? Thanks.
Here you go.
Mailer: postsmtp
HostName: redacted
cURL Version: 7.68.0
OpenSSL Version: OpenSSL/1.1.1f
OS: Linux web.redacted 5.4.0-165-generic #182-Ubuntu SMP Mon Oct 2 19:43:28 UTC 2023 x86_64
PHP: Linux 8.0.30 C
PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=No, zlib_encode=Yes
WordPress: 6.4.2 en_US UTF-8
WordPress Theme: GeneratePress Child
WordPress Plugins: ManageWP – Worker, Gravity Forms, AutomateWoo, Classic Editor, Admin Columns, Elementor Pro, Elementor, Enable Media Replace, Essential Addons for Elementor – Pro, Essential Addons for Elementor, FacetWP – Elementor, FacetWP – Pods integration, FacetWP, GP Premium, Gravity Forms PayPal Standard Add-On, Gravity Forms User Registration Add-On, Instant Images, Limit Login Attempts Reloaded, Nginx Helper, Password Policy Manager, Pods – Custom Content Types and Fields, Post SMTP, SearchWP Live Ajax Search, ShortPixel Image Optimizer, Simple Cloudflare Turnstile, Simple CSS, Simple History, Tawk.to Live Chat, WooCommerce WishLists, WooCommerce, WP Crontrol, WP Instagram Widget, WP REST API Controller, SEOPress PRO, SEOPress, WP Statistics
WordPress wp_mail Owner: /var/www/redacted/htdocs/wp-content/plugins/post-smtp/Postman/PostmanWpMailBinder.php
WordPress wp_mail Filter(s): wp_staticize_emoji_for_email, PostsmtpMailer->get_mail_args
Postman: 2.8.5
Postman Sender Domain (Envelope|Message): redacted | redacted
Postman Prevent Message Sender Override (Email|Name): No | No
Postman Active Transport: Mailgun API (https://api.mailgun.net:443)
Postman Active Transport Status (Ready|Connected): Yes | Yes
Postman Deliveries (Success|Fail): 25234 | 204
Postman TCP Timeout (Connection|Read): 20 | 60
Postman Email Log (Enabled|Limit|Transcript Size): Yes | 500 | 128I suggest adding your IP to the whitelist. If you can’t get in and have access to the server via FTP or SSH you can either rename/remove the plugin in wp-content/plugins/wordfence/ which will disable or remove it. Then you can log back in, re-enable Wordfence, and add yourself to the whitelist. You’ll probably see where it locked you out in the Tools section.
Bots attempting brute force attacks generally use a list of common accounts that less experienced site admins aren’t managing properly. In most cases, you’d never want accounts with generic, commonly used names like admin. I always set up a list of these under “Immediately lock out invalid usernames” in the Brute Force settings. My list is admin, administrator, manager, editor, user, demo, test, guest, ftp, operator, marketing, sales, support. Anyone attempting to sign in with these are certainly attempting a brute force attack, so they get locked out immediately.
There’s really not much you can do other than that. Unless you either protect your login page with HTTP AUTH (additional login) or obfuscate it by changing the login URL, people will always try to brute force login. All part of the fun of running a website I suppose.
Hi David. I see the same error when using Genesis Layout Extras. On the screen Genesis -> Layout Extras, under the Custom Post Types by Child Themes section I see this error:
Warning: call_user_func() expects parameter 1 to be a valid callback, function ‘default’ not found or invalid function name in E:\xampp\htdocs\adamsts\wp-admin\includes\template.php on line 924
I am using the Portfolio Post Type plugin for the custom post type. That might be the problem…not sure. I am going to do some more research to see what I can find.
Thanks!