I was testing this module today and after confirming that the login buttons were displayed correctly, things stopped working a few minutes later.

Going to the Gigya settings page gives this error message:
Gigya encountered an error while validating itself. Please check watchdog and try later. If this message keeps appearing please contact gigya or file a bug in the gigya project issue queue

And watchdog shows this entry for each attempt to access Gigya settings or features:
403002 Forbidden. Request has expired

Comments

matthew petty’s picture

matthew petty commented

I uninstalled and then reinstalled gigya, and now two errors are being generated for each request...

Also, my server time is 3 minutes off from time.gov.

japerry’s picture

japerry
Location KOMK
commented

it does indeed look like a time issue. Gigya is somewhat sensitive about making sure the timestamps match up, and your server might be off enough to cause it to fail.

The new 'kill switch' validation is for instances like this, to make sure people don't get WSOD for invalid gigya API calls. I believe you were having WSOD issues in the past?

matthew petty’s picture

matthew petty commented

Ok, I'll see about getting it spot on and report back if that solves the problem.

matthew petty’s picture

matthew petty commented

It's perfect on the time now, but I still get the error. And why would I get errors from time sync on the settings page, anyway?

matthew petty’s picture

matthew petty commented
Status: Active » Closed (fixed)

It seems to be functioning fine as of this morning. I'll re-open the issue if it comes back.

arnaudfischer’s picture

arnaudfischer commented

Very promising module. Thank you so much!

Matt, how did you solve the probleme? I am getting the same error on the settings page as well. Should I just wait until tomorrow morning? ;-)

"Gigya encountered an error while validating itself. Please check watchdog and try later. If this message keeps appearing please contact gigya or file a bug in the gigya project issue queue." Thank you.

arnaudfischer’s picture

arnaudfischer commented

Well, I got up this morning and it worked :-) Thanks for the fix Matt; seriously.

Thomasr976’s picture

Thomasr976 commented
Version: 6.x-1.x-dev » 6.x-1.0-beta6

I am getting the same error but an using the latest version 6.x-1.0-beta6. Any advice?

andreic’s picture

andreic commented

I get the exact same error as in the description at the top but I fail to see how this is time related. Even if it is how do I check my server time settings on a shared hosting server? The physical location is in Canada. The website is http://www.biocera.ro and I simply cannot make gigya socialize active.

Any ideas are greatly appreciated!

kostajh’s picture

kostajh commented
Version: 6.x-1.0-beta6 » 6.x-1.0-beta9

I have the same error with the beta9.

lucashodge’s picture

lucashodge commented
Version: 6.x-1.0-beta9 » 6.x-2.1
Category: support » bug

My server was over 120 seconds out of sync and I was getting the following:

"403002 Forbidden. Request has expired"

I followed the instructions here from cPanel and all is now working:
http://forums.cpanel.net/f5/rdate-down-142077.html

ragavendra_bn’s picture

ragavendra_bn commented

getting the error on Gigya settings page.

The Gigya API and other settings not saving.

Version is: gigya-6.x-2.1

azinck’s picture

azinck commented

ragavendra_bn:

Do I understand you to be saying that you are getting the "validating error", AND none of the settings on the Gigya settings page are saving? When you make changes on the Gigya settings page and save them, then return to the settings page none of them are saved?