• Resolved nikkofir

    (@nikkofir)


    Calendar is public
    Calendar ID is correct
    API key set up correctly with HTTP referrer restriction e.g.
    *.sitename.org.uk/*

    Generates the following error:

    While trying to retrieve events, Google returned an error:
    
    { “error”: { “code”: 403, “message”: “Requests from referer \u003cempty\u003e are blocked.”, “errors”: [ { “message”: “Requests from referer \u003cempty\u003e are blocked.”, “domain”: “global”, “reason”: “forbidden” } ], “status”: “PERMISSION_DENIED” } }
    
    Please ensure that both your Google Calendar ID and API Key are valid and that the Google Calendar you want to display is public.

    Removing the HTTP referrer restriction immediately makes the calendar work – however this is obviously not ideal. How can we get the calendar plugin to identify itself with the referrer correctly? It appears that the referrer is <empty>.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Rohit Singhal

    (@rosinghal)

    @nikkofir Sorry for delayed reply. Can you confirm if the issue still persists? Sometimes Google throws this error because of caching issue as per my first-hand experience.

    Marking this thread as resolved since it is old. Feel free to reply to open it.

    Hi, I see this exact same issue. I’m running that latest version of WordPress and calendar plugin. I also had HTTP restriction on the key – when disabled everything works. I really don’t want to make it public. I’ve used the same restriction settings on other apps and it works perfectly.

    Plugin Support john

    (@johnweru)

    Hi there,

    Thanks for writing in.

    In regards to the query here, we are actually looking into resolving this issue. Do you perhaps have the pro addons installed?

    I look forward to your reply.

    Kind Regards,

    John

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Calendar not sending referrer – API keys restricted by HTTP referrer not working’ is closed to new replies.