I have a question about Firebase Authentication for custom domains. I added the dns record and tried to verify the email after 24 hours, but when I click the link I get a 404 error. How can I fix this problem?
Thanks for your help!
Related
I have purchased the domain name as domain-name.in.net from bigrock. But adding custom domain name in firebase, it only considering in.net and not considering domain-name.
Any solutions guys?
Due to above issue i am unable to verify ownership in firebase.
In the hosting section of the Firebase console, enter in the custom domain name of "domain-name.in.net". In your hosting provider add the A record with the IP address. Wait up to 24 hours for the record to propagate.
The subdomain should now correctly go to your Firebase app. Note, if you're concerned about the console saying "needs setup", ignore. It always says that and seems to be a bug with Firebase.
I am trying to verify domain for email template in firebase.
it keep failing for a week now.
Please help me. TIA
I am trying to run this sample firebase project, but I keep getting this error in the browser console.
Lf {code: "auth/unauthorized-domain", message: "This domain (mail-demo-fcm.firebaseapp.com) is not…se console -> Auth section -> Sign in method tab."}
code: "auth/unauthorized-domain"
message: "This domain (mail-demo-fcm.firebaseapp.com) is not authorized to run this operation. Add it to the OAuth redirect domains list in the Firebase console -> Auth section -> Sign in method tab."
I have enabled Google in Authentication -> Sign-in Method as sign-in providers.
Am I missing something ?
A little guide will be helpful.
And I am using Firebase's free plan.
You need to add domain mail-demo-fcm.firebaseapp.com to
Authentication menu in Firebase at Authorized domains
Below the sign-in method section, there is a Authorized domains section. I think you need to whitelist your domain there.
The authorized domains section might also be in the settings page. Here is a screenshot:
If localhost is already in the list of domains, make sure you're accessing your test app via http://localhost/ and not http://127.0.0.1/
Enable localhost and your own domain that you are using in the firebase console.
Login into firebase
Click on the authentication tab
Add authorized domains
The solution from #alkas was helpful, but I also needed to explicitly enable the Sign-in providers for my app (Email/Password, Google, etc) for this error to go away
In my case, I found the problem after deleting localhost from my "Authorized domains".
So I just add it (localhost), so everything is okay !
-localhost, because I'm on local,
-project_name.firebase.com and project_name.web.app when app deployed.
Thanks !
Open Firebase
Go to console
Open your project
Go to Authentication
sign-in-method
Add domain
Try it!
In my case it's working
I’ve been trouble shooting this all weekend and not finding any solutions. I’m trying to setup webhooks for Mailchimp and CiviCRM 4.6.1 through Wordpress 4.3.1.
The mailchimp settings panel in CiviCRM provides the web hook address as:
Webhook URL - http://<domain>/?page=CiviCRM&q=civicrm/mailchimp/webhook&reset=1&key=2345
Anytime I request the url in a browser window it returns a ‘null’ response. When I paste it into the Mailchimp webhook setup Mailchimp gives me a 403 error (“We couldn't verify the URL is working. Please double check and try again. HTTP Code: 403”).
I’ve tried to ensure that step 3 of the Veda Consulting instructions https://github.com/veda-consulting/uk.co.vedaconsulting.mailchimp was handled:
Make sure webhook url is accessible to public. If not, just make sure anonymous / public user has “allow webhook posts” permission.
but in wordpress settings (https://en.support.wordpress.com/webhooks/#what-would-i-use-something-like-this-for) I can’t find a webhook tool. Am I missing something? Is this from an older version of wordpress. I found the Hookpress plugin but it has a warning that it hasn’t been tested with the current version of wordpress.
Whoever can tell me how to get this webhook working for Mailchimp I would greatly appreciate it, thanks!
It's a civiCRM setting, not a Wordpress setting.
This comment from the developer reveals a URL to use to expose the permissions panel:
You can enable 'allow webhook posts' permission in wordpress access control by navigating to
http:///wp-admin/admin.php?page=CiviCRM&q=civicrm%2Fadmin%2Faccess%2Fwp-permissions&reset=1
Reference: https://github.com/veda-consulting/uk.co.vedaconsulting.mailchimp/issues/172#issuecomment-162478431
Not a totally satisfying answer but I ran my webhook link through firebug and it always returns an ok 200 response from the server.
I corresponded with Mailchimp and they confirmed that from what they can see there isn't an issue with the webhook I'm using. They suggested I whitelist their API's IP addresses but my hosting doesn't allow whitelist IPs. I've gone back to Mailchimp but it's looking like the fate is sealed on this one.
If not, just make sure anonymous / public user has “allow webhook posts” permission.
This refers to permissions configuration in your CMS.
In Drupal and Backdrop, this is configured under Admin > People > Permissions (admin/people/permissions) where you must grant "allow webhook posts" permission to the "anonymous user" role.
In WordPress, a similar pattern should allow you to grant the "allow webhook posts" capability to the "Anonymous User" role.
In Joomla, I think the Veda MailChimp plugin doesn't check permissions on that webhook callback.
I had to debug a site which hadn't had this configuration set today, and the HTTP response code for the callback to MailChimp was 500 when permission not granted, and 200 when it was granted. That might help debug your own situation (you should be able to duplicate this simply by GET to the webhook callback).
I changed my site to HTTPS but my PayPal now does not work.
It takes me to a page that with an invalid request error and a return to merchant button.
Is there something I need to change, using paypal rest
Thanks
You may file a ticket to the PayPal MTS guys here:
https://www.paypal-techsupport.com/
With detailed errors and maybe access logs, you will get an solution there