My update to 5.9 has been difficult. 5.9.0 seems to have installed badly, after a few days my admin pages began behaving as downloads instead of loading in my browser. A downgrade to 5.8 and a reinstall of 5.9.0 (plus clearing the cookies and cache) fixed this. 5.9.1 installed without issue. A few days after 5.9.2 installed, my admin pages (not all of them, but most of them) began displaying 403 errors. A downgrade to 5.8 fixed this, and I reinstalled 5.9.2. Two days later, the same error has recurred. A downgrade to 5.8 fixed it a second time.
I’m not having the errors now, because I’ve left version 5.8 as it is. It’s only on the admin pages anyway, so you won’t be able to see it without login information, and that’s only if I reinstall 5.9.2 and it happens again.
I’m reluctant to reinstall 5.9.2. It’s has either installed badly twice in a row, or there is something else going on. My theme is Customify 0.3.7 . I can provide a list of plugins if that’s helpful, but turning off plugins and themes does not fix the issue, going back to 5.8 always does.
]]>I’m in the process of cleaning up my current site installation readying to move to a VPS.
My first attempt collapsed due to a catastrophic server 403 Forbidden error, which was resolved through updating the apache html version permissions. However, while this is the case, I’m still experiencing a number of internal 403 errors — “Update failed: <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”> 403 Forbidden”
Ok, how’s this is relevant… well, before moving my site again, which I know does work besides the internal errors above, I decided to run some Wordfence checks where my site currently sits. I opened up the WordFence Logs.
Wordfence Full Activity Log:
While most of the results seem promising, I found this in red —
“error] Call to Wordfence API to resolve IPs failed: There was an error connecting to the Wordfence scanning servers: cURL error 6: getaddrinfo() thread failed to start”
I have had a look through the net for an answer and found the one below through this forum. I have taken the liberty to run the checks, bearing in mind I don’t have anything installed to run “Trace Route” or, “tracert”.
dig noc1.wordfence.com – 46 IN A 44.239.130.172
nslookup noc1.wordfence.com – Address: 44.239.130.172
host noc1.wordfence.com – Address: 44.239.130.172
getent hosts noc1.wordfence.com – Address: 44.239.130.172
ping noc1.wordfence.com – 56(84) bytes of data (frozen)
“You should then see the IP 69.46.36.28 returned.”
As you can see the address is different from the one provided.
Any ideas, or do I not need to worry!?
My Appreciation in advance. John
]]>The iThemese plugin (free version) is spawning 403 for URLs as follows
Website: https://www.romancescamsnow.com
Link you are blocking: https://romancescamsnow.com/dating-scams/landmark-case-changes-everything-for-money-mules/?utm_campaign=SCARS Newletter ? News %26 Information About Scams&utm_medium=email&utm_source=Revue newsletter
Link you are NOT blocking: Landmark Case Changes Everything For Money Mules – SCARS Romance Scams Education & Support Website (romancescamsnow.com)
WHY???
Thes blocked link comes from our newsletter provider GetRevue.com – this is a recent problem – last week or so, it suggests it is related to a recent update???
Non of our newsletter links now work, this has destroyed our campaigns during our most important week of the year! By turning OFF your plugin things work – ON doesn’t work.
We have gone through the .htaccess & wp_config files – no joy. We have gone through every option in ithemes security – no joy. The ONLY thing that solves the problem is to deactivate.
What is worse, you don’t even have a way on your website to report problems to you. Very unacceptable.
Have been a long-term user, at least 9 years – but sadly I cannot be any more – you broke your plugin. If you can fix it, please email me at [email protected]
]]>After clicking on the link you will see a resources page of my website. When you scroll down you will see that Creative Market and Canva are lined (an overwritten line on them). It is caused because of links. Same thing happened to all the buttons and etc on which I have used those links.
When I clicked on them it worked normal and when I checked on broken link checker it appeared that that is a 403 error.
The problem is I want the line on them to disappear. Please help me fix this.
Thanks,
Ekta
403 – Forbidden Error
You are not allowed to access this address.
If the error persists, please contact the website webmaster.
Common reasons for this error are:
Incorrect file/directory permissions: Below 644.
In order files to be read by the webserver, their permissions have to be equal or above 644. You can update file permissions with a FTP client or through cPanel’s File Manager.
Restrictive Apache directives inside .htaccess file.
There are two Apache directives which can cause this error – ‘Deny from’ and ‘Options -Indexes’.
UPDATE: My server’s IP Address changed and caused this issue. I think they should give a clearer error message. So that is why I gave 4/5.
]]>I am not sure what is going on but my users and potential members aren’t able to register or log in. After looking into this with the Hosting provider it seems that the plugin is creating a “AIOWPS_LOGIN_WHITELIST_START” entry in the htaacess file which is creating this problems. It is listing 2 ip’s, mine and the hosting company’s.
Apparently the plugin is making an exception and i was told by the tech “You cant make an exception to it by adding the domain in there as the people accessing access it though their own IP. Most likely the plugin is creating the issue.”
What is going on and how to fix this? Thanks
]]>I tried to switch out of troubleshooting mode and everything went pear shaped and I received 403 errors. Everything I try and do in the backend I get a 403 error. Like an earlier post I am using litespeed cache, but I cannot get to to the dashboard to clear the cache. I tried renaming litespeed to _old but that did not force a cache clearing. We are also on cloudflare.
I have deleted WP Health heck and the php file in the mu plugins but still getting the 403 errors when trying o acess anything in the backend.
We’re a news site. we have journalists who can’t get in and publish their stories. Any help will be appreciated.
Thank you
]]>