• Resolved Quique

    (@enriccardonagmailcom)


    Hello,
    Since I installed the plugin I’m having tones of errors in my error.log file. Two kinds:

    Around 5 every minute:
    [31-Dec-2017 12:12:51 UTC] Error in maxmind_db_manager:get_db:::WP_ERROR: Forbidden

    1 every 2 hours:
    [02-Jan-2018 00:22:52 UTC] <h4>Estas realizando peticiones demasiado rápidamente. Por favor, vuelve a enviar tus peticiones a un ritmo más lento. Para mayor información, revisa las Recomendaciones de eficiencia.</h4>

    The website mentioned doesn’t provide enough info for troubleshooting.

    I’m using WordPress 4.9.1 Language: Spanish. PHP version: 7

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • I have the same issue:

    2018-01-02 21:01:37 Error 107.178.196.37 AH01071: Got error ‘PHP message: Error in maxmind_db_manager:get_db:::WP_ERROR: Forbidden\n’

    except for the fact that it hits me multiple times per second ??

    Wordpress 4.9.1, PHP 7, Plugin version 1.5.2.

    Yep, dozens upon dozens. In another thread here, I think someone said it won’t affect anything except prevent proper use of GeoTargeting, but it’s definitely something that shouldn’t happen.

    I’ve gone so far as to set the entire path to 777 temporarily, but it still throws the errors (I set the permissions back to standard after the test).

    Love to see this fixed!

    I can not use the plugin properly neither, since I have this message too all the time when I try to search for anything:

    Estas realizando peticiones demasiado rápidamente. Por favor, vuelve a enviar tus peticiones a un ritmo más lento. Para mayor información, revisa las Recomendaciones de eficiencia.

    And also, my links do not appear in the posts. What happened?

    The same error message has been reported numerous times now. See other threads for a solution.

    Plugin Author Amazon Associates Link Builder

    (@amazonlinkbuilder)

    Dear Users,

    We fixed the issue in v1.5.3 of plugin released yesterday. Please update to the same and let us know if this problem got fixed for you.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Errors in the error.log’ is closed to new replies.