While trying to login using the Meteor packages accounts-facebook and accounts-google, I'm getting an OAuth handler exception. Packages accounts-twitter appears to work fine and logs in perfectly. I haven't written any code, this is right out of the box using the accounts-ui package
The front end simply says "Internal Server Error" in red text, and the Meteor stack trace is the following:
Exception in oauth request handler [Error: failed]
Exception while invoking method 'login' Error: failed
at Request.Meteor.http.call [as _callback] (app/packages/http/httpcall_server.js:117:19)
at Request.init.self.callback (/usr/lib64/meteor/lib/node_modules/request/main.js:122:22)
at Request.EventEmitter.emit (events.js:96:17)
at Request.<anonymous> (/usr/lib64/meteor/lib/node_modules/request/main.js:654:16)
at Request.EventEmitter.emit (events.js:123:20)
at IncomingMessage.Request.start.self.req.self.httpModule.request.buffer (/usr/lib64/meteor/lib/node_modules/request/main.js:616:14)
at IncomingMessage.EventEmitter.emit (events.js:123:20)
at IncomingMessage._emitEnd (http.js:366:10)
at HTTPParser.parserOnMessageComplete [as onMessageComplete] (http.js:149:23)
at CleartextStream.socketOnData (http.js:1366:20)
I'm running the Meteor app on my own infrastructure with a working domain name. Any idea what's going on?
I had the same issue, and it turned out my service was not configured correctly, specifically I had the wrong Facebook app secret. Go into your mongo shell and check your meteor_accounts_loginServiceConfiguration to ensure it's set up correctly.
Start up Meteor, then go into the mongo shell via meteor mongo
Then type 'db.meteor_accounts_loginServiceConfiguration.find()' to show the documents in that collection. Now check your Facebook document to ensure it matches the app you created on Facebook exactly.
I did this and everything worked immediately.
Sorry for that. Our error reporting in these cases sucked. A fix is coming out in the soon-to-be-released Meteor 0.6.2.
Related
I am currently using CAS 5.2.3 and running our application in a Docker container. It runs fine locally without any issues but when I push the Docker image to the cloud in AWS as a Cloud Formation Stack, it throws the following error
2019-01-28 19:13:31,339 WARN [org.apereo.cas.services.ServiceRegistryConfigWatcher] - <Directory key is no longer valid. Quitting watcher service>
Exception in thread "org.apereo.cas.services.JsonServiceRegistryDao" java.nio.file.ClosedWatchServiceException at sun.nio.fs.AbstractWatchService.checkOpen(AbstractWatchService.java:80)
at sun.nio.fs.AbstractWatchService.checkKey(AbstractWatchService.java:92)
at sun.nio.fs.AbstractWatchService.take(AbstractWatchService.java:119)
at org.apereo.cas.services.ServiceRegistryConfigWatcher.run(ServiceRegistryConfigWatcher.java:72)at java.lang.Thread.run(Thread.java:748)
I am not sure what is causing this. Please let me know if you need any further details.
I search online and someone else also have your problem
Ref: https://groups.google.com/a/apereo.org/forum/#!topic/cas-user/L0XUII6FazI
And judging from they response, the problem was a right issue with Access Right. Maybe this is also your problem?
I have followed the Autodesk "View Your Models" Tutorial...incredibly helpful. I believe I have followed the tutorial, the site loads, and my existing buckets are shown with their current models listed. However when I create a new bucket and attempt to upload a model it does not show as having arrived in the bucket (I have refreshed, and waited 12 hours). There is a white arrow for expanding the bucket (to show its child models), but when clicked it just goes away.
The files I have attempted to upload are in the "Uploads" folders. Models I had in already existing buckets load and can be viewed.
I receive the following error:
/usr/local/bin/node start.js
events.js:183
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE :::3000
at Server.setupListenHandle [as _listen2] (net.js:1360:14)
at listenInCluster (net.js:1401:12)
at Server.listen (net.js:1485:7)
at Function.listen (/Users/ben/Documents/GitHub/sampleForgeNode/node_modules/express/lib/application.js:618:24)
at Object.<anonymous> (/Users/ben/Documents/GitHub/sampleForgeNode/start.js:21:5)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
Glad you enjoyed the tutorial! :-)
About the error, EADDRINUSE usually indicates the port (e.g. 3000) is already in use by another process. In most cases, it's another nodejs sample you left running or stopped working. On Windows, open the Task Manager and end all nodejs processes. For MacOS, open the Activity Monitor and kill all nodejs processes.
From your description, I would say that the upload is failing and, after that, a Nodejs process remains running and causing the EADDRINUSE error. As mentioned by Petr Broz, please check the terminal console for any error message that can identify the problem (probably during upload). You may try with a small file to get started, big files can cause timeout errors.
I have a random error: undefined that keeps getting popped up in my featherjs console and I don't know where it is coming from.
Does anyone know how I can figure out where the console.log pops up from?
console is the default error logger for the Feathers Express error handler middleware. You can disable error logging by setting the logger option to false but you probably want to find out why the Express error handler got triggered without an actual error.
We have generated jHipster project using "yo jHipster" which runs fine locally.
Now, we want to deploy the application to AWS using Elastic Beanstalk.
I have tried deploying the WAR file generated for the jHipster project using the Elastic Beanstalk console, however, it fails to launch the application.
Then I came across a sub project of jHipster to generate the application for AWS directly. e.g. yo jHipster:aws
But I am getting the following error while running it. Any pointers to investigate this issue further please?
yo jhipster:aws
events.js:141
throw er; // Unhandled 'error' event
^
TypeError: Cannot read property 'toLowerCase' of undefined
at module.exports.AwsGenerator.extend.initializing.checkDatabase (/usr/local/lib/node_modules/generator-jhipster/aws/index.js:23:37)
at Object. (/usr/local/lib/node_modules/generator-jhipster/node_modules/yeoman-generator/lib/base.js:436:25)
at /usr/local/lib/node_modules/generator-jhipster/node_modules/yeoman-generator/node_modules/run-async/index.js:24:25
at /usr/local/lib/node_modules/generator-jhipster/node_modules/yeoman-generator/lib/base.js:446:8
at processImmediate [as _immediateCallback] (timers.js:383:17)
I am following this tutorial (using meteor on modulus) to test telescope app and how the deploy works
I am getting this error :
Unable to connect to any application instances.
And this is the log:
/mnt/data/1/node_modules/fibers/future.js:245
throw(ex);
^ TypeError: Cannot read property 'name' of undefined
at app/server/migrations.js:469:43
at [object Object]._.extend.forEach (packages/mongo/mongo_driver.js:965:1)
at [object Object].Cursor.(anonymous function) [as forEach] (packages/mongo/mongo_driver.js:812:1)
at Object.migrationsList.updateUserNames (app/server/migrations.js:462:14)
at runMigration (app/server/migrations.js:45:52)
at app/server/migrations.js:10:5
at Array.forEach (native)
at Function..each..forEach (packages/underscore/underscore.js:105:1)
at Meteor.methods.removeMigration.Migrations.remove.name (app/server/migrations.js:9:5)
at /mnt/data/1/programs/server/boot.js:229:5 [2015-04-09T22:31:49.395Z] Failed to start application.
Thank you !!
This is a common issue when you don't redeploy the application after the first step.
run this 2 commands.
modulus project restart
modulus deploy
NOTE be sure the URL don't have any blank space either.
From step three of the tutorial,
The Meteor app is not quite ready yet and the logs will show errors. We have to deploy first in order to receive a URL for Meteor's required environment variables.
Have you goen through and correctly defined all of the environment variables?