Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Infinite 301 redirect loop on test environment #395

Open
Lazza opened this issue Jul 12, 2023 · 0 comments
Open

Infinite 301 redirect loop on test environment #395

Lazza opened this issue Jul 12, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@Lazza
Copy link

Lazza commented Jul 12, 2023

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:

$ http GET 'https://192.168.11.110/' "Host:test.example.com" --verify=no
HTTP/1.1 301 Moved Permanently
Content-Length: 36
Content-Type: text/html; charset=utf-8
Date: Wed, 12 Jul 2023 09:44:01 GMT
Location: /

<a href="/">Moved Permanently</a>.

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.

@Lazza Lazza added the bug Something isn't working label Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant