Quite facebook or oauth error on server?

Question

Facebook

I set up authorization through facebook (not the first time I do this, but usually everything was in order).
On the local in development, everything is in order and works.
I deployed it to staging (not heroku), And this is what happens there:
-I click the link (login fb)
-Redirects to confirm the rights of the application (Which, in principle, confirms that the secret key is suitable)
-I agree, and I am transferred back to that page where I was, although it must be somewhere else. (i.e. sign in did not occur)
In the logs on the server

I, [2015-12-22T04:59:25.110938 #29694]  INFO -- : Started GET "/account/auth/facebook" for 195.88.124.212 at 2015-12-22 04:59:25 -0500
I, [2015-12-22T04:59:25.482880 #29694]  INFO -- : Started GET "/account/auth/facebook/callback?code=AQD-iva4slpiNn1YfqDf_tYTGA9N8BorpVX0dV-tCaCyVpHaBsgaj4fYdOAfZDITNl_GQRlwuJxdz4KE1hjkcZWyFanBhcoQELeBPw6BRCC8n2V6d8Tr3sPCl_HKandJKEKaEbQeIaOmkEuZ5lk9mOj9mqrqk03qkESLVmNAV5w2nnStbTwjD9CBxj03KcI0rnPmBWxdqyQWsnKwLX-iWjYMLIvXv-KtpLIkDk0w03xhcrUM43fOTorsSuSeSg3qBC9dzAzeQbBWzek_ljsYOX05tU3Zhj-Z3GjqYGAvsN5nEgAJqERb70Co3B-u81Mzk0JcmNrd47bctfemTDcv4ePX&state=7e68b0374b5c95bae05fbcaaf52ae841afc49a682791141d" for 195.88.124.212 at 2015-12-22 04:59:25 -0500
I, [2015-12-22T04:59:25.686525 #29694]  INFO -- : Processing by OmniauthCallbacksController#failure as HTML
I, [2015-12-22T04:59:25.687169 #29694]  INFO -- :   Parameters: {"code"=>"AQD-iva4slpiNn1YfqDf_tYTGA9N8BorpVX0dV-tCaCyVpHaBsgaj4fYdOAfZDITNl_GQRlwuJxdz4KE1hjkcZWyFanBhcoQELeBPw6BRCC8n2V6d8Tr3sPCl_HKandJKEKaEbQeIaOmkEuZ5lk9mOj9mqrqk03qkESLVmNAV5w2nnStbTwjD9CBxj03KcI0rnPmBWxdqyQWsnKwLX-iWjYMLIvXv-KtpLIkDk0w03xhcrUM43fOTorsSuSeSg3qBC9dzAzeQbBWzek_ljsYOX05tU3Zhj-Z3GjqYGAvsN5nEgAJqERb70Co3B-u81Mzk0JcmNrd47bctfemTDcv4ePX", "state"=>"7e68b0374b5c95bae05fbcaaf52ae841afc49a682791141d"}

I tried to go through the same application on Facebook in the development on the local. And everything worked out.
I tried to create another application on facebook and again this problem.