Hello,
whenever we try to use a customer transition we get an error 400.
I get this error for every User i try to use the transition. I read most of the "customer transition" topics here, but there is no working solution for me.
We are currently using a linux machine and we hosted jira ourselfs.
Maybe anyone of you can help me to get the customer transitions working?
Hi,
are you using proxy server (if yes which one)? Are you using some validators, post functions from any 3rd-party plugin (if yes which one)?
Can you share (insert into code block) your application log (INSTALL-DIR/logs/catalina.out) from time when did you click on button?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you share INSTALL-DIR/conf/server.xml (use code block - delete cert password if it's there)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you running application under root user? Because of connector ports are 80 and 443.
If you try set ports to 8080 and 8443 and run it under jira user what happens? Is problem still persist?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are using authbind to bind the ports
https://community.atlassian.com/t5/Jira-questions/Jira-on-port-80-443-using-AUTHBIND/qaq-p/411632
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't have experience with authbind so what I could try as first is running it under dedicated user and with default ports. If everything on java ports will be ok then is better to use some kind of reverse proxy (nginx, apache,...) for using ports 80 and 443.
I hope it will be this kind of problem - because 40X errors are usually caused by something between app and traffic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The solution for me was to grant the right to change the author for the customer side.
Dont know why this is needed, but it works now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.