-
Notifications
You must be signed in to change notification settings - Fork 292
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
Cannot acces production instance on ubuntu, (Subdomain problem?) #611
Comments
Want ahead and created the subdomain, the inverseproxy is somehow asking for.
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. |
Thanks @josep-tecnativa I tried updating the inverseproxy to traefik2.0.
Can you please document how to do it? |
Thanks, that inverse proxy seems to be working. Then starting the project with |
Thanks, |
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 a
gateway 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
The text was updated successfully, but these errors were encountered: