NS8 Mail AD Auth failing

NethServer Version: 8
Module: Mail Version 1.4.1

Hi

I am getting strange authentification timeouts on a clients NS8 Mail server.
All systems are up to date, including Debian 12 base.

VM Info:
System: Proxmox VE 8.22
OS: Debian 12.5
CPU: 8-Core x86-64-v2-AES
RAM: 16 GB
Disks: 1.5 TB VirtIO on NVME
Networking: Static IP, DNS lookup working on all 3 internal DNS Servers (Including NS( AD DNS)

Basically running AD, FileServer, Mail & Nextcloud

Log excerpt when trying to login from a Thunderbird installed on a Win10 VM-PC:

2024-05-25T23:48:09+02:00 [1:mail1:postfix/postscreen] cache lmdb:/var/lib/postfix/postscreen_cache full cleanup: retained=0 dropped=0 entries
2024-05-25T23:48:09+02:00 [1:mail1:postfix/postscreen] CONNECT from [178.215.236.130]:54986 to [192.168.33.20]:25
2024-05-25T23:48:09+02:00 [1:mail1:postfix/postscreen] PREGREET 11 after 0.03 from [178.215.236.130]:54986: EHLO User\r\n
2024-05-25T23:48:09+02:00 [1:mail1:postfix/smtpd] connect from unknown[178.215.236.130]
2024-05-25T23:48:09+02:00 [1:mail1:rspamd] #25(rspamd_proxy) <caa4a3>; proxy; proxy_accept_socket: accepted milter connection from ::1 port 34720
2024-05-25T23:48:09+02:00 [1:mail1:postfix/smtpd] disconnect from unknown[178.215.236.130] ehlo=1 auth=0/1 quit=1 commands=2/3
2024-05-25T23:48:09+02:00 [1:mail1:rspamd] #25(rspamd_proxy) <caa4a3>; milter; rspamd_milter_process_command: got connection from 178.215.236.130:54986
2024-05-25T23:48:09+02:00 [1:mail1:rspamd] #25(rspamd_proxy) <caa4a3>; proxy; proxy_milter_finish_handler: finished milter connection
2024-05-25T23:48:42+02:00 [1:mail1:dovecot] auth: Error: auth-worker: Aborted PASSV request for admin: Lookup timed out
2024-05-25T23:48:42+02:00 [1:mail1:dovecot] auth-worker(32): conn unix:auth-worker (pid=24,uid=90): auth-worker<1>: ldap(admin,192.168.33.99,<RdrSO04ZNNLAqCFj>): Shutting down
2024-05-25T23:48:42+02:00 [1:mail1:dovecot] auth-worker(32): Warning: conn unix:auth-worker (pid=24,uid=90): Auth master disconnected us while handling request for admin for 60 secs (result=FAIL)

The Auth-Worker seems to shut down.

How can the Auth-Worker be restarted?

More Important: What could be causing this?

Even Roundcube installed in the same NS8 cluster can not log in.

AFAIK, it was working for a short while after migration from. NS7 (No issues during Mail Migration).

My 2 cents
Andy

Hi Andy, check if both samba and ldapproxy are running in the node. Look at their logs too: the error can be there.

This looks odd: are you sure it is Thunderbird talking? Port 25 is not correct, should be 587. It seems a bot connection.

1 Like

Hi @davidep

When I reboot the VM, samba is working.
After mail access (I also tried Outlook 2010, the version the client is using for NS7 so far, that fallbacks to port 25…) with TB, it looks at first OK, but that one try fries the proxy. After that attempt, TB can not verify the Password (The Proxy is dead) and times out, without adding the account.

I do not know how to restart just the proxy, any suggestions?
At the moment, restarting the server works. But mail dies on the first access attempt.

:frowning:

I can provide logs, if you tell me what helps / what you need.

My 2 cents
Andy

Go to System logs page, select the Ldapproxy app instance and check for errors and connections both in dump and tail mode.

https://docs.nethserver.org/projects/ns8/en/latest/log_server.html#system-logs

To restart Ldapproxy, usual commands:

runagent -m ldapproxy1 systemctl --user status ldapproxy
runagent -m ldapproxy1 systemctl --user restart ldapproxy
2 Likes

Hi @davidep

I’m testing to connect a Thunderbird client to mail from a Win10 VM.
Win10 and TB are very current.

DNS resolution on the client works:

C:\Users\admin>nslookup suma-ns8.sumaXXXXX.ch
Server:  suma-ns8.sumaXXXXX.ch
Address:  192.168.33.20

Nicht autorisierende Antwort:
Name:    suma-ns8.sumaXXXXX.ch
Address:  192.168.33.20


C:\Users\admin>nslookup suma-ns8.sumaXXXXX.ch. 192.168.33.39
Server:  pi.hole
Address:  192.168.33.39

Name:    suma-ns8.sumaXXXXX.ch
Address:  192.168.33.20


C:\Users\admin>nslookup suma-ns8.sumaXXXXX.ch. 192.168.33.1
Server:  suma-opnsense-1.sumaXXXXX.ch
Address:  192.168.33.1

Name:    suma-ns8.sumaXXXXX.ch
Address:  192.168.33.20

The LDAPproxy seems OK, status & restarting show no unusual stuff:

[root@suma-ns8 ~]# runagent -m ldapproxy1 systemctl --user restart ldapproxy
[root@suma-ns8 ~]# runagent -m ldapproxy1 systemctl --user status ldapproxy
● ldapproxy.service - ldapproxy1 LDAP account provider local proxy
     Loaded: loaded (/home/ldapproxy1/.config/systemd/user/ldapproxy.service; enabled; preset: enabled)
     Active: active (running) since Sun 2024-05-26 22:38:25 CEST; 5s ago
       Docs: man:podman-generate-systemd(1)
    Process: 56467 ExecStartPre=/bin/rm -f /run/user/1003/ldapproxy.pid /run/user/1003/ldapproxy.ctr-id (code=exited, status=0/SUCCESS)
    Process: 56469 ExecStartPre=/usr/local/bin/runagent update-conf (code=exited, status=0/SUCCESS)
    Process: 56477 ExecStart=/usr/bin/podman run --detach --env=NGINX_ENTRYPOINT_QUIET_LOGS=1 --conmon-pidfile=/run/user/1003/ldapproxy.pid --cidfile=/run/user/10>
   Main PID: 56492 (conmon)
      Tasks: 1 (limit: 19136)
     Memory: 3.7M
        CPU: 1.149s
     CGroup: /user.slice/user-1003.slice/user@1003.service/app.slice/ldapproxy.service
             └─56492 /usr/bin/conmon --api-version 1 -c a78b2268e8b1f0d915c58f02469f6cdd964b0b77448d6fc2ed58346a5d2b2250 -u a78b2268e8b1f0d915c58f02469f6cdd964b0b>

May 26 22:38:25 suma-ns8 ldapproxy[56492]: 2024/05/26 20:38:25 [notice] 1#1: start worker process 27
May 26 22:38:25 suma-ns8 ldapproxy[56492]: 2024/05/26 20:38:25 [notice] 1#1: start worker process 28
May 26 22:38:25 suma-ns8 ldapproxy[56492]: 2024/05/26 20:38:25 [notice] 1#1: start worker process 29
May 26 22:38:25 suma-ns8 ldapproxy[56492]: 2024/05/26 20:38:25 [notice] 1#1: start worker process 30
May 26 22:38:25 suma-ns8 ldapproxy[56492]: 2024/05/26 20:38:25 [notice] 1#1: start worker process 31
May 26 22:38:25 suma-ns8 ldapproxy[56492]: 2024/05/26 20:38:25 [notice] 1#1: start worker process 32
May 26 22:38:25 suma-ns8 ldapproxy[56492]: 2024/05/26 20:38:25 [info] 25#25: *1 client 127.0.0.1:36394 connected to 127.0.0.1:20001
May 26 22:38:25 suma-ns8 ldapproxy[56492]: 2024/05/26 20:38:25 [info] 25#25: *1 proxy 192.168.33.20:49752 connected to 192.168.33.20:636
May 26 22:38:27 suma-ns8 ldapproxy[56492]: 2024/05/26 20:38:27 [info] 26#26: *3 client 127.0.0.1:36402 connected to 127.0.0.1:20001
May 26 22:38:27 suma-ns8 ldapproxy[56492]: 2024/05/26 20:38:27 [info] 26#26: *3 proxy 192.168.33.20:49766 connected to 192.168.33.20:636
[root@suma-ns8 ~]# 

Logs of LDAPproxy during mailclient config attempt:

DUMP mode - shutdown is shown…

2024-05-26T22:38:02+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:02 [info] 25#25: *35 client 127.0.0.1:52082 connected to 127.0.0.1:20001
2024-05-26T22:38:02+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:02 [info] 25#25: *33 proxy 192.168.33.20:56910 connected to 192.168.33.20:636
2024-05-26T22:38:02+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:02 [info] 25#25: *35 proxy 192.168.33.20:56924 connected to 192.168.33.20:636
2024-05-26T22:38:05+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:05 [info] 25#25: *29 client disconnected, bytes from/to client:351/339, bytes from/to upstream:339/351
2024-05-26T22:38:05+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:05 [info] 25#25: *31 client disconnected, bytes from/to client:65/14, bytes from/to upstream:14/65
2024-05-26T22:38:05+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:05 [info] 25#25: *37 client 127.0.0.1:52086 connected to 127.0.0.1:20001
2024-05-26T22:38:05+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:05 [info] 26#26: *39 client 127.0.0.1:52094 connected to 127.0.0.1:20001
2024-05-26T22:38:05+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:05 [info] 25#25: *37 proxy 192.168.33.20:56926 connected to 192.168.33.20:636
2024-05-26T22:38:05+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:05 [info] 26#26: *39 proxy 192.168.33.20:56942 connected to 192.168.33.20:636
2024-05-26T22:38:13+02:00 [1:ldapproxy1:systemd] Stopping ldapproxy.service - ldapproxy1 LDAP account provider local proxy...
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: signal 3 (SIGQUIT) received, shutting down
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 25#25: gracefully shutting down
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 27#27: gracefully shutting down
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 28#28: gracefully shutting down
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 26#26: gracefully shutting down
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 31#31: gracefully shutting down
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 28#28: exiting
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 27#27: exiting
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 32#32: gracefully shutting down
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 31#31: exiting
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 32#32: exiting
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 30#30: gracefully shutting down
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 29#29: gracefully shutting down
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 30#30: exiting
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 29#29: exiting
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 31#31: exit
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 32#32: exit
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 27#27: exit
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 28#28: exit
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 29#29: exit
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 30#30: exit
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: signal 17 (SIGCHLD) received from 27
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: worker process 27 exited with code 0
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: signal 29 (SIGIO) received
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: signal 17 (SIGCHLD) received from 30
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: worker process 30 exited with code 0
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: signal 29 (SIGIO) received
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: signal 17 (SIGCHLD) received from 31
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: worker process 29 exited with code 0
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: worker process 31 exited with code 0
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: signal 29 (SIGIO) received
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: signal 17 (SIGCHLD) received from 29
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: signal 17 (SIGCHLD) received from 32
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: worker process 28 exited with code 0
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: worker process 32 exited with code 0
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: signal 29 (SIGIO) received
2024-05-26T22:38:13+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:13 [notice] 1#1: signal 17 (SIGCHLD) received from 28
2024-05-26T22:38:23+02:00 [1:ldapproxy1:podman] time="2024-05-26T22:38:23+02:00" level=warning msg="StopSignal SIGQUIT failed to stop container ldapproxy in 10 seconds, resorting to SIGKILL"
2024-05-26T22:38:23+02:00 [1:ldapproxy1:podman] 2024-05-26 22:38:23.424585894 +0200 CEST m=+0.027832326 container died 0fce6a79bab3d914e92be9288203ff33af83f72ac86afcb9983c57f8216ba384 (image=docker.io/library/nginx:1.25.4-alpine, name=ldapproxy, PODMAN_SYSTEMD_UNIT=ldapproxy.service, maintainer=NGINX Docker Maintainers <docker-maint@nginx.com>)
2024-05-26T22:38:23+02:00 [1:ldapproxy1:podman] 2024-05-26 22:38:23.534458655 +0200 CEST m=+0.137705080 container cleanup 0fce6a79bab3d914e92be9288203ff33af83f72ac86afcb9983c57f8216ba384 (image=docker.io/library/nginx:1.25.4-alpine, name=ldapproxy, PODMAN_SYSTEMD_UNIT=ldapproxy.service, maintainer=NGINX Docker Maintainers <docker-maint@nginx.com>)
2024-05-26T22:38:23+02:00 [1:ldapproxy1:podman] 2024-05-26 22:38:23.534939757 +0200 CEST m=+10.247361924 container cleanup 0fce6a79bab3d914e92be9288203ff33af83f72ac86afcb9983c57f8216ba384 (image=docker.io/library/nginx:1.25.4-alpine, name=ldapproxy, PODMAN_SYSTEMD_UNIT=ldapproxy.service, maintainer=NGINX Docker Maintainers <docker-maint@nginx.com>)
2024-05-26T22:38:23+02:00 [1:ldapproxy1:podman] 0fce6a79bab3d914e92be9288203ff33af83f72ac86afcb9983c57f8216ba384
2024-05-26T22:38:23+02:00 [1:ldapproxy1:systemd] ldapproxy.service: Main process exited, code=exited, status=137/n/a
2024-05-26T22:38:23+02:00 [1:ldapproxy1:podman] 2024-05-26 22:38:23.805398003 +0200 CEST m=+0.233066895 container remove 0fce6a79bab3d914e92be9288203ff33af83f72ac86afcb9983c57f8216ba384 (image=docker.io/library/nginx:1.25.4-alpine, name=ldapproxy, PODMAN_SYSTEMD_UNIT=ldapproxy.service, maintainer=NGINX Docker Maintainers <docker-maint@nginx.com>)
2024-05-26T22:38:23+02:00 [1:ldapproxy1:podman] 0fce6a79bab3d914e92be9288203ff33af83f72ac86afcb9983c57f8216ba384
2024-05-26T22:38:23+02:00 [1:ldapproxy1:systemd] ldapproxy.service: Failed with result 'exit-code'.
2024-05-26T22:38:23+02:00 [1:ldapproxy1:systemd] Stopped ldapproxy.service - ldapproxy1 LDAP account provider local proxy.
2024-05-26T22:38:23+02:00 [1:ldapproxy1:systemd] ldapproxy.service: Consumed 1.444s CPU time.
2024-05-26T22:38:23+02:00 [1:ldapproxy1:systemd] Starting ldapproxy.service - ldapproxy1 LDAP account provider local proxy...
2024-05-26T22:38:24+02:00 [1:ldapproxy1:podman] 2024-05-26 22:38:24.757158223 +0200 CEST m=+0.022100158 image pull  docker.io/library/nginx:1.25.4-alpine
2024-05-26T22:38:24+02:00 [1:ldapproxy1:podman]
2024-05-26T22:38:25+02:00 [1:ldapproxy1:podman] 2024-05-26 22:38:25.016879096 +0200 CEST m=+0.281821106 container create a78b2268e8b1f0d915c58f02469f6cdd964b0b77448d6fc2ed58346a5d2b2250 (image=docker.io/library/nginx:1.25.4-alpine, name=ldapproxy, maintainer=NGINX Docker Maintainers <docker-maint@nginx.com>, PODMAN_SYSTEMD_UNIT=ldapproxy.service)
2024-05-26T22:38:25+02:00 [1:ldapproxy1:systemd] Started libpod-a78b2268e8b1f0d915c58f02469f6cdd964b0b77448d6fc2ed58346a5d2b2250.scope - libcrun container.
2024-05-26T22:38:25+02:00 [1:ldapproxy1:podman] 2024-05-26 22:38:25.123298447 +0200 CEST m=+0.388240459 container init a78b2268e8b1f0d915c58f02469f6cdd964b0b77448d6fc2ed58346a5d2b2250 (image=docker.io/library/nginx:1.25.4-alpine, name=ldapproxy, PODMAN_SYSTEMD_UNIT=ldapproxy.service, maintainer=NGINX Docker Maintainers <docker-maint@nginx.com>)
2024-05-26T22:38:25+02:00 [1:ldapproxy1:podman] 2024-05-26 22:38:25.148361469 +0200 CEST m=+0.413303406 container start a78b2268e8b1f0d915c58f02469f6cdd964b0b77448d6fc2ed58346a5d2b2250 (image=docker.io/library/nginx:1.25.4-alpine, name=ldapproxy, PODMAN_SYSTEMD_UNIT=ldapproxy.service, maintainer=NGINX Docker Maintainers <docker-maint@nginx.com>)
2024-05-26T22:38:25+02:00 [1:ldapproxy1:podman] a78b2268e8b1f0d915c58f02469f6cdd964b0b77448d6fc2ed58346a5d2b2250
2024-05-26T22:38:25+02:00 [1:ldapproxy1:systemd] Started ldapproxy.service - ldapproxy1 LDAP account provider local proxy.
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: using the "epoll" event method
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: nginx/1.25.4
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: built by gcc 12.2.1 20220924 (Alpine 12.2.1_git20220924-r10)
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: OS: Linux 6.1.0-21-amd64
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: start worker processes
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: start worker process 25
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: start worker process 26
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: start worker process 27
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: start worker process 28
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: start worker process 29
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: start worker process 30
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: start worker process 31
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [notice] 1#1: start worker process 32
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [info] 25#25: *1 client 127.0.0.1:36394 connected to 127.0.0.1:20001
2024-05-26T22:38:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:25 [info] 25#25: *1 proxy 192.168.33.20:49752 connected to 192.168.33.20:636
2024-05-26T22:38:27+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:27 [info] 26#26: *3 client 127.0.0.1:36402 connected to 127.0.0.1:20001
2024-05-26T22:38:27+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:38:27 [info] 26#26: *3 proxy 192.168.33.20:49766 connected to 192.168.33.20:636
2024-05-26T22:39:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:39:25 [info] 25#25: *1 client disconnected, bytes from/to client:321/343, bytes from/to upstream:343/321
2024-05-26T22:39:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:39:25 [info] 27#27: *5 client 127.0.0.1:35896 connected to 127.0.0.1:20001
2024-05-26T22:39:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:39:25 [info] 28#28: *7 client 127.0.0.1:35912 connected to 127.0.0.1:20001
2024-05-26T22:39:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:39:25 [info] 27#27: *5 proxy 192.168.33.20:40286 connected to 192.168.33.20:636
2024-05-26T22:39:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:39:25 [info] 28#28: *7 proxy 192.168.33.20:40302 connected to 192.168.33.20:636
2024-05-26T22:39:27+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:39:27 [info] 26#26: *3 client disconnected, bytes from/to client:351/339, bytes from/to upstream:339/351
2024-05-26T22:39:27+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:39:27 [info] 29#29: *9 client 127.0.0.1:35926 connected to 127.0.0.1:20001
2024-05-26T22:39:27+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:39:27 [info] 31#31: *11 client 127.0.0.1:35940 connected to 127.0.0.1:20001
2024-05-26T22:39:27+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:39:27 [info] 29#29: *9 proxy 192.168.33.20:40316 connected to 192.168.33.20:636
2024-05-26T22:39:27+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:39:27 [info] 31#31: *11 proxy 192.168.33.20:40328 connected to 192.168.33.20:636
2024-05-26T22:40:02+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:40:02 [info] 30#30: *13 client 127.0.0.1:45476 connected to 127.0.0.1:20001
2024-05-26T22:40:02+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:40:02 [info] 30#30: *13 proxy 192.168.33.20:51828 connected to 192.168.33.20:636
2024-05-26T22:40:02+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:40:02 [info] 30#30: *13 client disconnected, bytes from/to client:591/2280, bytes from/to upstream:2280/591
2024-05-26T22:40:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:40:25 [info] 27#27: *5 client disconnected, bytes from/to client:65/14, bytes from/to upstream:14/65
2024-05-26T22:40:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:40:25 [info] 28#28: *7 client disconnected, bytes from/to client:321/343, bytes from/to upstream:343/321
2024-05-26T22:40:27+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:40:27 [info] 29#29: *9 client disconnected, bytes from/to client:65/14, bytes from/to upstream:14/65
2024-05-26T22:40:27+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:40:27 [info] 31#31: *11 client disconnected, bytes from/to client:65/14, bytes from/to upstream:14/65
2024-05-26T22:42:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:03 [info] 32#32: *15 client 127.0.0.1:37286 connected to 127.0.0.1:20001
2024-05-26T22:42:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:03 [info] 25#25: *16 client 127.0.0.1:37294 connected to 127.0.0.1:20001
2024-05-26T22:42:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:03 [info] 25#25: *16 proxy 192.168.33.20:37940 connected to 192.168.33.20:636
2024-05-26T22:42:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:03 [info] 32#32: *15 proxy 192.168.33.20:37936 connected to 192.168.33.20:636
2024-05-26T22:42:10+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:10 [info] 25#25: *19 client 127.0.0.1:50628 connected to 127.0.0.1:20001
2024-05-26T22:42:10+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:10 [info] 25#25: *19 proxy 192.168.33.20:59078 connected to 192.168.33.20:636
2024-05-26T22:42:10+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:10 [info] 25#25: *21 client 127.0.0.1:50632 connected to 127.0.0.1:20001
2024-05-26T22:42:10+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:10 [info] 25#25: *21 proxy 192.168.33.20:59092 connected to 192.168.33.20:636
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *21 client disconnected, bytes from/to client:74/14, bytes from/to upstream:14/74
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *19 client disconnected, bytes from/to client:4782/8912, bytes from/to upstream:8912/4782
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *23 client 127.0.0.1:50646 connected to 127.0.0.1:20001
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *23 proxy 192.168.33.20:59102 connected to 192.168.33.20:636
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *25 client 127.0.0.1:50654 connected to 127.0.0.1:20001
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *25 proxy 192.168.33.20:59112 connected to 192.168.33.20:636
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *25 client disconnected, bytes from/to client:74/14, bytes from/to upstream:14/74
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *23 client disconnected, bytes from/to client:395/1000, bytes from/to upstream:1000/395
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *27 client 127.0.0.1:50666 connected to 127.0.0.1:20001
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *27 proxy 192.168.33.20:59118 connected to 192.168.33.20:636
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *29 client 127.0.0.1:50668 connected to 127.0.0.1:20001
2024-05-26T22:42:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:11 [info] 25#25: *29 proxy 192.168.33.20:59134 connected to 192.168.33.20:636
2024-05-26T22:42:12+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:12 [info] 25#25: *29 client disconnected, bytes from/to client:74/14, bytes from/to upstream:14/74
2024-05-26T22:42:12+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:12 [info] 25#25: *27 client disconnected, bytes from/to client:395/1000, bytes from/to upstream:1000/395
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *31 client 127.0.0.1:43034 connected to 127.0.0.1:20001
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *31 proxy 192.168.33.20:60048 connected to 192.168.33.20:636
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *33 client 127.0.0.1:43040 connected to 127.0.0.1:20001
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *33 proxy 192.168.33.20:60064 connected to 192.168.33.20:636
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *33 client disconnected, bytes from/to client:74/14, bytes from/to upstream:14/74
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *31 client disconnected, bytes from/to client:395/1000, bytes from/to upstream:1000/395
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *35 client 127.0.0.1:43054 connected to 127.0.0.1:20001
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *35 proxy 192.168.33.20:60068 connected to 192.168.33.20:636
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *37 client 127.0.0.1:43070 connected to 127.0.0.1:20001
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *37 proxy 192.168.33.20:60076 connected to 192.168.33.20:636
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *37 client disconnected, bytes from/to client:74/14, bytes from/to upstream:14/74
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *35 client disconnected, bytes from/to client:395/1000, bytes from/to upstream:1000/395
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *39 client 127.0.0.1:43074 connected to 127.0.0.1:20001
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *39 proxy 192.168.33.20:60086 connected to 192.168.33.20:636
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *41 client 127.0.0.1:43086 connected to 127.0.0.1:20001
2024-05-26T22:42:22+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:22 [info] 25#25: *41 proxy 192.168.33.20:60096 connected to 192.168.33.20:636
2024-05-26T22:42:23+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:23 [info] 25#25: *41 client disconnected, bytes from/to client:74/14, bytes from/to upstream:14/74
2024-05-26T22:42:23+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:23 [info] 25#25: *39 client disconnected, bytes from/to client:395/1000, bytes from/to upstream:1000/395
2024-05-26T22:42:24+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:24 [info] 25#25: *43 client 127.0.0.1:43090 connected to 127.0.0.1:20001
2024-05-26T22:42:24+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:24 [info] 25#25: *43 proxy 192.168.33.20:60112 connected to 192.168.33.20:636
2024-05-26T22:42:24+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:24 [info] 25#25: *45 client 127.0.0.1:43096 connected to 127.0.0.1:20001
2024-05-26T22:42:24+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:24 [info] 25#25: *45 proxy 192.168.33.20:60114 connected to 192.168.33.20:636
2024-05-26T22:42:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:25 [info] 25#25: *45 client disconnected, bytes from/to client:74/14, bytes from/to upstream:14/74
2024-05-26T22:42:25+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:42:25 [info] 25#25: *43 client disconnected, bytes from/to client:395/1000, bytes from/to upstream:1000/395
2024-05-26T22:43:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:43:03 [info] 32#32: *15 client disconnected, bytes from/to client:65/14, bytes from/to upstream:14/65
2024-05-26T22:43:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:43:03 [info] 25#25: *16 client disconnected, bytes from/to client:321/343, bytes from/to upstream:343/321
2024-05-26T22:43:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:43:03 [info] 25#25: *47 client 127.0.0.1:36856 connected to 127.0.0.1:20001
2024-05-26T22:43:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:43:03 [info] 26#26: *49 client 127.0.0.1:36862 connected to 127.0.0.1:20001
2024-05-26T22:43:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:43:03 [info] 25#25: *47 proxy 192.168.33.20:48732 connected to 192.168.33.20:636
2024-05-26T22:43:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:43:03 [info] 26#26: *49 proxy 192.168.33.20:48740 connected to 192.168.33.20:636
2024-05-26T22:44:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:44:03 [info] 25#25: *47 client disconnected, bytes from/to client:65/14, bytes from/to upstream:14/65
2024-05-26T22:44:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:44:03 [info] 26#26: *49 client disconnected, bytes from/to client:321/343, bytes from/to upstream:343/321
2024-05-26T22:44:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:44:03 [info] 26#26: *51 client 127.0.0.1:35638 connected to 127.0.0.1:20001
2024-05-26T22:44:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:44:03 [info] 27#27: *53 client 127.0.0.1:35642 connected to 127.0.0.1:20001
2024-05-26T22:44:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:44:03 [info] 27#27: *53 proxy 192.168.33.20:43776 connected to 192.168.33.20:636
2024-05-26T22:44:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:44:03 [info] 26#26: *51 proxy 192.168.33.20:43772 connected to 192.168.33.20:636
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 26#26: *55 client 127.0.0.1:53312 connected to 127.0.0.1:20001
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 26#26: *55 proxy 192.168.33.20:57112 connected to 192.168.33.20:636
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 26#26: *57 client 127.0.0.1:53328 connected to 127.0.0.1:20001
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 26#26: *57 proxy 192.168.33.20:57114 connected to 192.168.33.20:636
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 26#26: *51 client disconnected, bytes from/to client:65/14, bytes from/to upstream:14/65
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 27#27: *53 client disconnected, bytes from/to client:321/343, bytes from/to upstream:343/321
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 26#26: *59 client 127.0.0.1:53332 connected to 127.0.0.1:20001
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 27#27: *60 client 127.0.0.1:53338 connected to 127.0.0.1:20001
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 26#26: *55 client disconnected, bytes from/to client:361/10550, bytes from/to upstream:10550/361
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 26#26: *57 client disconnected, bytes from/to client:2055/1404, bytes from/to upstream:1404/2055
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 27#27: *60 proxy 192.168.33.20:57140 connected to 192.168.33.20:636
2024-05-26T22:45:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:45:03 [info] 26#26: *59 proxy 192.168.33.20:57128 connected to 192.168.33.20:636
2024-05-26T22:46:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:46:03 [info] 26#26: *59 client disconnected, bytes from/to client:65/14, bytes from/to upstream:14/65
2024-05-26T22:46:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:46:03 [info] 27#27: *60 client disconnected, bytes from/to client:321/343, bytes from/to upstream:343/321
2024-05-26T22:46:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:46:03 [info] 26#26: *63 client 127.0.0.1:39166 connected to 127.0.0.1:20001
2024-05-26T22:46:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:46:03 [info] 27#27: *65 client 127.0.0.1:39182 connected to 127.0.0.1:20001
2024-05-26T22:46:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:46:03 [info] 26#26: *63 proxy 192.168.33.20:51578 connected to 192.168.33.20:636
2024-05-26T22:46:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:46:03 [info] 27#27: *65 proxy 192.168.33.20:51590 connected to 192.168.33.20:636
2024-05-26T22:47:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:47:03 [info] 26#26: *63 client disconnected, bytes from/to client:65/14, bytes from/to upstream:14/65
2024-05-26T22:47:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:47:03 [info] 27#27: *65 client disconnected, bytes from/to client:321/343, bytes from/to upstream:343/321
2024-05-26T22:47:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:47:03 [info] 26#26: *67 client 127.0.0.1:43674 connected to 127.0.0.1:20001
2024-05-26T22:47:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:47:03 [info] 27#27: *69 client 127.0.0.1:43690 connected to 127.0.0.1:20001
2024-05-26T22:47:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:47:03 [info] 27#27: *69 proxy 192.168.33.20:46506 connected to 192.168.33.20:636
2024-05-26T22:47:03+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:47:03 [info] 26#26: *67 proxy 192.168.33.20:46490 connected to 192.168.33.20:636
2024-05-26T22:48:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:48:11 [info] 26#26: *71 client 127.0.0.1:58486 connected to 127.0.0.1:20001
2024-05-26T22:48:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:48:11 [info] 27#27: *73 client 127.0.0.1:58494 connected to 127.0.0.1:20001
2024-05-26T22:48:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:48:11 [info] 26#26: *71 proxy 192.168.33.20:37272 connected to 192.168.33.20:636
2024-05-26T22:48:11+02:00 [1:ldapproxy1:ldapproxy] 2024/05/26 20:48:11 [info] 27#27: *73 proxy 192.168.33.20:37288 connected to 192.168.33.20:636

TAIL mode

→ Not as interesting

TB mail config still running, it seems to hang there after verifing the connection details are OK:

after a long timeout time, this is shown:

Something went wrong. Eventually configuration, username and password are not correct.

This is the admin user! (I know it’s not the same animal as the root-coupled NS7 one!).
I can login to cluster, but also to Nextcloud on NS8 without issues.
File access also work without issues (AD).

The error happens no matter if using IP or DNS name for NS8.

The same is shown no matter if I use admin or admin@domain.tld.
I’ve even tried both AD versions of the username, error shown is the same.

Interesting fact:

Mal as such seems to be working. This client - for legacy reasons still used fetchmail from NS7, that was correctly migrated to NS8. Mails are picked ip at the provider box and it seems correctly placed in the user mailboxes. It’s just client auth not working, no matter if Outlook, Thunderbird or Roundcube is used.

If even a pre-configured roundcube does not work, probably using a CLI mail client would make no difference…
So no way to really verify except logs, and the fact the mail is picked up as configured…

My 2 cents
Andy

Did you already try to set the incoming mail server port to 993 and the connection security to SSL/TLS ?

Hi @mrmarkuz

I have tried all possible options for auth, trying to see if one of both IMAP or SMTP works.
Also different encryption options…

:frowning:

Looking at the mail1 status page, one would think everything is working fine, except for backups not configured…
As it’s not working, setting p a local backup doesn’t improve things.
The whole system and files are backed up using Proxmox PBS.

I do have a Win10 client for testing with Thunderbird (current) and Outlook 2010 (The client is still using this, and it still works great!), and another client running MacOS for testing.

Both clients can easily connect to the old NS7 (Running in an isolated network / vmbr.).
Both clients can easily connect to the provider mailbox, also without issues.
But both timeout during setup to NS8 when doing auth - so impossible to set up.

:frowning:

1 Like

Hi

I can report this issue as solved for my client!

Solution?

As two Proxmox are available, I already had installed a second node on that 2nd Proxmox and joined it to the cluster on node 1.

It was working, but I did not have time to play with it, as I needed to get mail working for my client.

After reviewing the logs, I thought: Well, I’ll make a PBS backup of both nodes.
Then migrate mail1 to node2 and see what happens when I try to connect to an account from my Win10…

Moving the ca. 150 GB mail took a short while. But surprise: It works now. Still need to test roundcube, but it’s now a little late (or early, depending on your vantage point!) 01:30…


I would like to summarize:

This was my biggest running VM with NethServer!

The VM in Proxmox (NS7) had 24 GB RAM, 8 cores and 1.4 TB (On real NVMEs) diskspace allocated.
This system has been running without issues since 2019, when I migrated this client from a Windows 2008 SBS…

For those interested, here are some specs:

The two Proxmox PVE:

The nodes:

Node1:

Node2:

This typical SME has 15 users using the system, locally and home office via VPN / RDP.

There are still a few open points before I can call this a fully sucessful migration, but I’m well on the way!

Still WIP:

  • Zabbix
  • Webmail (working & tested!)
  • static html pages
  • Dokuwiki
  • Guacamole

These are all already installed, but configuration / testing needed!
After Files / Mail / Ad / Nextcloud are all working, I’m ready to challenge “Murphy” to break any of the open items on my list!

(Murphy: If it can fail, it will!) :slight_smile:

And yes, i’m confidant enough I’ve got more solutions to problems up my sleeve than Murphy has problems to use!
Besides which, Murphy doesn’t have the incredible dev team as back up, I do!

:slight_smile:

My 2 cents
Andy

1 Like