I want to build some web apps using sanity. Initially I watch videos in youtube this. In video everything go well. But when I try console get me error:
You're setting up a Sanity.io project! We'll make sure you're logged
in with Sanity.io. Then, we'll install a Sanity Studio for your
project.
Press ctrl + C at any time to quit.
We can't find any auth credentials in your Sanity config
log in or create a new account
| Fetching providers... Error: connect ECONNREFUSED 35.241.31.122:443
After I some create simple project sanity and run command sanity init --template get-started --project 8tbt7v3g --dataset production --provider google. It is too get me this error. I am trying use lantern vpn. Vpn work well but this no work. Please help me. I didnt do anything half month.
Thanks
Related
Being kinda new to React and everything clientside related, I am trying to build a Electron application with React.
At this point I can't tell if that's a good idea, but I wanted to try it.
Currently it works fine (see Github).
However I now wanted to add #react-oauth/google to give users the option to sign into their Google Account to allow the application to access their google drive and I'm struggling with that.
See the testing_auth_2 branch for that.
I enabled the drive-api in GCP and created credentials for a web application, adding http://localhost and http://localhost:3000 as authorised Javascript origins.
Now it works, but only when I start it as a webpage (npm start in my Github)
Starting it as an electron app failes, probably because electron doesnt run under localhost somehow (npm run electron:dev in my github code).
I tried creating Desktop and ios credentials since those dont ned authorised origins but the error persists.
Steps to recreate:
Enable drive api and create credentials in GCP
clone git#github.com:Urr4/electron-archive.git
checkout testing_auth_2 branch
Replace XXX in index.tsx with the client_id
The Google login should work using npm start, but not using npm run electron:dev
Any help is appreciated
I am developing an Excel JS TypeScript React addin with VS code. I deployed my add-in to Azure and it worked fine. Now I wanted to start a localhost for development purposes but all of a sudden I got this message:
I am posting this question, so clearly there is no issue with my internet connection. Furthermore I tried to surf to the https://localhost:3000 URL and it gave me a blank page with this text:
Cannot GET /
I tried to use the Yeoman Generator to create an empty project because I thought I maybe messed up the webpack.config.js file or the manifest but installing the boilerplate React TypeScript Excel add-in did not get me anywhere neither because even the npm install command did not succeed. I have no idea how to tackle this.
many thanks in advance.
Thanks to Eugenes feedback I dug back into the Yeoman generator and generated a new boilerplate react project and found that a package.json.lock file was blocking npm install. After I removed the package.json.lock file I was able to perform the npm install command and then I compared the manifest file from the newly created boilerplate project to the actual project and I saw that I accidentally replaced the https://localhost:3000 by http://localhost:3000. So if you do not attach the s in HTTPS, it does this strange error. the reason I replaced it is because for production I use another URL.
Most likely something is preventing access to the URL. It can be local firewall software, VPN software, proxy configuration or Metered Connection setting.
Be aware, to run web add-ins you need to generate and install a valid certificate to use https. Office Add-ins should use HTTPS (not HTTP) even when you are developing, because Office clients require add-ins and webpages to come from a trusted and secure location. If your add-in fails to load within an Office client, it may be because you haven't installed (trusted) the certificate that the Yeoman generator for Office Add-ins provides. To make sure a valid certificate is used, try to navigate to the html file in any web browser.
Also you may try to switch to another network connection and try again.
I'm really struggling with deploying my Strapi+React App. I am more of a frontend developer and not so familiar with what happens server side.
So, I have my own server that I want to deploy to, but I can't find any instructions on how to do it....
My Strapi is fine and running on port 1337 and I did npm run build in React to deploy the app in a folder that my domain points to and I get the following error:
Error: {"graphQLErrors":[], "clientErrors":[], "networkError":{}, "message": "Failed to fetch"}
and in the console:
POST https://xx.xxx.xx.xx:1337/graphql net::ERR_SSL_PROTOCOL_ERROR
When I do npm start and then open http://xx.xxx.xx.xx:3000, I get a (partially) blank page and these errors in the console:
GET https://xx.xxx.xx.xx:3000/static/js/bundle.js net::ERR_SSL_PROTOCOL_ERROR
:3000/favicon.ico:1
GET https://xx.xxx.xx.xx:3000/favicon.ico net::ERR_SSL_PROTOCOL_ERROR
So I guess it has something to do with SSL? And I don't know how to fix this...
Will you need any code to help me?
Thank you in advance!! I really appreciate any help!
I've been trying to install and setup the ASK CLI for a days now. I've followed the setup instructions and was able to install it. Whenever I try to run the ask init command and choose the "No. Skip AWS credentials association step.", a browser opens up and asks me to login to my developer account. I enter my credentials and just get redirected to a page that says unable to connect (Here's the link: http://127.0.0.1:9090/cb?code=ANjcJMpKRGqoqrSbiHdX&scope=alexa%3A%3Aask%3Askills%3Areadwrite+alexa%3A%3Aask%3Amodels%3Areadwrite+alexa%3A%3Aask%3Askills%3Atest+alexa%3A%3Aask%3Acatalogs%3Aread+alexa%3A%3Aask%3Acatalogs%3Areadwrite&state=Ask-SkillModel-ReadWrite).
I also tried using the ask init --no-browser command. I paste the generated url to a browser (I've tried Google Chrome, IE, Edge and Firefox and so far Firefox and IE works well). It gives me an authentication code but when I go back to the terminal, it's just frozen. I can't paste anything to it. I always get stuck at this point.
The reason I'm choosing "No. Skip AWS credentials association step." is because my skill endpoint is hosted as a web service in Azure and not using AWS Lambda. Am I missing anything? There were no errors in the installation process. I installed nodejs and git correctly. When I do ask --version in the terminal, the result is 1.4.7.
Does the ASK CLI not allow the skipping of the AWS profile setup?
A few details to make it clearer:
OS: Windows 10
Node JS: v10.13.0
NPM: 6.4.1
Git: git version 2.19.1.windows.1
ASK: 1.4.7
(I also found someone who experienced the same problem: ASK CLI INIT not working)
I am receiving an error on Azure while getting it to build.
I have a react app and my azure is connected with bitbucket. So when I upload the changes to my bitbucket the Azure starts building and deploying the changes and fail with the errors in the following screenshot. I am not sure what is happening to it because I am new to Azure. Please guide me, guys! Thank you.
Note: I have received the same kind of error on my windows env laptop when I build my react app locally, But I haven't received it on my Linux environment pc. Could it be possible that the files didn't copy properly when I tried to move the project through pen drive?. On my windows laptop, I receive this kind of error on npm run build but when I run the npm command three times it satrts building properly on the third time without any error.