toddwhittle

I found the issue. There is a popup on the cart page, and I had the shortcode for checkout on this pop up AS WELL AS the actual cart page. I removed the one from the popup and that resolved the issue.

Shameem and Juan, thank you for your help with this troubleshooting.

Hey Shameen…thanks for the response. Here, you’ll see a popup first, when you first visit the cart page. https://mulchman.com/cart/

https://snipboard.io/91tx7w.jpg

For a discount code, try “march20”, then click “apply coupon”. You’ll see that the same item is repeated, but it’s not doubling the purchase. It’s just displaying a repeat of the item in the cart.

https://snipboard.io/FRNAwC.jpg

System Status Report – https://www.dropbox.com/scl/fi/mpfvgdwxotxbg4qjen37j/SystemStatusReport_mulchman.com_2024-03-07T15-22-58.txt?rlkey=9x1ltgv9v089jbj8zd1iev53s&dl=0

Custom Payment Gateway Log – https://www.dropbox.com/scl/fi/8peq4ly0twyp7in39q88d/custom_payment_gateway-2024-03-07.log?rlkey=bi612vedr32gspti06ysumv81&dl=0

Thank you Aswin! I appreciate the quick response!

Todd

Thanks Steve…one other question, if I may…

I have Ultimate Member plugin installed for our users. Are you aware of any way to combine the search feature on the home page to search not only the content, but the member directory as well? Right now, we have to have separate search bars – one for each. Any help would be appreciated.

Todd

Damn dude – I wish everyone was as quick to reply as you. You sir, need a raise. I was WONDERING who that email address was!! Thanks again. Have a great weekend!

T

Ugh….it’s buried WAY down there. Thanks! Sorry for the stupidity! ??

Now you know. ??

So Steve – just discovered something. Did a little more research and found that SELinux is VERY secure. So I set it to permissive, and BINGO. Money. So if you ever run into the issue again, you can try this solution. Again, THANK YOU for your help.

T

Well, I can’t tell you how much I appreciate your help. I guess I’ll continue to wait for what Artbees says. Thanks so much, Steve.

Looks like it is…

[twhittle@maagbdevweb1 /]$ more /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
10.92.33.34 marylandregionalaviation.aero
[twhittle@maagbdevweb1 /]$

Of the server you mean? I’d have to check.

Hey Steve – I don’t ‘think’ this would have anything to do with it, but right now, we don’t have a public domain name pointed to this IP address just yet. I set up the URL for wordpress, and changed my hosts file to point to this while working on the site. But right now, the IP is 10.92.33.34. The URL is marylandregionalaviation.aero.

Here is the site info based on Health Check.

### wp-core ###

version: 5.3.2
site_language: en_US
user_language: en_US
permalink: undefined
https_status: false
user_registration: 0
default_comment_status: closed
multisite: false
user_count: 3
dotorg_communication: cURL error 7: 

### wp-paths-sizes ###

wordpress_path: /var/www/html
wordpress_size: 37.88 MB (39718346 bytes)
uploads_path: /var/www/html/wp-content/uploads
uploads_size: 1,004.45 KB (1028557 bytes)
themes_path: /var/www/html/wp-content/themes
themes_size: 12.57 MB (13182138 bytes)
plugins_path: /var/www/html/wp-content/plugins
plugins_size: 19.15 MB (20076427 bytes)
database_size: 1.22 MB (1277952 bytes)
total_size: 71.80 MB (75283420 bytes)

### wp-active-theme ###

name: JupiterX Child (jupiterx-child)
version: 1.0.0
author: Artbees
author_website: https://jupiterx.com
parent_theme: JupiterX (jupiterx)
theme_features: title-tag, post-thumbnails, automatic-feed-links, html5, wp-block-styles, editor-styles, jupiterx-default-styling, wc-product-gallery-zoom, wc-product-gallery-slider, woocommerce, menus, widgets, editor-style
theme_path: /var/www/html/wp-content/themes/jupiterx-child

### wp-parent-theme ###

name: JupiterX (jupiterx)
version: 1.16.0
author: Artbees
author_website: https://artbees.net/
theme_path: /var/www/html/wp-content/themes/jupiterx

### wp-themes-inactive (1) ###

Twenty Twenty: version: 1.1, author: the WordPress team

### wp-mu-plugins (1) ###

Health Check Troubleshooting Mode: author: (undefined), version: 1.7.0

### wp-plugins-active (4) ###

Elementor: version: 2.9.3, author: Elementor.com
Health Check & Troubleshooting: version: 1.4.2, author: The www.ads-software.com community
Jupiter X Core: version: 1.12.0, author: Artbees
WP-ServerInfo: version: 1.66, author: Lester 'GaMerZ' Chan

### wp-media ###

image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1690
imagemagick_version: ImageMagick 6.9.10-86 Q16 x86_64 2020-01-13 https://imagemagick.org
imagick_limits: 
	imagick::RESOURCETYPE_AREA: 15 GB
	imagick::RESOURCETYPE_DISK: 9.2233720368548E+18
	imagick::RESOURCETYPE_FILE: 768
	imagick::RESOURCETYPE_MAP: 15 GB
	imagick::RESOURCETYPE_MEMORY: 8 GB
	imagick::RESOURCETYPE_THREAD: 1
gd_version: 2.2.5
ghostscript_version: 9.25

### wp-server ###

server_architecture: Linux 4.18.0-147.el8.x86_64 x86_64
httpd_software: Apache/2.4.37 (Red Hat Enterprise Linux) OpenSSL/1.1.1c mod_fcgid/2.3.9
php_version: 7.4.3 64bit
php_sapi: fpm-fcgi
max_input_variables: 1000
time_limit: 30
memory_limit: 512M
max_input_time: 60
upload_max_size: 20M
php_post_max_size: 20M
curl_version: 7.61.1 OpenSSL/1.1.1c
suhosin: false
imagick_availability: true
server-headers: unknown

### wp-database ###

extension: mysqli
server_version: 10.3.17-MariaDB
client_version: mysqlnd 7.4.3

### wp-constants ###

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /var/www/html/wp-content
WP_PLUGIN_DIR: /var/www/html/wp-content/plugins
WP_MAX_MEMORY_LIMIT: 512M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_LOCAL_DEV: undefined

### wp-filesystem ###

wordpress: not writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
mu-plugins: writable

I’ll try that right now.

Did that (installed Health Check) a few days ago…

3 Critical Issues:

1 – The REST API encountered an error

The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.

The REST API request failed due to an error.
Error: [] cURL error 7:

2 – Could not reach www.ads-software.com

Communicating with the WordPress servers is used to check for new versions, and to both install and update WordPress core, themes or plugins.

Error Your site is unable to reach www.ads-software.com at 198.143.164.251, and returned the error: cURL error 7:

3 – Your site could not complete a loopback request

Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability.

The loopback request to your site failed, this means features relying on them are not currently working as expected.
Error encountered: (0) cURL error 7:

Okay, I’m getting this…but I am not fluent in this, so my apologies for not understanding. Is something standing out other than the no content handshakes?

[twhittle@maagbdevweb1 /]$ curl -v https://api.www.ads-software.com
* Rebuilt URL to: https://api.www.ads-software.com/
* Trying 198.143.164.251…
* TCP_NODELAY set
* Connected to api.www.ads-software.com (198.143.164.251) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, [no content] (0):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: OU=Domain Control Validated; CN=*.www.ads-software.com
* start date: Nov 6 17:42:01 2017 GMT
* expire date: Dec 15 20:11:21 2020 GMT
* subjectAltName: host “api.www.ads-software.com” matched cert’s “*.www.ads-software.com”
* issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=https://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority – G2
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.3 (OUT), TLS app data, [no content] (0):
* TLSv1.3 (OUT), TLS app data, [no content] (0):
* TLSv1.3 (OUT), TLS app data, [no content] (0):
* Using Stream ID: 1 (easy handle 0x55c23bdf5700)
* TLSv1.3 (OUT), TLS app data, [no content] (0):
> GET / HTTP/2
> Host: api.www.ads-software.com
> User-Agent: curl/7.61.1
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS app data, [no content] (0):
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* TLSv1.3 (OUT), TLS app data, [no content] (0):
* TLSv1.3 (IN), TLS app data, [no content] (0):
* TLSv1.3 (IN), TLS app data, [no content] (0):
< HTTP/2 302
< server: nginx
< date: Thu, 05 Mar 2020 16:27:09 GMT
< content-type: text/html; charset=utf-8
< location: https://developer.www.ads-software.com/rest-api/
< x-frame-options: SAMEORIGIN
<
* Connection #0 to host api.www.ads-software.com left intact