Traefik Docker container raises Provider connection error #642
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello,
I'm new to Coop-Cloud. I have some (small) Docker skills (but not Swarm).
I'm following this guide https://docs.coopcloud.tech/operators/tutorial/#web-proxy-setup to install Traefik
Unfortunately when browsing to https://traefik.coopcloud.local.domain.tld I'm getting this error
Ce site est inaccessible
Il se peut que la page Web à l'adresse https://traefik.coopcloud.local.domain.tld soit temporairement inaccessible ou qu'elle ait été déplacée de façon permanente à une autre adresse Web.
ERR_SSL_UNRECOGNIZED_NAME_ALERT
My install is on top of Proxmox VE with 3 LXC containers with Docker installed (following https://gist.github.com/Drallas/e03eb5a4f68bb526f920a423455bc0c9 )
I tried to understand why I can't see Traefik dashboard despite I have
in ~/.abra/servers/coopcloud.local.domain.tld/traefik.coopcloud.local.domain.tld.env
I did
Any idea?
Hi,
could you also check the logs in the
socket-proxy
container`:Hey @scls19fr and welcome to coop-cloud :)
It would help if you could change the system locale to english or translate the error message.
But from
ERR_SSL_UNRECOGNIZED_NAME_ALERT
I think it's something about the SSL/TLS certificate. Istraefik.coopcloud.local.domain.tld
the domain you use? That could be the problem, because traefik can only get TLS certificates for domains with public DNS records. I think people were able getting treafik to run in a local environment, but this requires a special setup.Another thing I see is that the socket-proxy container is not running.
Can you provide some abra logs:
abra app logs traefik.domain.tld socket-proxy
abra app logs traefik.domain.tld app
Hi @p4u1 and @moritz
Sorry for not answering earlier but I didn't received email from this forge.
I end up restarting (rebuilding in fact) my Docker Swarm from scratch using this time Ubuntu VM (inside Proxmox VE) instead of LXC containers (this will probably be a more usual configuration)
socket-proxy is now running fine.
but I don't see it using
moreover
Any idea?
So it seems like you have 3 nodes. Note the that using coopcloud with multi node swarm setup is not really supported (or at least I don't know anyone running such a setup). If you still wasn't to continue on that road you need to adjust the traefik recipe and make sure the socket proxy container gets deployed on a manager. This can be done in the deploy config
Sorry for my newbie question but what is interest of using Docker Swarm with only one node ?
I will not continue on that road (because I'm not skilled enough on this kind of configuration) and will use only one node.
@scls19fr in practice, single node is really "good enough" for most small/medium-scale things and it saves cash. with some effort on the backups solution, you are still resilient. migrating a single swarm is easy ("just bring
/var/lib/docker/
with you"). a lot of Co-op Cloud is just making it easy/cost-effective to do hosting (which few are willing to pay much for...)Ok so let's close it as it working fine now with one node.
Thanks @p4u1 @moritz and @decentral1se