-
Notifications
You must be signed in to change notification settings - Fork 35
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Unable to get container working #52
Comments
First things first, see if Mailrise works without the Traefik wrapper. If you want extra logging pass Once you've confirmed Mailrise is doing its thing, you can turn your attention to your Traefik and Compose configurations. The Traefik Dashboard will show you whether you've connected your routers and services correctly. As for Compose, you seem to be using an unmanaged I'll caution that I am not really a Traefik expert; the config I have in the Readme is what works for me. |
What command are you referring to? The docker compose doesnt include a command in your templates and running it just uses The proxy network is what everything that is behind traefik is on and no other containers have any issues being on it. I have an entire media stack, gitea, portainer, and more all on that network with IPs and connectivity with my external machine and each other. |
I'm referring to the command-line arguments passed to the container. In Compose, you set these with the services:
mailrise:
image: yoryan/mailrise
container_name: mailrise
command: -vv /etc/mailrise.conf
restart: unless-stopped
networks:
- proxy
volumes:
- /mnt/docker/mailrise/mailrise.conf:/etc/mailrise.conf:ro
labels:
traefik.tcp.routers.mailrise.rule: "HostSNI(`*`)"
traefik.tcp.routers.mailrise.tls: "true"
traefik.tcp.routers.mailrise.certresolver: "cloudflare"
traefik.tcp.routers.mailrise.tls.domains[0].main: "mailrise.my.domain"
traefik.tcp.routers.mailrise.tls.domains[0].sans: ""
traefik.tcp.routers.mailrise.entrypoints: "mailsecure"
traefik.docker.network: "proxy" Also see if you can get any services to reach Mailrise directly (by IP address), without going through Traefik. |
Okay. Commented out all the labels and added in the command flag but left it on the proxy network since that is what everything else is on anyway. Finally getting logs now though realistically not many logs
Not sure really how best to get services to reach Mailrise in this state since the gitea method I was testing with requires TLS to be enabled and I am not passing any keys or anything into the container currently. |
Also tried running with the extra flags with the labels uncommented and got the same log result just different timestamp. so that leads me to believe that something is up with the way it is interfacing with traefik but as you can see from the stuff I posted originally I just added in the flags and such you mention (other than changing resolver to cloudflare and specifying the network) so unless there is something else in your traefik setup that I am missing I dont know what could be going on. In my traefik dashboard I am not seeing anything in the TCP section for routers which confirms the theory it isnt interfacing properly |
The last user who had a similar problem (#47) needed to add the |
Okay some progress now. That got me the TCP Router and Service in the Traefik dashboard.
|
That last line indicates your client provided an incorrect username/password combo. |
Okay. Yep I do see the typo there now that it is actually hitting something. Is the complete log silence by default intentional? I have never seen a docker container log absolutely nothing to the stdout for docker logs and or things like Loki to pick up on. Makes troubleshooting if the container is actually even doing anything nearly impossible |
The default logging level for a Python app is warnings or errors only. You're right that most other Docker images use the "info" level. I could certainly change the default behavior. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hey all. I am at a loss here. Trying to get mailrise working in a container with traefik and cannot for the life of me figure it out.
The container reports as running but has 0 logs when I run
docker logs mailrise
I tried looking in the container but dont see any place that would define a log file or anything internally.
When I try to send a test email from for example gitea to mailrise.my.domain:465 gitea just hangs and nothing ever comes through. I have provided my configs below if anyone can offer assistance please.
If I have missed a file or something that would be useful for troubleshooting please let me know. I love the concept of this app and want to get it working and will do whatever needed to help that process happen.
Docker-compose.yml
mailrise.conf
traefik.yml
The text was updated successfully, but these errors were encountered: