500 Server Error - Dangerously writable - error/auth googleoauth2/couldnotgetgoogleaccesstoken

[rabser]

500 Server Error - Dangerously writable - error/auth googleoauth2/couldnotgetgoogleaccesstoken

[mouneyrac]

Hi Alfonso,
it looks like your server detected facebook_redirect.php has been writable and then fail to server the file of a security reason that only your host knows (which doesn't mean your host is wrong) - this is obviously just an assumption.

I'm wondering if I didn't push the rep file with wrong permission, I'll have to check but anyway you should be able to change the permission of your file (in the case the issue is related to permission).

[sintjago]

Thanks. I'll check on that. Not sure if this helps, but this showed up on debugging mode.

Google
Debug info:
Error code: couldnotgetgoogleaccesstoken
Stack trace:
line 392 of /auth/googleoauth2/auth.php: moodle_exception thrown
line 88 of /login/index.php: call to auth_plugin_googleoauth2->loginpage_hook()
Output buffer:
Notice: Trying to get property of non-object in /home3/cursosct/public_html/moodle/auth/googleoauth2/auth.php on line 167

Facebook
Debug info:
Error code: couldnotgetgoogleaccesstoken
Stack trace:
line 392 of /auth/googleoauth2/auth.php: moodle_exception thrown
line 88 of /login/index.php: call to auth_plugin_googleoauth2->loginpage_hook()
Output buffer:
Notice: Undefined index: access_token in /home3/cursosct/public_html/moodle/auth/googleoauth2/auth.php on line 175

[jowhiting]

Hi sintjago did you manage to sort this out as I am having exactly the same problem?

[maliky]

maybe it has to do the oauth.so module not been called by your php.ini file. If so add
'''extension=oauth.so'''
in your php.ini (if oauth is installed)

[jowhiting]

Thanks for this but still no joy.

Jo

On 4 December 2013 19:30, maliky [email protected] wrote:

maybe it has to do the oauth.so module not been called by your php.ini
file. If so add
'''extension=oauth.so'''
in your php.ini (if oauth is installed)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-29836847
.

http://facebook.com/varndean_Find us on Facebook
http://facebook.com/varndean http://twitter.com/varndean__Follow us on
Twitter_ http://twitter.com/varndean

[maliky]

I'm having this problem only on bluehost.

The same install with another host (ovh) is ok.

So It should be a host, php, config related issue.

[maliky]

Check that your php local session.save_handler is set to file and not user. If not set to file, uncheck "Use database for session information" in /admin/settings.php?section=sessionhandling ... It may help... did not for me but still who knows...

[jowhiting]

Thanks for this I will try it out

Jo

On 18 December 2013 21:03, maliky [email protected] wrote:

Check that your php local session.save_handler is set to file and not
user. If not set to file, uncheck "Use database for session information" in
/admin/settings.php?section=sessionhandling ... It may help... did not for
me but still who knows...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-30880424
.

http://facebook.com/varndean_Find us on Facebook
http://facebook.com/varndean http://twitter.com/varndean__Follow us on
Twitter_ http://twitter.com/varndean

[maliky]

any news?

[jowhiting]

Thanks for getting back to me on this. Still no joy I'm afraid

Jo

On 13 January 2014 19:33, maliky [email protected] wrote:

any news?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-32202515
.

http://facebook.com/varndean_Find us on Facebook
http://facebook.com/varndean http://twitter.com/varndean__Follow us on
Twitter_ http://twitter.com/varndean

[kyledef]

@maliky I'm on hostmonster (which is basically similar to bluehost) I'm having a similar problem. Did you get this library to work on other host providers?

I am seeing the exact errors highlighted by @sintjago for both attempting google and facebook authentication.

[mouneyrac]

Quickly googling at the initial @sintjago report, "error 500 Dangerously writable", it seems that some hosting company forbid to access files when their permissions are too high. Try to put your files in mode 644 (use 'chmod' command in a terminal) and check that they are own by your web server (use 'chown').

When running Moodle on a hosting company (often a bad idea from my experience, imo a VPS should be the minimum to run Moodle), you can have a look a too: http://docs.moodle.org/24/en/Security_recommendations#Running_Moodle_on_a_shared_hosting_environment

Note that the recommended way to setup your files is described there:
http://docs.moodle.org/24/en/Security_recommendations#Running_Moodle_on_a_dedicated_server

[mouneyrac]

If anyone resolve this issue, confirm the solution as I'll put the solution in the documentation/FAQ. Or even better, contribute to the FAQ. In this case mention you modified the FAQ here, it's nice for me to know that it has been done.
Thanks guys.

[fcorey]

I am using Moodle 2.4.5 on a shared server hosted by hostgator.com. Sign in with Google never worked (error/auth googleoauth2/couldnotgetgoogleaccesstoken) but Facebook worked for a few hours and now I get the exact same error. The authentication provider sent us a communication error. Please try to sign-in again.

More information about this error

I have opened a Ticket with Hostgator and hopefully they can get to the bottom of it. If they come up with a solution I will post it here for other people using shared servers. One thing I know for sure is Bluehost and Hostgator both use CPANEL.

[mouneyrac]

couldnotgetgoogleaccesstoken error now returns a much better error message when you enable the debug mode in the Moodle admin. I am closing this issue as it is an old/dead one. Please open a new issue if needed.

[maliky]

I moved form a shared hosting environnement on bluehost to a VPS on OVH hoping it would resolve my connection problem but not. Althoug I do not get the couldnotgetgoogleaccesstoken but the faileduserdetails.
Could it be because I don't have a certified certificate on my IP ? If so my students will have to way some more until I can pay and install that.

[cme0848]

I had the same error "Error 500 - Dangerously Writeable" running on a shared server (HostMonster). Then I went to my server log (which can be easily accessed on a shared host like Bluechip, Hostgater, Hostmonster,etc). The error stated
[Mon May 01 11:37:00 2017] [error] [client 23.24.136.177] SoftException in Application.cpp:256: File "/home4/<DOMAINUSER>/public_html/CRM/index.php" is writeable by group [Mon May 01 11:37:00 2017] [error] [client 23.24.136.177] Premature end of script headers: index.php

I changed the permissions of the files inside of the CRM folder to 755 and the issue was resolved. Hope this helps