yorkki

Hi @ashikurwp, tested and it works. Thanks for the fix, take care!

BR, – Yorkki

Hi @ashikurwp,

thanks for your reply, and no worries, glad I could help.

Will wait for the fix, and close / mark this thread solved when done.

BR, – Yorkki

Just adding inspects,

This works: data-eael-wrapper-link='{“url”:”https:\/\/domain.smthg\/path\/to\/page\/”,”is_external”:””,”nofollow”:””}’

This does not work: data-eael-wrapper-link='{“url”:”\/path\/to\/page\/”,”is_external”:””,”nofollow”:””}’

• Yorkki

@hilbertknl No worries, glad to help. IF and when WF updates this, remember to revert / disable sha1 (optional, but recommended). You may even disable it now, if all of your WP sites have updated rules. Problem again is that new rules and sites won’t update. Anyways, to revert/disable sha1 type:

update-crypto-policies --set DEFAULT and reboot.

@wfpeter Hi Peter, I sent you e-mail about this. Could you WF guys take a look at this issue please. It’s, say the least, annoying problem on all RHEL9. Here is another post about it. And now that many CentOS’s are being updated / migrated to other RHEL9 distros, more and more rules are not updating, without people even knowing about it.

Cheers,

BR, – Yorkki

Hi @catwingz ,

sha1 is disabled as crypto-policy by default on Alma and Rocky (and other rhel9), so to get rules update again, need to enable it.

update-crypto-policies --set DEFAULT:SHA1

If you/they run that command and reboot the server, rules should update within next 30 minutes or so. But, they (if this a hosting company or something where your site is) might not wanna do that. This is a problem with WF signing, and def not ideal situation.

p.s. Google the command first and make sure you/they understand what it does and if it effects anything else you/they might have on the server. Test this on a non-prod server first, if possible. Good resources are?here?and?here. So until WF updates their end… as far as I know, this is the only way to get rules updated again.

I’d ask them, show this thread or something. GL.

BR, – Yorkki

Hi @catwingz , those are rhel (Red Hat) operating systems, Linux distros.

Rocky Linux and AlmaLinux (mostly used successors for Centos), among other rhel9 distros, have security hardened, and rules for WF are not updating because of this.

Now, the cause of rules not updating can be million things, but this is tricky one because it’s server-wide problem, not WP site/theme/plugin.

BR, – Yorkki

Hi @catwingz , let me guess, distro is Alma or Rocky 9?

Hi @hilbertknl , as I thougth.

sha1 is disabled as crypto-policy by default on Alma and Rocky, so to get rules update again, need to enable it.

update-crypto-policies --set DEFAULT:SHA1

If you run that command and reboot the server, rules should update within next 30 minutes or so.

p.s. Google the command first and make sure you understand what it does and if it effects anything else you might have on the server. Test this on a non-prod server first, if possible. Good resources are here and here. So until WF updates their end…

• This reply was modified 1 year, 8 months ago by yorkki.

@hilbertknl What is the OS/Distro where DA is installed?

• This reply was modified 1 year, 8 months ago by yorkki.

@daemonic79 Holy cow, it works now for some reason. So it must’ve been the sha1. It just took a little bit of time to update. Now my rules.php has been updated and I can see from the backend that the rules are there!

Million thanks @daemonic79 for the help/tip. Now I guess need to figure out what other impacts this might have before doing other (prod) servers.

You recon this is something WF should take a look at / fix at their end, or is it just Rocky/Alma “issue”?

BR, – Yorkki

@daemonic79 Damn, wasn’t the easy fix I was hoping for.

I changed the DEFAULT and verified it was sha1, rebooted server. Then first tried just deleting rules.php, but it came back as 0kb. Then deleted whole wflogs, all came back ok but rules.php still 0kb. Then removed the plugin and deleted all data/tables, installed it again but the damn one file is still 0kb ??

Damn this sucks lol. Thanks for the help though, appreciate it.

Not sure what to do next…

BR, – Yorkki

Awesome @daemonic79 , I’ll try on one server, which I can reboot right now. Will let you know if it works. Thanks!

BR, – Yorkki

@daemonic79 Hi, thanks for your reply. I’m running Rocky Linux 9.2 on all of the problem servers. I think you are on something here.

I can try to google this, but if you have an easy fix procedure, would appreciate it, thanks ??

BR, – Yorkki

Hi, just sent another report. Now this report is from different server, so different IP. It’s in a different country even! I did a new clean WP installation, and the only plugin is WF.

Same problem there, rules.php is just 0kb no matter what I do.

Did few curl commands from this server too.

Any particular port(s) I should have open for rules? Both these servers are on a cloud, so maybe something the cloud / provider is blocking? My only server working with rule updates, is not on a cloud…

I’m lost…

BR, – Yorkki

• This reply was modified 1 year, 9 months ago by yorkki.

Hi Peter, thanks for the reply. I get HTTP/2 301 or HTTP/1.1 301 Moved Permanently from all servers, depending on the distro.

Edit: just did the query four times in a row, will do few more from the problem server.

BR, – Yorkki

• This reply was modified 1 year, 9 months ago by yorkki.