Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi SickSquirrel, can you try the following.

    #AIOWPS_LOGIN_WHITELIST_START
    <FilesMatch “^(wp-login\.php)”>
    Order Allow,Deny
    Allow from https://www.xxxxxxxxxxxx.com
    Allow from 204.188.***.*
    Allow from 125.234.**.*. <—— remove the end dot

    so it looks like this
    Allow from 125.234.**.* <—— no end dot

    Let me know if that works.

    Kind regards

    Thread Starter SickSquirrel

    (@sicksquirrel)

    There is no dot in reality. Just the class c IP then an asterisk I didn’t want to print his IP or mine publicly

    Six sites give him the error. Three others took the addition to whitelist. I just added a different IP for him on one.

    (My error logs are full with errors from your script. Some I could fickle but others reset. My host just says it isn’t their app. Duh? They could offer to try and help a little.

    Update: after adding yet another IP and changing his password again, he just emailed

    I’m so sorry maam, work with you is good. But I’m too busy with other jobs and have to stop this job at here.

    Please, find another people have static IP do this job for you.

    I guess this problem is technically resolved, but I do wasntto know why it kept throwing errors.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi in regards to your comment below.

    I have someone working on my sites. His IP changes daily *sigh*. I whitelisted him today but he still gets 403’d. He’s not blacklisted.

    If you don’t use static IP addresses then whitelisting an IP addresses can be challenging.

    You can also read more about it from the following URL.

    I hope the above helps you further understand whitelisting of IP addresses.

    If you issue has being resolved could you mark this support thread as resolved.

    Kind regards

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘403 error’ is closed to new replies.