gmailr authentication fails, after a fresh installation of Debian, only on one of my systems.
I have a script that run fine on two remote machines, but fails on my local machine.
I use this for authentication:
gm_auth_configure(path = "~/.credentials_main_mail.json")
gm_auth(email = "natsisthanasis#gmail.com",
cache = "~/.secret_main_mail")
print(gm_profile())
On my local machine, I get the error:
Error: Can't get Google credentials.
Are you running gmailr in a non-interactive session? Consider:
* Call `gm_auth()` directly with all necessary specifics.
I have tried interactive with Rstudio and R console, with the same result.
All scripts and credentials are always on sync between machines using unison. And all worked fine as cron jobs, before the new installation.
Does anyone have any idea on how to investigate further the problem or solve it?
I made it to work again, but I don't understand why, as I didn't have to do that on my other systems.
I used an answer from this stackoverflow question.
I used:
rappdirs::user_cache_dir("gargle")
library("gargle")
gargle_oauth_sitrep()
If someone has a short explanation, please enlighten me!
Related
I used to not having issues on this particular subject, but bigrquery::bq_auth is not working on my installed RStudio. Funnything is that within an R terminal session it works perfectly.
All started when I updated the R to R version 4.2.2 (2022-10-31).
This impacts me because I'm not being able to run a shiny application due to this problem.
Does any one knows what am I missing or has any clue where to look for? At least for start, because I am lost.
The code I am running is quite simple:
json="The_file.json"
bigrquery::bq_auth(path = jason)
The message:
*Error: Can't get Google credentials.
Are you running bigrquery in a non-interactive session? Consider:
Call bq_auth() directly with all necessary specifics.
*
As a matter of fact, I was just hoping to have the same answer in the R terminal session:
The bigrquery package is requesting access to your Google account.
Select a pre-authorised account or enter '0' to obtain a new token.
Press Esc/Ctrl + C to cancel.
Folks, I removed all packages and installed everything possible again. It worked. Sorry. I had tryed a lot and this last one ocurred me later. Regards all.
TCP connections work fine as I am able to converse with someone over zoom and teamviewer. However, whenever I attempt to access another webpage, I get a network error. Google seems to work fine for some reason but any webpage I go to listed by Google fails to connect. The only way I can open up my http connections is by ending a task called "init" inside of task manager. This shuts down my vscode as well as my ubuntu terminals I have running. If someone knows the solution please do tell. It's really annoying having to close out my vscode and terminals as well as my local servers to look up information and debug.
I found a fix to this issue.
So I was running a Windows Subsystem for Linux and my Windows Build was outdated as well as WSL. When I updated Windows and upgraded to WSL2, my issue was resolved and I don't seem to get any more network errors.
I have been using R on commandline (BASH). I am unable to access the internet (download any packages). I have tried proxy system wide, and tested it with wget, which works. The "install.packages()" command however does not.
Per some user's advice, I also tried setting the proxy in .Rprofiles file. That didn't help either. Please advice.
I recently ran into the same issue on my work machine. Our Firm uses Cylance as its antivirus software. Cylance was quarantining the file "internet.dll" that R uses to access the Internet. Fortunately, however, it only does so in the 32-bit version of R. For me, there were two solutions:
First, I was able to download packages directly from the 32-bit version of R (outside of RStudio). This works fine. The downloaded packages will run in 64-bit RStudio.
The longer-term solution was to submit an IT service request to release this file from quarantine (that is, to "whitelist a blocked entity"). At my Firm this was promptly done, as there is (obviously) nothing unsafe about this R file.
I've been trying to install Meteorjs on windows but error occurs. I already tried downloading another installer and restarting my computer but it doesn't work. It always pops 'failed to contact install server. Please try again' then displays the message 'One or more issues caused the setup to fail. Please fix the issues and then retry setup. For more information see the log file.'
Under that it displays '0x80070643. Fatal Error during installation.'
what to do with this?
One option is to run meteor preview for windows. Believe it is a standalone copy of meteor 1.1
https://github.com/meteor/meteor/wiki/Preview-of-Meteor-on-Windows
(this doesn't address the issue of connecting to server though because when you try to create a meteor account you get a similar error).
there definitely is a way to install through command line on windows (which annoyingly I can't remember from my other machine). Perhaps through npm...
Try to run the package as administrator.It works!
Try this guide.
Download .zip, then unzip and set path environment variable.
Recently I added email sending capability to my Meteor app, using both the email package, and the account registration APIs to send emails. The other day, after having tested this thoroughly on my dev machine, I deployed it to our production server using Meteor Up. Once deployed, I did a quick check that the email APIs were working properly, and let it be. A day or two later, I made some minor changes, wrapping these email APIs in a Meteor.defer method to speed up the UI. I tested the changes locally (all fine), and re-deployed. I also ran apt-get update on my server after seeing a notification there were some new security updates available. After doing this, the email system no longer works. I tried reverting back to my previous configuration, and it still isn't working. I'm getting a timeout error:
Exception while invoking method 'forgotPassword' Error: connect ETIMEDOUT
I was wondering if anyone had any ideas on what might be causing this timeout (a blocked port?...how can I diagnose this?). Given my SMTP port is working on my development machine, it doesn't seem to be an issue with my code, but rather either with the MUP deployment, or Ubuntu configuration. I'm not super familiar with configuring Ubuntu servers. Any suggestions on how to go about de-bugging would be greatly appreciated!
We got a similar problem, and it was solved by opening the needed port in EC2. thanks to https://kylegoslin.wordpress.com/2012/06/05/116/