I am developing a web-app which will manage user page posts etc,
My app in Facebook developer console is in development mode, but when i try to login in http://localhost then it gives error that facebook login does not allow http but i have to use https protocol.
Any solution to test facebook login in localhost with http ? or
Any idea to convert http to https in localhost?
I tried ngrok that converted http to https but facebook developer console said it is suspicious kinda link and refused to accept;
I am using a npm pakage react-facebook-login,
I will shift to pure code of facebook sdk if that will solve problem.
This is a solution I found for create-react-app. https://create-react-app.dev/docs/using-https-in-development/
Make sure you use the right terminal and it works. For instance, I started dev in the cmd line (set HTTPS=true&&npm start).
The downside is you still will get not secure warnings in the browser but the errors with the FB.login or similar from Facebook login packages went away. Hope it helps.
I am developing a web app with Facebook integration and I can't figure out why I can't test the login function locally. I have looked through the answers here (How to Test Facebook Connect Locally) and have tried to follow the steps of having the app in test mode, setting the site URL and the domain.
Based on FBs documentation here: https://developers.facebook.com/blog/post/2018/06/08/enforce-https-facebook-login/
I should be able to use http for localhost development, but I get the error
The method FB.api can no longer be called from http pages. https://developers.facebook.com/blog/post/2018/06/08/enforce-https-facebook-login/
and can't log in. Below are pictures of my app settings (including an indication it is an app in 'test mode').
So this is really only a half answer, but it seemed easier for me to just force https for my local development using mkcert (https://github.com/FiloSottile/mkcert). After creating local certs I updated my site URL to say https://localhost:8080 and I am able to log in without issue.
I've got a clients site that uses Google Cloud Run and I need to implement some redirects as they have both www. and a non www. version of the site simultaneously.
https://www.example.com
https://example.com
I would like to setup a redirect so that it goes from www. to the non www. version. I know I can't do this at DNS level for this type of redirect so am looking at doing it at a server level. I've checked for documentation on this on Google Cloud run and can't seem to see anything relevant. I've never worked with a client site that uses cloud run before, but have a good idea of how I'd go about doing this on a website that uses Apache or Nginx.
Does anyone know if there is a specific file where I should be implementing redirects within the Cloud Run setup?
Thanks,
Adam
You should do this in the code. For example if you were using Python with Flask, you can implement it in your #app.before_request
In Netlify I have tried and even upgraded the paid plan with their community forums reference. But later found that they are not supporting wildcard subdomain configuration.
For the basic level subdomain with one-click app setup, Netlify is good. Except for wildcard domain it's a best to configure your frontend apps.
For the basic level subdomain with one click app setup Netlify is good. Except wildcard domain its a best to configure your frontend apps.
I am developing a website which uses the Facebook login. Now, I want to be able to get this to work both in my production environment, as well as in my development environment.
On Facebook, I can give ONE site url, which Facebook can redirect to. This worked great during my development phase, but now I want it both to work in production, but also while developing my solution.
I guess one way would be to run my application on the local IIS with my domain-navn and change my hosts file, but that can't seriously be the most easy solution!?
- What is the easiest way to get it to work in both environments?
Update: As of 2018 the path to this setting is now Products > Facebook Login > Settings > Client OAuth Settings the rest of this answer is still valid.
There is a better way. You just need to add valid callback URL's for your localhost to Settings > Advanced > OAuth Settings.
This method allows you still have your production website URL while allowing oauth from dev, staging, production, etc.
After I have worked with this for ~6 months, I have found a solution which works really well, based on the other two answers.
In Facebook I add two apps:
Production app
Dev app
Then, in my web.config app settings I have:
<!--Prod-->
<add key="_FacebookApiId" value="id"/>
<add key="_FacebookApiSecretId" value="secret_id"/>
<!--Dev-->
<add key="FacebookApiId" value="dev_id"/>
<add key="FacebookApiSecretId" value="dev_secret_id"/>
Which of course is read through a helper-class.
Then it works seamlessly on both production and localhost, and both myself and my team is happy.
I have the same problem.
The only solutions I have found are:
yes... edit the host file on your local machine: How to Test Facebook Connect Locally
create another Facebook app only for development purposes: Facebook Oauth on localhost for testing during development (the blog is about Rails but the solution to use different apps depending on the environment is still valid for other languages)
Facebook only allows localhost OAuth redirects when your app is in development mode. This means you can't run your application in production and perform local development tests.
Instead, you need to create a test variant of your app. Head to https://developers.facebook.com and view the dashboard for your production application. Click the drop-down menu at the top-left and choose Create Test App.
This populates a test application with almost the same settings as your production app. However, it gives you a new app ID and app secret, so you'll need to toggle these settings when running in development mode (as other answers suggest).
Here's some further info on test apps: https://developers.facebook.com/docs/apps/test-apps/
Following the advice in this answer, it will work if set the Mobile URL to be your development domain (ie. localhost) and the Site URL to be your production domain.
The updated way.
In the App Dashboard, choose your app and go to Products > Facebook
Login > Settings. Under the Client OAuth Settings, enter your redirect
URL in the Valid OAuth redirect URIs field for successful
authorization.
Go to https://developers.facebook.com/docs/facebook-login/web for more info.