Common Redmine Installation & Update troubles

You have installed or updated Easy Redmine under user with insufficient permissions, not following our strong recommendation in the instructions (at least once in the past).

1. Correct permissions by commands chgrp and chown according to server settings (eg. chgrp -R www-data public_html)
2. Run installation again bundle exec rake easyproject:install RAILS_ENV=production which will clear cache (if you run it by root, it will not be succesful)
3. Restart server

If you are using virtual machine provided by Easy Software, run under user easy:

sudo chown -R easy /home/easy/current
(in older machines - sudo chown -R easy /srv/easyredmine/public_html)

sudo chgrp -R easy /home/easy/current
(in older machines - sudo chgrp -R easy /srv/easyredmine/public_html)

cd /home/easy/current
(in older machines - cd /srv/easyredmine/public_html)

bundle exec rake easyproject:install RAILS_ENV=production

sudo service unicorn restart

Remember to set the permissions for all necessary folders.

Here are some hints what you can do if you run into 500 error.

• run Easy server requirements check and try to repair failed validations
• back-up your database
• download the latest package from the Client Zone
• make sure that webserver has Full access public, files, log, tmp folders
• run bundle install --without development test
• run bundle exec rake easyproject:install RAILS_ENV=production
• restart application server
• delete any 3rd parties' Redmine plugins (also from database)
• write us on This email address is being protected from spambots. You need JavaScript enabled to view it.  and attach production.log, unicorn.err or unicorn.log (if you use thin, puma or anything else, then there should be thin, puma or anything else instead of unicorn) and nginx error.log or apache2 error log, depending on what you use

There are many possible causes of this error. Here are a few tips:

• browser cache problem - try deleting cache from the browser
• dns problem
• server setting problem

First check your connection and network (verify that server is reachable by using a ping command or traceroute command). Firewall server side.

If all above seems fine, try to get some information from nginx error.logs. Check nginx error.log at the server side - /var/log/nginx/error.log

Double check that your nginx configuration matches the standard. Standard nginx configuration can be found here:
http://www.redmine.org/projects/redmine/wiki/HowTo_configure_Nginx_to_run_Redmine

Example of an nginx configuration (as is used by Easy Software). It's quite similar to official one only few variables are optimized:

user www-data;
worker_processes  8;

worker_rlimit_nofile 60000;

error_log  /var/log/nginx/error.log;
pid        /var/run/nginx.pid;

events {
    worker_connections  10240;
    # multi_accept on;
}

http {
    ssl_protocols  TLSv1 TLSv1.1 TLSv1.2;  # dont use SSLv3 ref: POODLE
    include       /etc/nginx/mime.types;
                default_type  application/octet-stream;
                server_names_hash_bucket_size 2048;

    access_log  /var/log/nginx/access.log;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;
    tcp_nodelay        on;

    send_timeout 1800;
    client_body_timeout  1800;
    client_header_timeout 1800;
    proxy_read_timeout 1800;
    client_max_body_size 220m;
    fastcgi_buffer_size 64K;
    fastcgi_buffers 128 16k;
    proxy_max_temp_file_size 0;
    types_hash_max_size 4096;
    types_hash_bucket_size 128;

    proxy_busy_buffers_size   256k;
    proxy_buffers 8 256k;
    proxy_buffer_size 256k;

    gzip  on;
    gzip_disable "MSIE [1-6]\.(?!.*SV1)";

    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;
    include /etc/nginx/sites-auto/*;
}

Other possible causes of 502 error include...

Unicorn is not running at all, due to

• Insufficient permissions
• Wrong version of passenger
• Wrong Ruby version
• Missing gems
• Broken filesystem

To find out the exact problem, you need to check error logs in unicorn or apache + application log from Easy Redmine (log/production.log)

Timeout

If low timeout is configured, this error will appear on:

• large exports
• overload of server
• rake tasks run from the GUI

Limit of MySQL connections

Make sure you have a sufficient number of connections allowed to MySQL. It depends on the number of users, but you should have at least a 100 allowed.

This error occurs from version 2018 1.2 (platform 04.00 and higher)

Error during upgrade installation containg some of the following.

[!] There was an error parsing `Gemfile`:

[!] There was an error parsing `Gemfile`: cannot load such file --

#  plugin 'rys-bundler', github: 'easysoftware/rys-bundler', branch: 'master'
 >  Plugin.hook('rys-gemfile', self)

Bundler cannot continue.

It is caused by outdated version of redmine installer.

Solution:

Before installing the upgrade

$ gem install redmine-installer

This problems occurs when you use a suffix on your Easy Redmine URL, for example: https://company.com/easyredmine/

In this case, you need to make sure that you have the variable RAILS_RELATIVE_URL_ROOT configured to your correct suffix /easyredmine

Bitnami:

1. Create an additional configuration file config/additional_environment.rb
2. config.action_controller.relative_url_root = "/easyredmine"
3. then precompile assets (rake easyproject:install RAILS_ENV=production) and restart the server

Make sure wkhtmltopdf is installed and running ( wkhtmltopdf needs X server or other emulation)
Test it using: "wkhtmltopdf google.com google.pdf"

Add to your proxy configuration:

proxy_set_header X-Forwarded-Proto https

When you are updating Easy Redmine on Windows platform and hit on error message ExecJs ::RuntimeError

All you have to do is install NODEJS on your system for the proper update.

If the installation fails, run manually:

$ bundle update
$ rake db:migrate
$ rake redmine:plugins:migrate