Vidyut

It is possible, Mike. If it is important, I will happily confirm this by switching the lines again in a day or two. Least I can do, after knowing what I went through.

Though I suspect you are right about the reboot. Everything just worked after the reboot. I didn’t even have to start testing the permalinks setup.

For the record, result of further testing to identify what worked by switching the Nginx configs I’d tried, in case it helps anyone else.

This is the “try_files” line recommended by Nginx on their configuration page.

try_files $uri $uri/ /index.php;

This does NOT work.

This below is recommended by wordpress.

try_files $uri $uri/ /index.php?args;

Also does not work.

What worked was:

try_files $uri $uri/ /index.php?q=$request_uri;

After I restarted the server, I was planning to troubleshoot further, when I got a notification of an order! By a real client ??

Thank you @mike.

I will keep an eye to see that all is working as it should, but I think it is. This seems resolved to me. Will confirm in a couple of hours.

Okay, so I rebooted on a lark before starting more fiddling and it has started working. No idea what fixed it.

Much appreciation @mike. Apologies for the bad review. It was a shitty way of taking out my frustration. I am sorry.

@mike Not discounting your experience. It is the first concrete thing that seems possible. God knows all else has failed multiple times. Looking into this right now. Do you have a sample config to compare with that you recommend? I assume you are talking about the try_files line?

@mike
Sorry about the review. It has been a frustrating few days. Will fix it as soon as I get this thing running.

I have checked the nginx configuration too, switched it with another working configuration as well, same result. ?? All other plugins are working with both. Few other sites on server with same configuration also working. But it is a starting point. Will check again in a few hours, line by line.

None of the attempts at troubleshooting have even changed the problem in the slightest to hint at where the issue may be. Used nginx (with and without pagespeed, with and without SSL termination), mariadb and hhvm/php-fpm. All of them at latest stable versions, updated. Also tried with other browsers, laptops, mobiles, logged in, logged out, from device that has never been on that site before (to absolutely rule out cached page in browser…). None of these changes even made slightest difference to the issue. Exactly same result. The area remains greyed out. Becomes active briefly on entering new data – more like brief flash – reverts to being inactive. Consistently.

@webaware read above. All plugins disabled. SSL proxy disabled, zero caching anything, reinstalled WordPress and woocommerce, both default themes as well as storefront… is still giving me this ??

Any idea where to check for potential interference?

Best I can make out, Network tab shows a call to https://vidyut.info/checkout/?wc-ajax=checkout that results in the checkout page as a response and gives the “Syntax error: Unexpected token <” error, because it is expecting json, not an html page. I’m no coder but aren’t ajax calls made to admin-ajax? My page seems to be making them to the checkout page itself – it is not cached. It is returning what woocommerce gives it.

Will try that, vark, Eventually I need to get the plugin working here. Seems to be a form issue. Something isn’t letting the form proceed.

Closest I can figure out is that the json response seems to be returning a page instead of something looking like json. But can’t figure out where/why it is coming from.

Already fixed. Made no difference to the checkout problem. Feel free to “buy” with full process to test. I don’t have payment gateways active, only bank transfer info. Just add “testing” in the note.

oh, the site is at https://vidyut.info

Other things i have checked:

Memory – seems plenty – 256M – not many posts/products on site.

Re-saving permalinks (both as they are and after changing to something else and back)

Deleting and re-creating checkout page.

Uninstalling and reinstalling woocommerce.

Taking site directly to ssl instead of an ssl reverse proxy.

NONE of the above fixed the issue.

@christi

I did read that thread, and it did not help. The server logs don’t show anything out of the ordinary.

The greyed out area seems to come alive briefly, but reverts to being disabled when I enter some data in the address fields.

I tried hiding shipping till address was entered, and even entering full address did not make it display, which indicates that the address being entered did not get recognized.

I tried seeing the network responses and one of the ajax calls to update the page appears to return an html page. Not sure this is normal.