Datastore Backup Error message - Domain isn't using G Suite - google-cloud-datastore

I want to take regular backups of datastore. I tried opening 'Datastore Admin Panel' but I keep getting this error message.
Server error Sorry, you've reached a login page for a domain that
isn't using G Suite. Please check the web address and try again.
What steps should I take to fix it, I have no clue right now to take any steps. Thank you so much!

Admin Panel is deprecated. You can do backups using the managed export and import service.

Related

Unable to Connect to Box API in R

all. I am trying to set up boxr to read files from Box's API.
The set up seems pretty simple. I created a Box app. I then copy/pasted the client secret and client ID into box_auth()
library(boxr)
box_auth(client_id = "<placeholder>", client_secret = "<placeholder>")
When I do this I am taken to a new page that says:
There seems to be a problem with this app.
Error: redirect_uri_mismatch
Because there are so few steps, I am a little lost on what could be going wrong.
Advice is appreciated.
Ran into this same issue after months of boxr working as expected - the steps and explanation outlined here resolved the issue on my end.
Going to the dev console for your Box account, and then to the "Configuration" tab, add http://localhost:1410/ as a Redirect URI:

Airflow webserver redirects to nowhere

I'm trying to test a DAG I wrote in Astronomer/Airflow but I'm getting a really peculiar behavior that has me totally stuck.
Airflow's webserver comes up, and then after login as admin it redirects to http://localhost:8080/home which doesn’t appear to exist.
The specific error I get in the browser is ‘too many redirects’. I’m sure something is wrong in my configuration, but it’s not obvious (to me) what. Can you suggest steps for further diagnosis?
Thanks,
Keith
I thought I would share the resolution of this problem in case anyone else encounters it.
This problem came about while developing a DAG to test a part of our pipeline. The repo I was working with used a Dockerfile which was designed for automated testing and was not suitable for a DAG. Once I reverted to the stock Dockerfile the problem went away and I can now load localhost:8080/home just fine.
I have had similar issues when the username or the password is incorrect. I am expecting you are either entering wrong login credentials or your configuration is checking some external authentication server and it is not configured correctly.

Why do I keep receiving an error when initializing my firebase project while setting up firestore?

I am learning how to set up and host a webpage through firebase, and when I attempt to initialize the project (by running firebase init in the firebase CLI) every time I reach the firestore setup portion, it always results in the same error.
It looks like you haven't used Cloud Firestore in this project before. Go to https://console.firebase.google.com/project/resume-site-599bc/firestore to create your Cloud Firestore database
When I copy and paste the link, it brings me to the firebase console page and says "your action was forbidden" no matter what I do. I have tried to go into the console settings and made sure all of the correct APIs are enabled. But there seems to be little help when I tried googling the issue.
Thank you.
I had the very same and error and fixed it with #MS29's method. More verbose for simplicity:
In the Firebase Dashboard, go to Project Settings -> General
Set "Default GCP resource location" again.
After that, the Firestore can be found again.
So even though I already had the project created and I created my Firestore database, my: Default GCP resource location didn't select properly when creating the project. Once I fixed this, it had no problem connecting to my database.
I've faced the same problem with Angular 14.2.0 and firebase 19.14. The solution for me was as follow:
I've checked the project list by using firebase cli:
firebase projects:list
There I noticed that the Resource Location ID wasn't set for any reasons. So I opened the settings of my firebase-project using the console (https://console.firebase.google.com/) and on project settings tab u can set the GCP. That's it
Look like you haven't create project on your firebase account
So firebase ask you go into the link to create project.
For the problem of "your action was forbidden",
it seem to be the problem of multi google accounts.
Google still work quite bad on multi accounts sometime.
You can try access the google firebase console main page by the link below.
https://console.firebase.google.com/u/0/
https://console.firebase.google.com/u/1/
The last number is the number of user. You can change it if you have many google accounts.
P.S. The user order will change if you logout.
Most likely that you don't have the project created in firebase. Either create a new project by going to
https://firebase.corp.google.com/u/0/
or enable Firebase for an existing GCP project by choosing that project in the add project page
it's happening same to me too, but in my case:
I already created the database at Firestore Cloud *at their website
for now I'm still troubled with it, if I have solution.
#update
hello, I'm in bandwagon when it comes to this problem: [firebase init firestore not work with existing project]
I'm using firebase CLI version 10.6.0
but somehow I manage to deal with it, here's my solution/timeline:
I install using firebase login --no-localhost because encounter problems with firebase login
encountered with errors: cannot install firestore but hosting part can.
try to reset database, created again but still get error: cannot install firestore
then I logout, then login using ONLY firebase login, not the firebase login --no-localhost
bang! solved!
hope it helps~

Requested site does not appear to have claims enabled or the Login Url has not been set

i am currently getting information from my company's sharepoint page and display it on my asp.net project. I am using ClaimClientContext for authentication, and of course in my local host it is working fine.
However, when I publish the site and place it on my server the following error occurred: The requested site does not appear to have claims enabled or the Login Url has not been set.
The error is pointing to the Url which i have stated in my code:
Using ctx As ClientContext = ClaimClientContext.GetAuthenticatedContext("https://abc.sharepoint.com/team/Wiki/")
Any idea on how I can overcome this error? Do let me know if more information is needed, and i will gladly provide. Thank you.
Ok. After struggling with this for quite a bit now, I was able to resolve the issue. Its something to do with oAuth2 not supporting old protocols.
You can resolve with the below power shell commands
Connect-SPOService -Url https://<yourdomain>-admin.sharepoint.com -credential <adminIDwithElevatedPrivileges>
Set-SPOTenant -LegacyAuthProtocolsEnabled $True
You might have to wait for sometime after running this command.
Hope this helps!

How Do I Remove This Error in Firebase: "This domain is already in use."?

I'm trying to add a custom domain to an existing project but keep getting the error that "this domain is already in use." I'm not using this domain anywhere else in any other project.
There is only 1 other forum post (http://grokbase.com/t/gg/firebase-talk/165r5n78nq/firebase-domain-is-already-in-use) about this error but following the step provided leads to zero results.
If you are getting that error it means that you're already using the domain in a project. You probably deleted the project but did not disconnect the domain before it was shut down. In this case, you can either wait for 10 days from when you deleted the project for it to be removed or,
you can restore the project by going to the Firebase IAM & Admin console click on projects pending shutdown.
Then proceed to disconnect the domain from the project like you normally would. Now you can use that domain again with no problem.
Go to https://console.firebase.google.com/iam-admin/iam/project and click on 'Projects Pending Deletion" click Restore. Then go to https://console.firebase.google.com/project/YOUR-PROJ-ID/hosting/main and delete the domain connection(s).
That should free the domain up for a new SSL cert.
if you are using appname.page.link make appname uniqe

Resources