I got rid of the "hostname setting mismatch" warning by overwriting the OPENPROJECT_HOST__NAME environment variable when I run docker-compose, but I am still curious about why I cannot edit this field on system settings.

OPENPROJECT_HOST__NAME="pm.mydomain.com" docker-compose up -d

Any idea about why this field is disabled on system settings? Maybe a bug?

Hi Rafael,

please look into the manual (https://www.openproject.org/docs/installation-and-operations/installation/docker/#apache-reverse-proxy-setup)

I quote:

"The containers above are not meant as public facing endpoints. Always use an existing proxying web server or load balancer to provide access to OpenProject"

In your description you are not naming any webserver proxying, so i dought you installed a container yet. I recommend you to do so, as you might run into more trouble

I think the error message needs to be corrected here, which might be the only minor bug:

Feel free to report something about it here:

https://community.openproject.org/projects/openproject/work_packages/create_new?type=1

We appreciate the feedback and believe that together we can create great products for everyone!
If we can assist you with anything else, please don't hesitate to let us know.

Thank you for your kind help.

Hi Adam,

Thank you for your response.

Yes, I configured a web proxy. I am currently using the system and it looks great! But I had to apply the workaround I said above because I could not edit the hostname on system settings. Basically, since I could not edit this setting on the frontend, I passed the correct value as an environment variable.

OPENPROJECT_HOST__NAME="pm.mydomain.com" docker-compose up -d

If other users report the same issue, I will be glad to create a bug.

Have a nice day,
Rafael

Core version

OpenProject 12.3.2 

PostgreSQL version

13.8

And I run docker-compose...

Do you have full root access to your Amazon Linux?

I think you shall NOT start the docker with the -e hostname option at all.... i use to start docker instance by `docker-compose up -d`

Hi Adam, 

Yes, I use docker-compose up -d , just that I pass a value for an OpenProject environment variable. The full line is: 

OPENPROJECT_HOST__NAME="pm.mydomain.com" docker-compose up -d

Yes, I have full root access to my Amazon Linux. 

I solved the problem indirectly by using the command above and my OpenProject instance is working properly. 

Thanks for your attention,

Rafael

if you do not pass an argument like here

docker-compose up -d

you will be able to use the GUI to edit the hostname :)

I am indeed having this same issue - and I think this SHOULD be something that I can edit in my docker-compose.override.yml file, but I think there was something else about needing a .env file or something to make it all work? I'm not sure, exactly. I have tried setting the OPENPROJECT_HOST__NAME variable to no fewer than five different settings in the docker-compose.override.yml file, but I do not get consistent behavior at all. This is running on a physical server with which I have root access to, and is being proxied to via apache.

I have tried the following values:

1. "${OPENPROJECT_HOST__NAME:-localhost:8080}" (default)
2. "${OPENPROJECT_HOST__NAME:-openproject.example.com:8080}"
3. 'localhost:8080'
4. 'openproject.example.com:8080'
5. "openproject.example.com:8080"

No idea why, it's worked with 1, 3, and 4 - but none of the others - but sometimes it DOESN'T work with 1, 3, and 4, which is incredibly frustrating. >:/

This was with running OpenProject via docker-compose up -d. It works... better? when I try OPENPROJECT_HOST__NAME="openproject.example.com:8080" docker-compose up -d, but that's not something I can count on every time the server starts - and I still get bad links such as [`https://community.openproject.org/projects/demo-project.)

Rafael Cardero wrote:

Hi Adam,

Thank you for your response.

Yes, I configured a web proxy. I am currently using the system and it looks great! But I had to apply the workaround I said above because I could not edit the hostname on system settings. Basically, since I could not edit this setting on the frontend, I passed the correct value as an environment variable.

OPENPROJECT_HOST__NAME="pm.mydomain.com" docker-compose up -d

If other users report the same issue, I will be glad to create a bug.

Have a nice day,
Rafael

Hello to everyone :).

I have the same problem - i create the Container like in the documentation:

docker run -it -p 8080:80 \
-e OPENPROJECT_SECRET_KEY_BASE=ThisIsNotMyRealKey \
-e OPENPROJECT_HOST__NAME=localhost:8080 \
-e OPENPROJECT_HTTPS=false \
openproject/community:12

The setting is grayed out - so i can not change this hostname Parameter. I have no docker compose file.

How can i change the Parameter to: OPENPROJECT_HOST__NAME="192.168.111.11:8080"

Is it possible to start the container with -e OPENPROJECT_HOST__NAME="192.168.111.11:8080" Parameter - or create a new Container (docker run ...) but use the existing data? Or is it possible to export the Database an create a new Container and import the old Data?

Many thanks for your help :).

Adam Szabo wrote:

if you do not pass an argument like here

docker-compose up -d

you will be able to use the GUI to edit the hostname :)

I just did that and the option is still grayed out

I have prune the system, remove container, remove volumes and start with docker compose up -d and can not still edit that option. I believe that this option has to change because that is the hostname for the invitations and e-mails. But is there other way to change that?

Does anyone has an update on this issue? For me it persists. Have not been able to fully deploy because of this