Yep – you can actually run it on *any* high port (above 1024) as a non-root user. I wanted to use standard web ports for my setup and prefer to put everything behind a reverse proxy regardless.

com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira.versatushpc.com.br/rest/activity-stream/1.0/preferences?_=1558562492226, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

It appears to be certificate related, since on the dashboard the following message appears: gadget.common.error.500

I’ve read something about adding the certificate to the Java Keystore, but it does not worked as expected.

The configuration needs to be done for both Nginx and JIRA. As the title implies this is a setup guide for Nginx, not Apache. Good luck!

Does this require apache to be installed?

If anybody gets Error 502 Bad Gateway and your logs say “Permission denied…”, this worked for me:

$ sudo cat /var/log/audit/audit.log | grep nginx | grep denied | audit2allow -M mynginx
$ sudo semodule -i mynginx.pp

Source: https://confluence.atlassian.com/bitbucketserverkb/13-permission-denied-while-connecting-to-upstream-while-configuring-ngnix-803374014.html

This is a good tip for proxying in general if you need to handle file uploads – the default is often pretty low for security. I’ve updated the post, thanks!

Adding the following line to the server block listening on 443 corrected the issue:

client_max_body_size 20M;

Hope this helps someone at least as much as this guide helped me.

That is the upstream jira definition at the top of the config. You could specify multiple backend servers with weighting, etc here.