Olegs

Diagnostics shows that Samba is still working. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME rsyslogd 943 root 5u IPv4 20508 0t0 TCP 192.168.1.12:57428->192.168.1.39:5544 (ESTABLISHED) ... unraid-ap 4172 root 24u IPv4 20840 0t0 TCP 192.168.1.12:53658->172.67.69.176:443 (ESTABLISHED) smbd 4559 root 30u IPv4 16776 0t0 TCP 127.0.0.1:445 (LISTEN) Try changing this config and see if it helps you:

It turns out that was indeed the culprit causing the problem. Thanks to your advice, everything is now functioning smoothly, and I can confidently reboot the server without any issues. I had initially mentioned the 445 port problem in another thread, and your input was invaluable in resolving it.

My GUI was not loading as well. Not sure if you're issue is related, but this is what I had: ssh to the server, and tried starting nginx, and saw that 445 is used. root@node202:~# /etc/rc.d/rc.nginx start Starting Nginx server daemon... Message from syslogd@node202 at Jun 16 21:44:53 ... nginx: 2023/06/16 21:44:53 [emerg] 14086#14086: bind() to 127.0.0.1:445 failed (98: Address already in use) I stopped docker containers root@node202:~# /etc/rc.d/rc.docker stop stopping dockerd ... Cleaning up old /var/run/dockerd.pid. but that did not help, 445 still used. I checked for open ports, and samba was using that root@node202:~# netstat -ltnp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 6136/wsdd2 tcp 0 0 192.168.88.101:445 0.0.0.0:* LISTEN 6121/smbd So I stopped samba and started nginx. It went fine this time. root@node202:~# /etc/rc.d/rc.samba stop root@node202:~# /etc/rc.d/rc.nginx start Starting Nginx server daemon... I can see that nginx is using 445 port now tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 5824/nginx: master If I disable Samba - unraid reboots ok and gui starts, if it's enabled - after reboot web gui does not boot.

I am having a similar issue. unraid.example.com is forwarding to my unraid configuration page, ha.example.com is forwarding to homeassistant page. When on unraid.example.com I am doing a long operation, like docker pulling image for a new App from the store - ha.example.com and unraid.example.com(in another tab) are unreachable. As soon as long-op finishes - ha.example.com and unraid.example.com(in another tab) work fine. @lsmith5 have you found anything new?