Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted February 22, 20187 yr Hey folks! I'm SO new to this and I'm trying to follow this guide: When I follow the instructions I'm still getting an error when I try to sign in directly to my site. Any ideas on what I could be doing wrong? Thanks! -James
February 22, 20187 yr Is the app still in development mode? You should be able to tell by looking near the top while you're viewing it:
February 23, 20187 yr Author Hi @Cemmos - No it's showing as live. I'm receiving this error: (See attached) I am using the domain as: www.thrivingmusicians.com I've tried thrivingmusicians.com, http://www.thrivingmusicians.com, and https://www.thrivingmusicians.com I've followed the instructions to the T so I'm trying to figure out where I'm going wrong? Thanks for the reply! -James
February 23, 20187 yr Interesting I've been testing this over the ;last day or two and I'm getting the same error unless I switch off Strict mode.
February 23, 20187 yr 2 hours ago, TheThrivingMusician said: Hi @Cemmos - No it's showing as live. I'm receiving this error: That specific error means you need to add your domain name to the App Domains portion under Settings > Basic: As for strict mode (different error), go to Facebook Login settings under the PRODUCTS section and enter the below URL in the Valid OAuth redirect URIs portion: https://www.YOURDOMAIN.com/applications/core/interface/facebook/auth.php For App Domains, you don't need http, but for the OAuth redirect you need to use it (I use both http and https in the OAuth field). Strict Mode is going to be forced in March, so best to get it over with now.
February 24, 20187 yr Author Hey @Cemmos thanks for the reply! I've tried everything suggested here and am still getting error messages. Here's what my setup looks like: I apologize if I'm missing something - I'm definitely not experienced in this stuff. Thanks again for taking the time
February 24, 20187 yr And the SSL cert that is on your site is classed as insecure because the subject alternative name it contains (*.cloudfront.net) doesn't match up to your site name....so Facebook are likely to reject that too.
February 24, 20187 yr Author @Nathan Explosion I have no idea how you got to any of that lol is there a way I can fix it? 2 hours ago, opentype said: Looks like your site is http and your oAuth redirect URL uses https. @opentype tried to put https across all of them but no luck
February 26, 20187 yr Author Hi guys - @Nathan Explosion still can't get this resolved. Do you have any suggestions on how I can fix this? I've submitted support request as well to the team but their suggestion didn't work either.
February 26, 20187 yr Well, you need to sort out your SSL problem - the SSL certificate used by your site is invalid for your site, it's as simple as that. Contact your host for assistance? Contact cloudfront for assistance? I can't help you any more than that.
February 27, 20187 yr Author @Nathan Explosion When I contact GoDaddy, what do I need to explain? I'm not familiar with the terminology (SSL is out of my realm of understanding) so I want to ensure I'm as informed as possible. Sorry to keep bugging ya I'm completely new to all of this
February 27, 20187 yr Quote Dear GoDaddy Support, The SSL certificate on my site <include site url> doesn't match the name of my site, and therefore is not a valid SSL certificate for use and browsers etc are rejecting this as insecure. It's most likely the cause of an issue I have with integrating Facebook login on my site. Can you help please? etc. etc. etc. Please don't tag me again - I seriously cannot help you any more than this. Get the SSL situation sorted out first, then revisit the Facebook issue if it's still not working.
February 28, 20187 yr Author Sorry man... You were just speaking a lingo I didn't quite understand so was looking for clarity.
May 1, 20187 yr Hello @TheThrivingMusician co-representative! Any news regarding the issue with Facebook login? I have this injury now and nobody can support over 6 hours yet.
Archived
This topic is now archived and is closed to further replies.