nigelrs

I appreciate what you are saying.

I want to say from my experience, when I installed LE on my domain, from my Plesk panel, I select a wildcard option. It puts the record as a txt record acme-challenge.<YOUR_DOMAIN>.

However, that still does not cover the issue that the certificate is only covering the main domain, even with the wildcard option on the SSL. Even if I create a physical sub domain, that isn’t being picked up by LE, you have to go into that and apply it’s own SSL. It could well be a configuration issue with LE and the server – but I cannot find a way around it. I have even been to the server people, I have tried a serveralias in Apache doubling up with a wildcard – all to no effect.

But thanks for your input. I have to look elsewhere.

The advice goes against anything I have experienced with LE. The DNS set up works fine for the main domain using the acme-challenge domain and the record; fine for the main domain and for subdomains a wild card does not work, you have to go into each subdomain and apply a let’s encrypt seperately.

LE simply does not support wildcards to cover virtuals.

Privacy error (lifetoolscorporationltd.co.uk)

This is a domain page with the nett error. My understanding is Let’s Encrypt does not cover virtual domains via a wildcard; it can only cover main domains or actual subdomains.

I have been informed that using the WP, then network set up, then creating the subsites (multi sites) is designed to sync all of the sub sites from a master site.

This is needed as I am running a central master site for a health related service, but sub sites will be for niche markets and will want the same information, but presented differently with additional bonus features only found on that sub site.

Also, the membership software will only work on a virtual multi site set up.

Hello,

I had the server ‘work a fudge’ during testing, so the subomains had a temp cert applied from the server.


This is another testing page:

https://work-well.nigelsinger.com/

and reads net::ERR_CERT_COMMON_NAME_INVALID

Cannot recall it exactly, I think I disabled Wordfence, set it up on Slice then renabled it; it was something similar to that.

Thanks Mihai,

I have done that, look forward to your support.

Thanks guys, I had this problem as well. I started up and had over 100 sign ups over night, so i guess they were all bots as I had Wordfence 2FA off to allow the Slice captcha to work. Will try a different setting with the code.

Thanks, this is working now and I have amended the text. Looking forward to road testing this out and seeing the best methods to recruit affiliates.

Thank you, I have used code snippets, it is giving me this warning:

Don’t Panic
The code snippet you are trying to save produced a fatal error on line 5:

syntax error, unexpected token “return”
The previous version of the snippet is unchanged, and the rest of this site should be functioning normally as before.

Line 5 is just the ‘return;’ in the code line below:

if ( empty( $_POST[‘slicewp_token’] ) || ! wp_verify_nonce( $_POST[‘slicewp_token’], ‘slicewp_register_affiliate’ ) ) {
return;

Thank you, I have done this and it works. The only time it clashes is with Wordfence Security. That has the option to have Google Captcha for general website sign ups and only has v3. Whenever that is turned on, and your plugin is turned on, it won’t allow a new registrant to sign up but triggers a system email for a user to verify themselves; but this, alas fails. So Wordfence has to have Captcha disabled to allow sign ups.

Thank you for your time, closing this now as I have found a work around.

Thanks, I did open a new thread 3 days ago when I realised it may have happened. I haven’t had a single reply to that as yet. Thanks.

I have also just seen in the WooCommerce Status that:

Enforce Approved Product Download Directories: –

So the approved product download is not enforced and I cannot see where you ‘enforce’ it? That may solve the issue?

Can I ask for a clarification please regarding this. I have all of my products in a folder called /audio/

So my domain https://mydomain/audio/ and then it goes:

/audio/recording1/track1.mp3
/audio/listenup/track1.mp3
/audio/listenup/track2.mp3

So following the /audio/ I have different titles and numerous tracks within those titles.

In my approved downloads directories I have tried both
https://mydomain.com/audio/*.*/
https://mydomain.com/audio/

It is enabled. If I selected the track url in the product and paste that into a url directly, it plays. So the url is right. The storage directory is listed and enabled.

However, each time I get an order, I get the “File not found: Go To Shop” warning.

I am not sure what to look at next?

• This reply was modified 2 years, 2 months ago by nigelrs.