Once setup, where do you set Persona or Google Keys so you can login to admin? #27
Comments
|
Are you running this in the development environment or in staging/production/something else? In development mode, you should also have the "Login with a dummy login (development only)" option, which will allow you to login to the admin with any made up username. However, if you're deploying this to a non-development environment, then Persona or Google will indeed be your default login options. In that case, there's a few manual steps you'll need to go through the first time:
Sorry this process isn't a bit smoother and better documented--we're in the process of trying to improve the installation and setup process, but in the meantime, give us a shout if you have any questions. |
|
Thank you for the information. I got the admin user inserted, and logged in with persona. It showed verified, but after it tried to login I got: We're sorry, but something went wrong. Unsure what to try now. Let me know if you have any ideas. Thanks again for the help. |
|
Hello, Not sure if this helps, below are some of the logs I get: $ |
|
Very sorry for the delay in following up! I've was meaning to run through a fresh setup of my own to work out any of these kinks this week, but haven't quite gotten to that yet (but hopefully sometime in the next few days). In the meantime, if the problem is what I think it might be, you might give this a spin: $ cd /vagrant/workspace/web # Or wherever your api-umbrella-web app root is
$ RAILS_ENV=production rake db:seed # Or whatever environment, if not productionI think that might be what's triggering this error on initial setup and what needs to be integrated into the setup steps. If that doesn't do the trick, can you tail |
|
Thanks for your help. That got me into admin. Now I have another problem :) When I try to add a Backend, I am using the Getting started, to test, so setting up the Google Maps example. When I enter in the information, and click save, I am getting a popup: 502 Bad Gateway - From Nginx. The tail of my development.log in Web is: The tail of my error.log for nginx is: Please let me know if you have any ideas. Getting close! Thanks. |
|
Also, here is my log for Router/log/gatekeeper/production.log This is after a restart. Pretty sure mongo is fine because I can login with out a problem now to the Admin panel. So seems like something is going on with the connection to the backend servers: [Fri Jun 06 2014 11:41:16 GMT+0000 (UTC)] ERROR Mongo disconnected {} |
|
Hello, sorry for the many comments. Do you know of anyone that would offer paid support to fix the few things we're having trouble with? The environment is close, there must just be a small thing causing our final issues. If there is that would be great as we really need to get this up for our project. Thanks again for your help. |
|
No worries, and sorry for the troubles! There were some semi-recent changes that I think have changed this setup process, and unfortunately the setup documentation hasn't caught up. As I mentioned, we're working to really improve this setup and installation process, but apologies for the current state of flux. I'm in the process of standing up a new environment of my own to test a fresh setup out again, but my one other thought that might get things working for you: After logging into the admin, first navigate to Configuration > Publish Changes. Is there a big Publish button available on this page? If so, try hitting that. Then after things reload, try going back to the Configuration > Backends area and completing the example from the Getting Started docs. Unfortunately, there's no paid support at this time. I'd be happy to try and sort out any issues you may encounter with this (but obviously that's not quite the same as paid support). |
|
Thanks for sticking with me to try to figure this out, very much appreciated. I went to the publish changes, and hit the green button, however I got the same result when trying to add the sample backend. Ive been looking through logs, and wanted to post a couple things that may give you an idea of the issue, and show you some of the configs I have:
apiUmbrella:
fs.js:427 fs.js:427 and Elasticsearch WARNING: 2014-06-06T11:42:12Z Elasticsearch WARNING: 2014-06-06T11:42:12Z Elasticsearch WARNING: 2014-06-06T11:42:12Z Elasticsearch WARNING: 2014-06-06T11:42:12Z Elasticsearch WARNING: 2014-06-06T11:42:12Z Elasticsearch WARNING: 2014-06-06T11:42:12Z Elasticsearch WARNING: 2014-06-06T11:42:12Z Elasticsearch WARNING: 2014-06-06T11:42:12Z Elasticsearch WARNING: 2014-06-06T11:42:12Z Elasticsearch WARNING: 2014-06-06T11:42:12Z Elasticsearch WARNING: 2014-06-06T11:42:12Z Elasticsearch WARNING: 2014-06-06T11:42:12Z
The main, front-facing public host server. This serves up both the APIs andthe web content.server { } Secondary hosts. These are other hosts we're handling only API traffic for,but don't want to show web page content for.server { I apologize for the long response, just trying to provide as much info as I can to try to sort this out. Thanks again for looking at this for me. |
|
I ran through things and was able to get things working after the addition of the Thanks for providing your logs. One issue I see in the supervisor logs is that I don't think the gatekeeper is starting due to some file permission issues. With the default setup, your In general, there's a few config things you'll need to setup for a new production environment. It seems like you've maybe figured some of this out, but I think you might be missing a few of these, so here's my attempt at actually putting together a list of the configuration things you'll need to tweak (and my apologies this wasn't already better documented):
And to your third point about the domain, if you're using the default capistrano scripts for deployment, then the nginx hostname should get automatically setup based on your I think you're close. Hopefully this helps, and if so, we can use these as better documentation for getting a production environment setup until we get the broader setup improvements made (basically, we want to get this down to a single RPM or DEB package installer and one config file you tweak--but I don't have a firm timeframe on when that will be ready). Let me know if you have any further questions or you're still running into any errors. Sorry again for the trouble! |
|
Thanks again for all the help. Went through all your input, and got further. Before your comments, if I accessed any of the analytics in the admin I got an error, now the analtics are loading and showing api calls. Each calls status is a 404, which may help in debugging. I still cannot add a backend. When I try now, the modal does not show me the nginx error, it just shows Error, with no actual error output.
This is /srv/sites/router/current/log/error.log 2014/06/08 10:32:17 [error] 1129#0: *285 connect() failed (111: Connection refused) while connecting to upstream, client: 23.22.216.162, server: _, request: "HEAD / HTTP/1.1", upstream: "http://127.0.0.1:50090/", host: "54.209.87.206" Actually, those are the only errors I can find at this point in the logs. All the others are looking good, no error and showing that the other services are running properly. Mongo is showing the connection, no errors, elasticsearch looks good now. So these are all I'm seeing at this point. Your changes seems to got me closer, just need to figure out what the errors are above. Potentially permissions? Not sure. Thanks again for all your help. |
|
Ah, I think I missed one more piece that might explain this:
|
|
We've rolled out a greatly simplified setup process that should hopefully alleviate these type of setup issues: http://nrel.github.io/api-umbrella/download/ (see #26 for more background). So I'm going to close this issue, but let me know if you're still interested in API Umbrella and run into any issues with the new setup. |
Hello, I have everything setup and running, however I do not know how to login as admin. My two options is google or persona. Where do I put the keys in the code to enable myself to login to admin?
The text was updated successfully, but these errors were encountered: