opensubscriber
   Find in this group all groups
 
Unknown more information…

n : ntop@unipi.it 2 October 2009 • 3:12PM -0400

Re: [Ntop] Google Maps API key: where do I store the key?
by R.H.Hoek

REPLY TO AUTHOR
 
REPLY TO GROUP




-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear Ken,

In the webinterface goto 'Admin' -> 'Configure' -> 'Preferences'
Then search for 'google_maps.key'
With the set button you can enter your key.

- --

Success,

Roel

Ken Teague schreef op 2009-10-01 22:46:
> When I select "Hosts World Map" from the ntop web interface, I'm
> presented with an error that my Google Maps API key has been rejected.
> I've visited http://www.google.com/apis/maps/signup.html and generated a
> key for my site, but I'm not sure where to store it.  After a lot of
> Googling, I found:
>   http://www.ntop.org/trac/changeset/3640
>   http://www.ntop.org/trac/ticket/61
>   http://lists.ntop.org/pipermail/ntop-dev/2008-November/007117.html
> I created a file named google_maps.key under /usr/local/var/ntop, stored
> my key in it, chown ntop:staff google_maps.key, chmod 640
> google_maps.key, restarted ntop, but still get this error.  Should the
> key be in that file?  Shold it be in prefsCache.db? (if so, how do I get
> it in there?)
>
> Many thanks!
>
> - Ken
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ntop mailing list
> Ntop@unip...
> http://listgateway.unipi.it/mailman/listinfo/ntop




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrFp8EACgkQJwlRSGnYBcaFXACeMIYb7VvmShxD7M3CQm6CmKSq
W/wAoJBt+hpa7a5MxeU+IPqpMVQkkG0e
=Ul5u
-----END PGP SIGNATURE-----
_______________________________________________
Ntop mailing list
Ntop@unip...
http://listgateway.unipi.it/mailman/listinfo/ntop

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.