ad: TinyPaddle-1

Callsign xml lookup error: (403) Forbidden

Discussion in 'QRZ XML Logbook Data' started by AD1L, Feb 20, 2019.

ad: L-HROutlet
ad: l-rl
ad: abrind-2
ad: Left-3
ad: Left-2
ad: Radclub22-2
ad: L-MFJ
  1. AD1L

    AD1L Premium Subscriber QRZ Page

    Using ACLog v6.4

    Tried filling missing (non contest) data for this past weekend's ARRL DX CW contacts.

    Tried yesterday and the access crawled along and resulted in "timeout" errors.

    Tried today and at first it appeared to be moving along for a couple calls but then started throwing the following error. I acknowledged the error and it might resume for one call or two then throw the error again and again.

    Had to close the program to get out of this loop.
    Reopened the program two more times to same resulting error (obviously different calls for each instance).

    Anyone got any ideas?

    [​IMG]
     
  2. AD1L

    AD1L Premium Subscriber QRZ Page

    Different day still the same errors.

    No reply here.
     
  3. AA7BQ

    AA7BQ QRZ Founder QRZ HQ Staff QRZ Page

    A 403 error means that your account has triggered mod_evasive in the Apache server, which has to do with the number of lookups per minute. The error should self reset after a waiting period. We have seen some users exceed 1000 lookups per minute, which, unfortunately, affects all users and therefore must be throttled.
    We do not know exactly what your program was doing at the time, or if some other program in your shack was doing this. In any event, it's not a common error and one which is triggered by excessive usage. Please contact us directly if you would like to troubleshoot the problem with an engineer. support@qrz.com
     

Share This Page

ad: Alphaant-1