On 5/24/2024 at 11:08 AM, ImSkully said:

Sorry for the delay! The docker registry has been moved to openproject/openproject and updated to the latest recommended stable release version 14.1.0.

 

Please try update to the latest version and see if the still issue persists.

On latest version, exact same issue unfortunately. quits at "running bootstrap script..." and unsure where else to pull any possible logs or helpful details.

On 6/9/2024 at 7:10 AM, Ocean HP said:

 

After hours of searching and testing, my solution to the Error 422 was to add the variable: OPENPROJECT_HTTPS and set it to false; both for the value and default value. I couldn't access the login page through my browser (Brave) even after clearing the cache. I was able to access the login page in a private/incognito window. Hope this helps you @Gelantious.

 

Anyone solved the Nginx problem? I've set both the OPENPROJECT_HTTPS, SERVER_PROTOCOL_FORCE_HTTPS, and OPENPROJECT_HSTS to true. Changed the host name to op.mydomain.com. Changed the network to match Swag and got the proxy config file. None of the settings seem to do anything. OP still listens on the localhost:port. Maybe there is another variable we have to use?

Thank you kindly, the OPENPROJECT_HTTPS variable worked great for me

 

I'm leaving this information here in hopes it helps someone. I did get V14.2.1 working with Swag, Https enabled, and email smtp working. Unfortunately, V14.3 onward no longer works with the nginx file, but it is close:

 

server {
    listen 80;
    server_name OpenProject.*;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    server_name OpenProjects.*;
    
    include /config/nginx/ssl.conf;
    
    client_max_body_size 0;
    
    proxy_redirect off;
    
     location / {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP  $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
        set $upstream_app OpenProject;
        set $upstream_port 8080;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;
    }
}

Any plans to update this template to the latest Openproject?

On 11/27/2024 at 3:53 AM, Deltym said:

Any plans to update this template to the latest Openproject?

Sorry for the delay, I've bumped the template to use the latest stable version 15.0.2.

Hi there,

 

great work, thanks a lot. Just set up an OpenProject installation with no problems at all! Only minor hick-up was with attachment size. The template explains that the size is set in MB, wich would mean the default entry would amount to 5GB of file size. The respective entry in the settings of openProject itself says "kb" wich is a much more likely size :-).

 

Again: Thanks a lot!

 

 

On 1/7/2025 at 7:27 AM, Yazo said:

Hi there,

 

great work, thanks a lot. Just set up an OpenProject installation with no problems at all! Only minor hick-up was with attachment size. The template explains that the size is set in MB, wich would mean the default entry would amount to 5GB of file size. The respective entry in the settings of openProject itself says "kb" wich is a much more likely size :-).

 

Again: Thanks a lot!

Thanks for notifying! I've updated the description in the template to correctly reflect this as KB instead of MB.

On 6/9/2024 at 5:52 PM, TheCyberQuake said:

On latest version, exact same issue unfortunately. quits at "running bootstrap script..." and unsure where else to pull any possible logs or helpful details.

I was able to get to the bottom of this issue as I kept seeing it myself as well- I gather unRAID’s /mnt/user share uses a FUSE layer that lacks full hard-link support, causing PostgreSQL’s WAL initialization to fail. I switched from "/mnt/user/appdata/openproject/pgdata" to "/mnt/cache/appdata/openproject/pgdata" inside the template and everything immediately began working normally.

Hey there.
Im currently in the process of setting this docker up for a productive environment. For obvious reasons I want a solid backup strategy.
The user manual explains how to create a backup via the GUI: https://www.openproject.org/docs/system-admin-guide/backup/

The backup process creates a .zip file with an openproject.sql and some attachments inside. No problem so far.

 

But how can I restore this backup in case of a failure ? The official dokumentation is obviously not covering a docker installation on unraid.

On 2/20/2025 at 7:10 AM, Tetsuya said:

Hey there.
Im currently in the process of setting this docker up for a productive environment. For obvious reasons I want a solid backup strategy.
The user manual explains how to create a backup via the GUI: https://www.openproject.org/docs/system-admin-guide/backup/

The backup process creates a .zip file with an openproject.sql and some attachments inside. No problem so far.

 

But how can I restore this backup in case of a failure ? The official dokumentation is obviously not covering a docker installation on unraid.

 

I'm not an active user of OpenProject myself but it should be agnostic of the fact that its on Unraid as compared to just Docker. Their documentation covers restoring from a backing using the all-in-one container which this template is based on (of course no postgres database if you are supplying your own postgres container via DATABASE_URL) and looking at the process it should be more or less the same?

 

Instead of creating folders to be mounted, use an appdata directory > restore the database dump back into your postgres instance > restore attachments into appropriate appdata directory > start OpenProject container.

Edited March 1, 20251 yr by ImSkully

Looks like this is quite behind the release-updates of the official docker?
As of writing this, 16.2.0 in Unraid and 17.0.2 was actually released a few days back.

3 hours ago, per.pettersson said:

Looks like this is quite behind the release-updates of the official docker?
As of writing this, 16.2.0 in Unraid and 17.0.2 was actually released a few days back.

Thanks for letting me know, OpenProject doesn't provide an image with the :latest tag so the version number has to be manually bumped in the template every major version.

I've updated to 17.0.2, should be refreshed within the hour - please let me know if you encounter any issues!

Edited February 3Feb 3 by ImSkully

Is it possible that the internal port should be set to 80 and not 8080? I get a lot of connection refused issues when I try to connect.
Running the openproject container manually with forwarding to 80 (as in the docs) works fine.

Edited February 8Feb 8 by juledev

4 hours ago, juledev said:

Is it possible that the internal port should be set to 80 and not 8080? I get a lot of connection refused issues when I try to connect.
Running the openproject container manually with forwarding to 80 (as in the docs) works fine.

Are you sure? Port 8080 works fine using this template and OpenProject begins listening on this port which is mapped to port :5683 by default if you don't change it otherwise in the template.

Tested with a fresh deployment using latest CA template running openproject:17.0.2.

Hmm weird, I can try again but a default on my machine opened the internal port on 80 instead of 8080. I now executed the docker command manually via SSH and it works.

What is the recommended setup for sending email? Sendmail isn't working. I get the following error:

An error occurred while sending mail (:arguments expected to be an Array of individual string args)

Sendmail is in the image; it's found in /usr/lib and /usr/sbin and by default the config in OpenProject points to the sbin path. It does seem, based on the documentation, SMTP is preferred since I can't find any details for Sendmail setup. Search engine results don't help either.

I'm using the docker image: openproject/openproject:17.0.2

Edited February 10Feb 10 by Bryo