I've just discovered that you get the same message if the server can't
resolve its own host name. Putting an entry for the server name in
/etc/hosts fixed it.
On Wednesday, July 6, 2011 2:56:09 PM UTC-7, dtolj wrote:
I just installed gitorious and as I login with my admin account, I get an
Hi,
Got this fixed with thanks to the below excerpts of a blog -
http://cjohansen.no/en/ruby/setting_up_gitorious_on_your_own_server.
I recommend git.local for development and git.myserver.com (i.e.,
the site you'll be running Gitorious on) for production. For some
reason, I'm unable to login
Using some strategic puts, it appears as tho the auth token is
expiring immediately. Whatever token is returned form the form is
always different from the one being verified against.
On Jul 17, 7:59 pm, Robert Kirchgessner asuranz...@gmail.com wrote:
I had Gitorious up and running on Friday.
I disabled forgery protection using
config.action_controller.allow_forgery_protection = false
Now I don't get the error, but logging in kicks me back to the index
page. Interestingly it looks like anything related to sessions is not
working properly.
On Jul 17, 10:27 pm, asuranzala
With forgery protection off, it appears as though I am succesfully
logging in and being redirected, but I am being redirected to the Home
page as if I wasn't logged in. There is something very odd going on
with sessions (since it also appears that the session issue is what is
causing my
Ok it works now, thanks to this post.
https://groups.google.com/forum/#!searchin/gitorious/invalidauthenticitytoken/gitorious/5jVZaApOaew/7ogNz3HxxPsJ
I created an entry inside /etc/hosts
127.0.0.1 code.host.com
restated gitorious: cd gitorious; touch tmp/restart.txt
and I was able to login.
--
