• Resolved m3gadeath

    (@m3gadeath)


    Hi,

    We just upgraded to PHP 8.3 from 8.0 (outdated version).

    However now we are getting – Your access to this site has been temporarily limited by the site owner. Your access to this service has been temporarily limited. Please try again in a few minutes. (HTTP response code 503)

    We were not getting this in PHP 8.0 or lower. Even on 8.1 PHP we are getting this error.

    All signed up authors/admins are getting this error.

    Can you help how to permanently get rid of this error.

    Best Regards

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support wfscott

    (@wfscott)

    Hello, @m3gadeath

    This may be an IP detection issue, which can be configured in Wordfence > All Options > General Wordfence Options > How Does Wordfence Get IPs. There, you should go through the different options to see which correctly reports your IP in the section below in Detected IPs and Your IP with this setting.

    To gain access to the site while you’re blocked, I recommend using the options outlined in this video: https://www.youtube.com/watch?v=JnThqkQmPlY

    First, you can try using the option?Send Unlock Email?on the block screen itself. This method is shown first in the video above. For that, you can enter your admin email on the block screen and click the send button. You should then receive an email with a few options. Once you open the email, you can first try the top option “Click here to unlock your ability to sign-in and to access the site.” If you do not receive an email, the site is likely having issues with email functionality. Be sure to check your junk/spam inboxes as well.

    If you receive the email and use one of the options, go back to your login form and log into the site. If this works, I recommend checking your IP detection at this point.

    If that doesn’t work, you can consider either using the third option in the email, “Click here to unlock all IP addresses and disable the Wordfence Firewall and Wordfence login security for all users.” With that option used, you should be able to log in and check the configuration of the site.

    Once you log in, please send diagnostics from Wordfence > Tools > Diagnostics > Send Report by Email and send that to wftest at wordfence dot com with your forum username in the appropriate field there.

    If the email options are not working for you, you can try using FTP or file manager to temporarily deactivate Wordfence and log in.

    If you decide to use FTP or File Manager from your hosting side/cPanel, you can rename the Wordfence folder in wp-content/plugins to something else (wordfence_temp for example). That will then be wp-content/plugins/wordfence_temp. The video above goes over this method at the 2:25 mark.

    You should then be able to log in as you normally would without seeing a Wordfence block. Log into your site, then after that is successful, go back to your FTP client or file manager and rename the wordfence plugin back to its original “wordfence” name (wp-content/plugins/wordfence). You can then refresh your dashboard on your site and you should see Wordfence back on the left-hand side. You can go into?Wordfence > Firewall > Blocking?and remove the block mentioning your IP/username/login name.

    If you are blocked again immediately after renaming Wordfence back to its original name, you can rename it again to disable it, download the Wordfence Assistant plugin, activate that, and use the option there to “Disable Wordfence Firewall”. With that option used, you can now rename Wordfence back to its original name and you should be able to send diagnostics as outlined above. Please let us know here when you send diagnostics.

    If for some reason the site were to go down after renaming the Wordfence folder, you can rename it back to just “wordfence” (without the quotes) and we will need to check on the config files that may have been changed during the firewall optimization process.

    Let me know if you have any issues.

    Thanks,
    Scott

    Thread Starter m3gadeath

    (@m3gadeath)

    Yes, via FTP , we need to remname only then we get access. We have been facing this issue again and again. every few days.

    Have emailed you the diag report on the email ID as well.

    Need a perma solution for this problem.
    Thanks In advace.

    Plugin Support wfscott

    (@wfscott)

    @m3gadeath

    I do not see anything standing out in the diagnostics, initially. I see a Cloudflare IP looks to be detected, so via the Wordfence > All Options > General Wordfence Options > How Does Wordfence Get IPs, I recommend checking the Cloudflare option there to confirm it reports your correct IP, and if so, you can use that if you’re using Cloudflare.

    Are you seeing a number of blocks in the Wordfence > Firewall > Blocking area? If so, please screenshot those and send them over to our email (wftest @ wordfence dot com) with your forum username as the subject.

    It is also possible you’re seeing a cached block page. Does refreshing the page when you’re seeing the block allow you access at any point?

    Thanks,
    Scott

    Thread Starter m3gadeath

    (@m3gadeath)

    Hi, yes we are connected to cloudflare.

    In that option – this is enabled.

    –?Let Wordfence use the most secure method to get visitor IP addresses. Prevents spoofing and works with most sites.?(Recommended)

    We have just changed it to cloudflare option. Will let you know in a few days if we see this error again.

    Thanks.

    Plugin Support wfscott

    (@wfscott)

    Thanks for the update — I’ll keep an eye out.

    Scott

    Thread Starter m3gadeath

    (@m3gadeath)

    Hi,

    Thanks –?cloudflare option.

    Seems to be working. No issues in the last few days. Thanks for the help. God bless!

    • This reply was modified 3 months, 1 week ago by m3gadeath.
Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.