From: Neil Williams <neil.williams@linaro.org>
Sent: Tuesday, 2 October 2018 4:18 PM
To: Jorgen Peddersen
Cc: Lava Users Mailman list
Subject: Re: [Lava-users] CSRF verification failed even after changing settings.confOn Tue, 2 Oct 2018 at 03:55, Jorgen Peddersen <jorgen.peddersen@seeingmachines.com> wrote:
Hi,
We're using LAVA 2018.5.post1 and we have not been able to log into the web interface since upgrading to this version. The system is running within a docker container.
There is limited experience of running the lava-server UI in docker. We don't have officially supported docker images for lava-server at this time. Work has been done with test images but those are not yet available for external users. We use lava-server in docker for the internal CI for lavasoftware.org but those images are only configured to run unit tests.
Make sure the system running docker is not already serving content on port 80 or specify a port for docker run. to use
Trying to log in results in a CSRF warning.
The same version of LAVA running on a dedicated debian machine does start working when adding the mentioned lines from this page: https://validation.linaro.org/static/docs/v2/installing_on_debian.html#django-localhost
Making the same changes to /etc/lava-server/settings.conf within the docker container has no effect on the way the web interface works. It still provides the same errors.
Is there anything else we should do to try to get the web interface to allow logins? I'm not even sure the settings.conf file is being read when restarting the LAVA services, would it appear in one of the logs so that I could search for it?
The BRANDING support is the simplest way to see if the settings.conf is being read correctly.
Of those, BRANDING_MESSAGE is probably the easiest to spot. https://staging.validation.linaro.org/ has a branding message - it appears in the About the LAVA staging instance section - a section which only appears if the branding message is correctly configured.
--
|
|
||||
|
||||
|
