You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our company we have been using Odoo in a virtualenv up to now. After several attempts (because the Doodba documentation is not very clear and mainly focuses on the devel environment), we got the test environment started.
We set it up, the DB has been initialized, the Odoo instance has been started (both with -d and without it to check that it was starting) and we also started the inverse proxy.
Currently the certificate is not validated by LE, but that's OK because we just need a self-signed certificate. The instance is not Internet-accessible, but we will proxy it through another Apache machine in the future (that one will have LE).
The main issue is that the Odoo instance (or Traefik? this is not clear) responds with an infinite 302 redirect:
192.168.11.110 is an Ubuntu host with Docker. The code has been edited to hide the hostname, but we use the correct one. If we add a wrong hostname, it correctly replies with a 404 error.
To Reproduce
Affected versions: 14
Steps to reproduce the behavior:
After cloning the template and providing answers to Copier, we started the environment like this:
docker-compose -f test.yaml down
docker network create inverseproxy_shared
docker network create globalwhitelist_shared
docker-compose -f inverseproxy.yaml up -d
docker-compose -f test.yaml build --no-cache
docker-compose -f test.yaml run --rm odoo --stop-after-init -i base
docker-compose -f test.yaml up --build --remove-orphans --force-recreate
Expected behavior: We would expect to see a web page of Odoo or something.
Additional context: Ubuntu 22.04 with Docker version 20.10.21.
The text was updated successfully, but these errors were encountered:
Describe the bug
In our company we have been using Odoo in a virtualenv up to now. After several attempts (because the Doodba documentation is not very clear and mainly focuses on the devel environment), we got the test environment started.
We set it up, the DB has been initialized, the Odoo instance has been started (both with
-d
and without it to check that it was starting) and we also started the inverse proxy.Currently the certificate is not validated by LE, but that's OK because we just need a self-signed certificate. The instance is not Internet-accessible, but we will proxy it through another Apache machine in the future (that one will have LE).
The main issue is that the Odoo instance (or Traefik? this is not clear) responds with an infinite 302 redirect:
192.168.11.110
is an Ubuntu host with Docker. The code has been edited to hide the hostname, but we use the correct one. If we add a wrong hostname, it correctly replies with a 404 error.To Reproduce
Affected versions: 14
Steps to reproduce the behavior:
After cloning the template and providing answers to Copier, we started the environment like this:
Expected behavior: We would expect to see a web page of Odoo or something.
Additional context: Ubuntu 22.04 with Docker version 20.10.21.
The text was updated successfully, but these errors were encountered: