Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

Support Installation & Updates
  1. OpenProject
  2. Forums
  3. Support Installation & Updates
  4. try to login but see error "422 Invalid form authenticity token. "

try to login but see error "422 Invalid form authenticity token. "

Added by donny liu over 10 years ago

I installed the openproject successfully in centos6.6.
i can login first time.
and after I shut down the server and start the server again,
i start the service of httpd apache, start the mysqld, start the openproject, then, try to login, see this “422
Invalid form authenticity token.” error.

is there any more service I need to start on centos server?
or some else problem.

please advice.

Thanks for any suggestion you can provide.

Donny


Replies (10)

RE: try to login but see error "422 Invalid form authenticity token. " - Added by donny liu over 10 years ago

i figure it out by myself.
what I did is as below,
ssh root access
run the command “openproject configure”
it will reset all the configuration of the services.
then the problem gone

RE: try to login but see error "422 Invalid form authenticity token. " - Added by Chengru Song over 10 years ago

Could you kindly show me the location of openproject cmd? I’ve searched for none.

RE: try to login but see error "422 Invalid form authenticity token. " - Added by Tracy Cramer over 10 years ago

This did not work for me. I also saw one (https://community.openproject.org/topics/3750?r=3951) that said we needed to have memcache running. I tried using the command they offered and it said “can’t find the user memcache to switch to”

I am not a Linux guy and am trying to sell this product to our COO but with bugs like this it is a non-starter. I shouldn’t need to have a Linux guru on hand when upgrading to a minor version release.

RE: RE: try to login but see error "422 Invalid form authenticity token. " - Added by Jeremy McClintock about 10 years ago

Running our instance on CentOS 6.
In order to get a service/process to start at boot you can use the chkconfig command.

In order to see what is set to start at different runlevels:

chkconfig --list

Your result will look similar to this:

[HOST]# chkconfig --list
auditd          0:off   1:off   2:on    3:on    4:on    5:on    6:off
cgconfig        0:off   1:off   2:off   3:off   4:off   5:off   6:off
cgred           0:off   1:off   2:off   3:off   4:off   5:off   6:off
cloud-config    0:off   1:off   2:on    3:on    4:on    5:on    6:off
cloud-final     0:off   1:off   2:on    3:on    4:on    5:on    6:off
cloud-init      0:off   1:off   2:on    3:on    4:on    5:on    6:off
cloud-init-local        0:off   1:off   2:on    3:on    4:on    5:on    6:off
crond           0:off   1:off   2:on    3:on    4:on    5:on    6:off
htcacheclean    0:off   1:off   2:off   3:off   4:off   5:off   6:off
httpd           0:off   1:off   2:on    3:on    4:on    5:on    6:off
ip6tables       0:off   1:off   2:on    3:on    4:on    5:on    6:off
iptables        0:off   1:off   2:on    3:on    4:on    5:on    6:off
kdump           0:off   1:off   2:off   3:on    4:on    5:on    6:off
mdmonitor       0:off   1:off   2:on    3:on    4:on    5:on    6:off
memcached       0:off   1:off   2:off   3:off   4:off   5:off   6:off
mysqld          0:off   1:off   2:on    3:on    4:on    5:on    6:off
netconsole      0:off   1:off   2:off   3:off   4:off   5:off   6:off
netfs           0:off   1:off   2:off   3:on    4:on    5:on    6:off
network         0:off   1:off   2:on    3:on    4:on    5:on    6:off
nova-agent      0:off   1:off   2:on    3:on    4:on    5:on    6:off
postfix         0:off   1:off   2:on    3:on    4:on    5:on    6:off
rdisc           0:off   1:off   2:off   3:off   4:off   5:off   6:off
restorecond     0:off   1:off   2:off   3:off   4:off   5:off   6:off
rsyslog         0:off   1:off   2:on    3:on    4:on    5:on    6:off
saslauthd       0:off   1:off   2:off   3:off   4:off   5:off   6:off
sshd            0:off   1:off   2:on    3:on    4:on    5:on    6:off
svnserve        0:off   1:off   2:off   3:off   4:off   5:off   6:off
udev-post       0:off   1:on    2:on    3:on    4:on    5:on    6:off
xe-linux-distribution   0:off   1:off   2:on    3:on    4:on    5:on    6:off

You can then set memcached to run at boot with the following command:

chkconfig memcached on

Once that runs, check your result:

[HOST]# chkconfig --list
auditd          0:off   1:off   2:on    3:on    4:on    5:on    6:off
cgconfig        0:off   1:off   2:off   3:off   4:off   5:off   6:off
cgred           0:off   1:off   2:off   3:off   4:off   5:off   6:off
cloud-config    0:off   1:off   2:on    3:on    4:on    5:on    6:off
cloud-final     0:off   1:off   2:on    3:on    4:on    5:on    6:off
cloud-init      0:off   1:off   2:on    3:on    4:on    5:on    6:off
cloud-init-local        0:off   1:off   2:on    3:on    4:on    5:on    6:off
crond           0:off   1:off   2:on    3:on    4:on    5:on    6:off
htcacheclean    0:off   1:off   2:off   3:off   4:off   5:off   6:off
httpd           0:off   1:off   2:on    3:on    4:on    5:on    6:off
ip6tables       0:off   1:off   2:on    3:on    4:on    5:on    6:off
iptables        0:off   1:off   2:on    3:on    4:on    5:on    6:off
kdump           0:off   1:off   2:off   3:on    4:on    5:on    6:off
mdmonitor       0:off   1:off   2:on    3:on    4:on    5:on    6:off
memcached       0:off   1:off   2:on    3:on    4:on    5:on    6:off
mysqld          0:off   1:off   2:on    3:on    4:on    5:on    6:off
netconsole      0:off   1:off   2:off   3:off   4:off   5:off   6:off
netfs           0:off   1:off   2:off   3:on    4:on    5:on    6:off
network         0:off   1:off   2:on    3:on    4:on    5:on    6:off
nova-agent      0:off   1:off   2:on    3:on    4:on    5:on    6:off
postfix         0:off   1:off   2:on    3:on    4:on    5:on    6:off
rdisc           0:off   1:off   2:off   3:off   4:off   5:off   6:off
restorecond     0:off   1:off   2:off   3:off   4:off   5:off   6:off
rsyslog         0:off   1:off   2:on    3:on    4:on    5:on    6:off
saslauthd       0:off   1:off   2:off   3:off   4:off   5:off   6:off
sshd            0:off   1:off   2:on    3:on    4:on    5:on    6:off
svnserve        0:off   1:off   2:off   3:off   4:off   5:off   6:off
udev-post       0:off   1:on    2:on    3:on    4:on    5:on    6:off
xe-linux-distribution   0:off   1:off   2:on    3:on    4:on    5:on    6:off

You will see that the results for memcached now show as “on” for the appropriate runlevels!
This will work for RHEL/CentOS… not 100% sure about Ubuntu or other distros.

Hope this helps!

RE: RE: try to login but see error "422 Invalid form authenticity token. " - Added by Milos Cuculovic over 9 years ago

I had the same problem, in my case, it was the memcached auto config that was wrong.

in the /etc/memcached.conf, the

-l xxx.xxx.xxx.xxx

Was wrong, I had to set it as

-l 127.0.0.1

RE: try to login but see error "422 Invalid form authenticity token. " - Added by Cascade Sun over 6 years ago

I recently upgraded from a great running 7.3 in Univention and had just convinced project managers to start using it, but then I made a huge error and upgraded to version 8.1 per the nag screen in open project. Now it has the error 422 and I have tried all the fixes. Now nobody in our company will touch open project. This is how good open source projects die, and we will never pay anyone for support for such a shoddy upgrade process, cant count on it in the business environment

RE: try to login but see error "422 Invalid form authenticity token. " - Added by Cascade Sun over 6 years ago

Seriously, this caused our dept major embarrassment - RUN!

RE: try to login but see error "422 Invalid form authenticity token. " - Added by Oliver Günther over 6 years ago

There has just been a update on the OpenProject UCS package which addresses this issue. It took more time than anticipated, and I'd like to note we're not providing this package ourselves.

I'd like to give some insight into why this was happening: The Univention service provides a master web server that terminates SSL/TLS connections and forwards requests to a docker image running the OpenProject packaged installation. Within it, an Apache is running that provides all features we have in the packaged installation (asset management, repositories, and so on).

The outer Apache was configured to allow HTTP traffic, but the inner OpenProject service always assumes HTTPs traffic in 8.1 and cannot provide both http and https. This results in our own web server responding with secure cookies set, which were then removed by the outer Apache and in turn, causing the errors you described.

We're sorry for the inconvenience in the upgrade of this service, the 8.1. package was premature and not fully tested on UCS before its release. Its release cycles and upgrades are not something we can immediately affect due to the separate stack of UCS we do not control.

Best regards,

Oliver

RE: try to login but see error "422 Invalid form authenticity token. " - Added by Cascade Sun over 6 years ago

Hello - thanks for the update. So I have updated both Univention and also Open Project to the latest version released yesterday or so, 8.2. Yet the problem persists as before with no changes. Can anyone explain what I need to do to roll this back and start over, or otherwise get it straight so we can get at our projects still in there... thanks

I have a post here as well, with more detail:

https://help.univention.com/t/openproject-8-1-0-422-error/10268/15

422

Unable to verify Cross-Site Request Forgery token. Did you try to submit data on multiple browsers or tabs? Please close all tabs and try again.

RE: try to login but see error "422 Invalid form authenticity token. " - Added by Cascade Sun over 6 years ago

Ok all - I did a complete uninstall and manually deleted all references to Open Project from the UMC and then used univention-app install command to install from the SSH Putty cli, and I can now login with no more 422 error!

Thanks for keeping up on it guys!

  • (1 - 10/10)
Loading...