iliya1991

So after getting a response from my host provider I found out that the issue persisted only when trying to access this page from my network. I suspect that because I did extensive testing I ended up being blocked somewhere. What eventually resolved my issue was moving login link from /wp-login to /login. Not sure why this made a difference but after chasing this for a good portion of the day I am good, as long as it finally works.

Thanks again to Laszlo who pushed me to the right direction.

Thank you very much for quick and professional answer, it’s not something that I see every day!

As for your advice, I have reached out to my hosting provider support to check the issue. If the issue is on their end I will post here again for other people who might encounter the same problem.

And again, really appreciate the help!

• This reply was modified 4 years, 9 months ago by iliya1991.

Also, this is the debug log:

Hostname graph.facebook.com was found in DNS cache
*   Trying 157.240.9.18...
* TCP_NODELAY set
* Connected to graph.facebook.com (157.240.9.18) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /srv/disk3/3407694/www/nihulhit.com/wp-includes/certificates/ca-bundle.crt
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=California; L=Menlo Park; O=Facebook, Inc.; CN=*.facebook.com
*  start date: May 14 00:00:00 2020 GMT
*  expire date: Aug  5 12:00:00 2020 GMT
*  subjectAltName: host "graph.facebook.com" matched cert's "*.facebook.com"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
*  SSL certificate verify ok.
> POST /v3.2/oauth/access_token HTTP/1.1
Host: graph.facebook.com
Accept: */*
Content-Length: 0
Content-Type: application/x-www-form-urlencoded

< HTTP/1.1 400 Bad Request
< WWW-Authenticate: OAuth "Facebook Platform" "invalid_request" "Missing redirect_uri parameter."
< Content-Type: application/json; charset=UTF-8
< facebook-api-version: v3.2
< Strict-Transport-Security: max-age=15552000; preload
< Pragma: no-cache
< x-fb-rev: 1002216154
< Access-Control-Allow-Origin: *
< Cache-Control: no-store
< x-fb-trace-id: HfWp+m3hegu
< x-fb-request-id: AomYqndoefJJSkanas8McaI
< Expires: Sat, 01 Jan 2000 00:00:00 GMT
< X-FB-Debug: 9+pp6H3Rr4My9JNQCrRVYK04XO4vclk6w0xFoD8SrDMRVChU3Ji2dYfLO58kFg4FdS/HpLc4P0Vr+6Q16ezkVw==
< Date: Mon, 08 Jun 2020 13:41:28 GMT
< Alt-Svc: h3-27=":443"; ma=3600
< Connection: keep-alive
< Content-Length: 129
* HTTP error before end of send, stop sending
< 
* Curl_http_done: called premature == 0
* Closing connection 0
{"error":{"message":"Missing redirect_uri parameter.","type":"OAuthException","code":191,"fbtrace_id":"AomYqndoefJJSkanas8McaI"}}