You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
Happily, docker-mailserver is running again. I have deactivated TLS to get things simple, can call domain:81 which redirects to login page.
Now did I create a user yet? I don't remember and try what I would have used -- no success.
So I call bin/production.sh run --rm web setup.sh and it works as expected.
But then I get an error message: Domain name: This value is already used.
And I keep getting this even if I use an address I certainly did not use before.
root@IONOS_2: /root/docker-mailserver # bin/production.sh run --rm web setup.sh
2020/06/03 21:25:38 Waiting for: tcp://web:80
2020/06/03 21:25:38 Waiting for: tcp://db:3306
2020/06/03 21:25:38 Connected to tcp://db:3306
2020/06/03 21:25:38 Connected to tcp://web:80
Welcome to docker-mailserver!
This tool will help you to set up the first mail account.
You just have to answer a few questions.
Please enter the first email address you want to receive mails to: yy@xxx.tld
Enter a password for the new account:
Repeat the password:
Domain name: This value is already used.
There were some errors. Please start over again.
2020/06/03 21:25:56 Command exited with error: exit status 1
Why? A search in source code delivered no results:
root@IONOS_2: /root/docker-mailserver # grep -rn './' -e "Domain name: This value is already used." | grep -v ':#' | grep -v ':wp_'
root@IONOS_2: /root/docker-mailserver #
Even Google did not know about this error.
I went as far as # cat /opt/manager/bin/console but did not get any wiser. I thought about getting rid of the volumes to start fresh but then I knew they were fresh.
What to do now?
To Reproduce
Steps to reproduce the behavior:
No idea.
Expected behavior
A clear and concise description of what you expected to happen.
Accept these values.
Screenshots
If applicable, add screenshots to help explain your problem.
Docker environment (please complete the following information):
Output of docker info
root@IONOS_2: /root/docker-mailserver # docker info
Client:
Debug Mode: false
https://github.com/jeboehm/docker-mailserver/wiki/Troubleshooting
Did that.
Describe the bug
A clear and concise description of what the bug is.
Happily, docker-mailserver is running again. I have deactivated TLS to get things simple, can call domain:81 which redirects to login page.
Now did I create a user yet? I don't remember and try what I would have used -- no success.
So I call
bin/production.sh run --rm web setup.sh
and it works as expected.But then I get an error message:
Domain name: This value is already used.
And I keep getting this even if I use an address I certainly did not use before.
Why? A search in source code delivered no results:
Even Google did not know about this error.
I went as far as
# cat /opt/manager/bin/console
but did not get any wiser. I thought about getting rid of the volumes to start fresh but then I knew they were fresh.What to do now?
To Reproduce
Steps to reproduce the behavior:
No idea.
Expected behavior
A clear and concise description of what you expected to happen.
Accept these values.
Screenshots
If applicable, add screenshots to help explain your problem.
Docker environment (please complete the following information):
docker info
root@IONOS_2: /root/docker-mailserver # docker info
Client:
Debug Mode: false
Server:
Containers: 23
Running: 22
Paused: 0
Stopped: 1
Images: 26
Server Version: 19.03.8
Storage Driver: overlay2
Backing Filesystem:
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: active
NodeID: nq5nstnpr9ufblimr4sjuprbi
Is Manager: true
ClusterID: twia8p3g75k1crdaxzk727co0
Managers: 1
Nodes: 1
Default Address Pool: 10.0.0.0/8
SubnetSize: 24
Data Path Port: 4789
Orchestration:
Task History Retention Limit: 5
Raft:
Snapshot Interval: 10000
Number of Old Snapshots to Retain: 0
Heartbeat Tick: 1
Election Tick: 10
Dispatcher:
Heartbeat Period: 5 seconds
CA Configuration:
Expiry Duration: 3 months
Force Rotate: 0
Autolock Managers: false
Root Rotation In Progress: false
Node Address: 217.160.241.84
Manager Addresses:
217.160.241.84:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 4.18.0-147.8.1.el8_1.x86_64
Operating System: CentOS Linux 8 (Core)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.607GiB
Name: mail.voxx.biz
ID: U6R6:LG75:3V7W:TEZD:DHBC:WLRJ:TYHO:YIWZ:RTKE:CWQB:SYLJ:WCKC
Docker Root Dir: /var/lib/docker
Debug Mode: false
Username: kklepper
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
docker-compose version
root@IONOS_2: /root/docker-mailserver # docker-compose version
docker-compose version 1.25.5, build 8a1c60f6
docker-py version: 4.1.0
CPython version: 3.7.5
OpenSSL version: OpenSSL 1.1.0l 10 Sep 2019
Additional context
Add any other context about the problem here.
Well, I stopped the services without removing the volumes, then started again. Now it worked.
Login worked as well. Sigh.
The text was updated successfully, but these errors were encountered: