Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

Support Installation & Updates
  1. OpenProject
  2. Forums
  3. Support Installation & Updates
  4. Configuration broken after upgrade to 8.3.2

Configuration broken after upgrade to 8.3.2

Added by Frank Grossmann about 6 years ago

I'm accessing my server through a apache https reverse proxy.
After the upgrade I can't access my server anymore through web interface (Cross-Site Request Forgery Token error message), this happened before.
Previously I was then able to directly access the server through http and local IP, not anymore. On previous upgrades I found it has reset the local hostname and http/https protocol settings to the default values and didn't remember my settings.

How do I set the hostname and protocol settings through CLI ?

Thanks!


Replies (2)

RE: Configuration broken after upgrade to 8.3.2 - Added by Oliver Günther about 6 years ago

Dear Felix,

this has been reported at and has be fixed for OpenProject 9.0.0. As a workaround until then, please set the SERVER_HOSTNAME and SERVER_PROTOCOL manually with:

openproject config:set SERVER_HOSTNAME="your hostname"

openproject config:set SERVER_PROTOCOL="https"

Best,

Oliver

RE: Configuration broken after upgrade to 8.3.2 - Added by Frank Grossmann about 6 years ago

Hi Oliver,

let me give you an update.

First of all it seems I've forgot to run openproject configure after apt update, which seems to have caused the same cookie error message even when accessing the server locally through http. So maybe you want to check into that and produce a more meaningful error.

Anyway, I can say

openproject config:set SERVER_HOSTNAME="your hostname"

openproject config:set SERVER_PROTOCOL="https"

do not result in the upgrade honouring these entries. They are imported into /etc/openproject/conf.d/other, however. But it seems they are not used during upgrade / configure or during service startup - they are not imported into the system config shown in the web application. After running openproject configure I was able to get into the web interface again and could manually change.

So I am not sure that's what you intended to achieve, as the config:set commands did not have any effect.

Thanks and regards

Felix

  • (1 - 2/2)
Loading...