Side note, as I said, I know I should know more about this. Once I get a couple things changed, I plan on moving my hosting so I don’t have to struggle with this type of stuff anymore. I just need to get my site to a certain state before I can do that.
]]>This is what was added to the .htaccess file:
# Wordfence WAF
<IfModule mod_php5.c>
php_value auto_prepend_file '/var/www/url/wordfence-waf.php'
</IfModule>
<IfModule mod_php7.c>
php_value auto_prepend_file '/var/www/url/wordfence-waf.php'
</IfModule>
<IfModule mod_php.c>
php_value auto_prepend_file '/var/www/url/wordfence-waf.php'
</IfModule>
<Files ".user.ini">
<IfModule mod_authz_core.c>
Require all denied
</IfModule>
<IfModule !mod_authz_core.c>
Order deny,allow
Deny from all
</IfModule>
</Files>
# END Wordfence WAFI’m going to send the report by email too.
]]>I added the Rewrite rules found https://www.ads-software.com/support/topic/nginx-rules-break-server/ and this fixed the podcast player issues, but the feed issues are still there. I also tried adding a new Podcast series but the feed still shows a 404 error.
]]>Everything seems to be working fine except for when you try to checkout an item using the Apple Pay option. After adding something to your cart, and clicking checkout, and selecting the apple pay option in the checkboxes, it brings you to an apple pay button to click on. After clicking on it, the Apple Pay Payment screen pops up for a split second, and then disappears without authorizing payment. After that, the Apple pay button is non-responsive.
I have enabled wordpress logging and there are no relevant logs in my wordpress logs, nor my Nginx logs. I’m not sure whats going on or how to debug this.
How can I debug and fix the broken apple payment button and get apple pay to work on my website? Thanks for any help!
]]>Ubuntu Version: 20.04.6 LTS (Focal Fossa) (aarch64) for Raspberry Pi
PHP Version: 7.4.3-4ubuntu2.19
Nginx Version: 1.25.1 Mainline
MariaDb/Mysql Version: 15.1 Distrib 10.10.5-MariaDB, for debian-linux-gnu (aarch64) using readline 5.2
WordPress Version: 6.3
Relevent WordPress Plugins: Payment Plugins for Stripe WooCommerce
On mobile devices, specifically on iOS using Safari, Apple Pay is not working. When I go to my woo commerce shop, then add an item to my cart, Click Proceed to Checkout, Select the Apple Pay Circle, Then click the “Check out with ApplePay” button at the bottom of the screen, the apple pay window pops up for only a split second, then it disappears, and the “Check out with ApplePay” button no longer works. In order to make the Apple Payment screen briefly pop up again, I need to refresh the checkout page. Then, the “Check out with ApplePay” button does the same thing again. It just pops up quickly, then disappears.
What is going on here? It used to work just fine and now it doesn’t. How can I debug and fix this issue? Thanks in advance for any help.
]]>I have run WordPress for a long time, but after I updated my Ubuntu server with the last packets I get this error in the “Site Health Status”
My server running: Ubuntu 22.04.2
- Apache/2.4.52
- PHP 8.2.8
If i run “apt update” this is the output:
root@***~ # apt update
Hit:2 https://download.docker.com/linux/ubuntu jammy InRelease
Hit:3 https://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:4 https://ppa.launchpadcontent.net/ondrej/php/ubuntu jammy InRelease
Hit:5 https://esm.ubuntu.com/apps/ubuntu jammy-apps-security InRelease
Hit:1 https://rspamd.com/apt-stable jammy InRelease
Hit:6 https://esm.ubuntu.com/apps/ubuntu jammy-apps-updates InRelease
Hit:7 https://archive.ubuntu.com/ubuntu jammy InRelease
Hit:8 https://esm.ubuntu.com/infra/ubuntu jammy-infra-security InRelease
Hit:9 https://esm.ubuntu.com/infra/ubuntu jammy-infra-updates InRelease
Hit:10 https://archive.ubuntu.com/ubuntu jammy-updates InRelease
Get:11 https://archive.ubuntu.com/ubuntu jammy-backports InRelease [108 kB]
Hit:12 https://deb.goaccess.io jammy InRelease
Ign:13 https://download.webmin.com/download/newkey/repository stable InRelease
Hit:14 https://download.webmin.com/download/newkey/repository stable Release
Fetched 108 kB in 7s (15,7 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
If i run apt upgrade i get this
root@****~ # apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
#
# An OpenSSL vulnerability has recently been fixed with USN-6188-1 & 6119-1:
# CVE-2023-2650: possible DoS translating ASN.1 object identifiers.
# Ensure you have updated the package to its latest version.
#
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.Any help will be nice.
]]>A scheduled event has failed. The scheduled event, action_scheduler_run_queue, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.How can I go about debugging this issue and what exactly is the proper way to fix this?
]]>The REST API encountered and unexpected result.
The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.
When testing the REST API, an unexpected result was returned:
REST API Endpoint: https://www.mcmo.is/wp-json/wp/v2/types/post?context=edit
REST API Response: (403) ForbiddenHow can I go about debugging this, and what can I do to fix this error? What might be the cause of this?
]]>I can access the frontend of my WordPress but not the backend.
When I try to login to my wp-admin backend by typing in browser
https://aws_route_53_subdomain_name.domain_name.com/wp-admin
I get this error
"Not Found" The requested URL was not found on this server. Apache/2.4.52 (Ubuntu) Server at <IP address> Port 80".
I also tried entering
"aws_route_53_subdomain_name.domain_name.com/wordpress/wp-admin",
but the result is the same.
When I hit enter I see the URL changes to something like
"https:///wordpress/wp-login.php?redirect_to=http%3A%2F%2Ftest.%2Fwp-admin%2F&reauth=1".
Can you please help me with this?
I suspect that the issue could be with the fact that I am using subdomain of a first prod instance and pointing it to another (this new) test instance. (I can access the frontend with “mydomainname.com” but not the backend) E.g when I ran
sudo certbot --apache
I got this error
Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems: Domain: www.test.mydomainname.com Type: dns Detail: DNS problem: NXDOMAIN looking up A for www.test.mydomainname.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for www.test.mydomainname.com - check that a DNS record exists for this domain Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet. Some challenges have failed. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
When I run: /opt/bitnami/php/etc# /usr/bin/php.default -v
PHP 8.2.1 (cli) (built: Jan 13 2023 10:43:08) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.2.1, Copyright (c) Zend Technologies
with Zend OPcache v8.2.1, Copyright (c), by Zend Technologies
But when I run :/opt/bitnami/php/etc# php -v
PHP 7.3.17 (cli) (built: Apr 23 2020 08:07:47) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.17, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.17, Copyright (c) 1999-2018, by Zend Technologies
I feel I tried everything! Seems the new PHP is installed but is not taken into account.
Does anyone have any idea?
]]>