Sorry for my english...
I'm using firebase authentication for first the first time.
I discovered that I cannot create/connect to accounts if my network automatically selects dns and does not use google dns(8.8.8)
I do not understand how my application will work (just I think that not everyone uses this DNS).
Is there any way to fix this so it works for everyone?or is it work correctly?
without google dns
with google dns
Please check any that applies to you,
Is your ISP is blocking DNS queries to Google Authentication servers,
Are you using a proxy, if yes try disabling it, and then try again,
Check the error returned in auth callback when you are requesting authentication,
Check stack trace in LogCat of Android Studio.
Related
I am attempting to integrate my NEST devices with Home assistant so following these instructions: https://www.home-assistant.io/integrations/nest/
I have created a google cloud project, enabled "Smart Device Management" and "Cloud Pub/Sub" APIs, configured OAuth Consent screen which is now in production and configured OAuth Application Credentials - which generated a client ID and Secret.
I have also paid the $5 for the device access console so can access this screen:
However when I go through the process of creating a project, inputting the OAuth Client ID and submitting, it will try for a few minutes and then get the following error:
Really not sure what I am doing wrong. Any help would be greatly appreciated.
I just encountered the same thing. I don't think it's you. The endpoint to actually create the project is returning a 503-Service Unavailable response. Likely a temporary issue.
I am encountering an issue as well
Marko seems to have discovered that it is on them right now
I had the same issue yesterday. This morning I logged out of the Drive Access Console and then logged back in with the same gmail account and my project was there.
I had this issue as well and I finally figured it out.
After spending more time than I care to admit on it, I realized I could create a project if I skipped the "OAuth Client ID" step. I was then able to go into the project and add the Client ID from there.
What happened is that I had been copy/pasting the Client ID directly from the Google Cloud Console. For some reason, copy/pasting directly from Google Cloud Console adds extra spaces to the start and end of the Client ID string. After I got rid of the extra spaces, I could create projects as expected.
I wish the errors were more descriptive.
At some point yesterday (25/08/21) we started getting errors accessing any documents held in firebase storage.
I can see them in the firebase console, but if I try to view them I get an error.
The exact error depends on which browser but it was along the lines of:
This site can’t provide a secure connection
firebasestorage.googleapis.com uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
After a bit of digging, it seems specific to the BT ISP in the UK, and caused by their BT Web Protect product. If I disable Web Protect from my BT account I can access the urls again, but obviously that is not a solution I can offer to our customers. (Similarly, if I connect via a mobile hotspot on my phone, all is well)
I contacted BT who suggested I email saferbrowsing#bt.com and ask them to unblock it, so if anyone else is having this issue please do the same - the more noise on this the quicker the resolution hopefully.
To the Firebase team - is there anything you can do from your side to expedite this? Firebase Storage is a huge part of our product and it simply doesn't work for anyone on BT at the moment.
Thanks
John
I got a reply from BT this morning saying that firebase has been unblocked, and all seems to be working again. phew!
Several ISP's have anti-spam detection, this is used to hunt down new spikes of traffic that can seem suspicious. If you are getting faults from users from a specific ISP or geolocation, this can indicate outages or blocked requests.
The best solution is to always call their technical support and discuss what could have triggered it and remove any potential blocks from happening again.
I have been facing a issue while connecting database via Meraki VPN when working remotely.
When working from office it does not ask me to login using Azure account. Because we do not have one. However, it keeps asking to login and then when I do so it says your account does not have valid subscriptions while there is no need of that.
I have done all troubleshooting steps mentioned on Microsoft reference doc, turned of firewall Follow the ink to see the image. Added inbound rule and whatnot.
Is there any other way to deal with this problem. Any help would be appreciated
I got the solution for this by working with our IT department. My IP address was not whitelisted by my company. After whitelisting, I could login in SSMS vis VPN.
Tip:- Before trying to troubleshoot by following steps given by Microsoft, make sure your personal device is registered as well with your IT department.
I am having trouble getting the Google Vision Sample App to have a successful API request.
I made sure the billing, API-key, were correct. I even tried using a browser key and service key, but had no luck.
The error coming back is:
failed to make API request because of other IOException Unable to
resolve host "vision.googleapis.com": No address associated with
hostname
If you have any ideas, I would surely appreciate it.
Solve:
Something was wrong with the Wifi on my phone. I think it was suffering from being off. I also changed the API-Key to Browser which is not the ideal solution, but will do for now.
Anyone is having problems retrieving Likendin connections with new apps?
With old apps my hybridauth app is retrieving connections just fine. While with new apps (I created 3 different apps) I keep getting Access to connections denied
When authenticating I got the correct scopes on likedin login screen(r_basic_profile, r_network, w_messages, r_emailaddresses)
Im using free plugin http://wordpress.org/plugins/wp-social-invitations/ which uses hybridauth
This is a recent problem with the linked. They have stopped providing member connection in their recent API change. Now you have to obtain a partner certificate in order to access member connection information. Even my production application has stopped this functionality to work. We might be removing linked from our application as it is of no use now with so much of restrictions.
Linkedin api changed recently, that's the reason scopes are not longer working
The get connections API in linked in has been deprecated follow this link to get the API' that are allowed as part of developers program right now.