Closed bosd closed 3 months ago
Want ahead and created the subdomain, the inverseproxy is somehow asking for. Well, at leat according to the logger there is a certificate delivered.
proxy-1 | INFO[2024-05-14T04:41:06Z] legolog: [INFO] [odoo.fr.freedxxxxx.net] acme: Could not find solver for: tls-alpn-01
proxy-1 | INFO[2024-05-14T04:41:06Z] legolog: [INFO] [odoo.fr.freedxxxxx.net] acme: use http-01 solver
proxy-1 | INFO[2024-05-14T04:41:06Z] legolog: [INFO] [odoo.fr.freedxxxxx.net] acme: Trying to solve HTTP-01
proxy-1 | INFO[2024-05-14T04:41:11Z] legolog: [INFO] [odoo.fr.freedxxxxx.net] The server validated our request
proxy-1 | INFO[2024-05-14T04:41:11Z] legolog: [INFO] [odoo.fr.freedxxxxx.net] acme: Validations succeeded; requesting certificates
proxy-1 | INFO[2024-05-14T04:41:15Z] legolog: [INFO] [odoo.fr.freedxxxxx.net] Server responded with a certificate.
proxy-1 | INFO[2024-05-14T04:41:15Z] Server configuration reloaded on :80
proxy-1 | INFO[2024-05-14T04:41:15Z] Server configuration reloaded on :443
A new release has been found: 3.0.0. Please consider updating.
But anyway, it resolves in a time-out as well
In fact we are using already Traefik 2 (and trying the v3). @josep-tecnativa can you please put the configuration for it (and update the README).
Thanks 🙏, I'm looking forward to it, as I'm kinda blocked right now.
For now, if you chose Traefik in the second question, you are already able to use Traefik 2 I think you should try to use Traefik 2 in your inverse proxy
Thanks @josep-tecnativa
I tried updating the inverseproxy to traefik2.0. It is not happy at all..
Can you please document how to do it?
Thanks, that inverse proxy seems to be working. Booting it up, presents me a Welcome to Nginx when visiting the domain.
Then starting the project with docker compose -f prod.yaml up --build --remove-orphans
.
I'll get a very long wait.. untul it provides a black screen with a Gateway Timeout
.
Thanks,
Fixed it with the new traefik 2.0 inverseproxy from the template.
Then..
docker compose -p inverseproxy -f inverseproxy.yaml up -d
Could not get an production instance running on a new ubuntu VPS (AMD).
Describe the bug
It seems that there is an issue between the inverseproxy and the doodba instance. When the inverse proxy is not running I get an
This site can’t be reached, Empty response
(as expected) When inverse proxy is running (and doodba project not) there is an 404 not found (as expected) When both are up and running there is an endless loading with agateway time-out
.Expected behavior I was expecting to be able to acces my odoo instance. just by having the containers up and running. Same as with my other older vps'es
To Reproduce
Steps to reproduce the behavior:
.*
)Only changes are my email and version bump to trafik 1.7. Due to this
The logs where not really helpfull yet finding the problem. Here is an excerpt from the inverseproxy. Complanining about the domain.
Well, actually this might be a lead.. It looks like the inverseproxy is looking for subdomain
odoo.fr.freedxxxxx.net
on the dns record. But why? I configured the hosts as:Additional context VERSION="24.04 LTS (Noble Numbat)" Docker version 26.1.2, build 211e74 Doodba template version 6.1.5