good that it is working now. But the behavior reminds me on a case we had in the past. It took us quite some time to find out what the issue was and who blocked SSH access. At the an TP-LINK Access Point was preventing SSH access. If you have time, you can read through this post https://dietpi.com/forum/t/ssh-never-get-to-prompt/4651/1
BTW. A successful SSH connection will looks like this on the logs
root@DietPiProd:~# journalctl -u dropbear.service
-- Logs begin at Fri 2020-12-25 00:40:55 CET, end at Mon 2020-12-28 18:36:25 CET. --
Dec 25 00:41:51 DietPiProd systemd[1]: Starting LSB: Lightweight SSH server...
Dec 25 00:41:52 DietPiProd dropbear[610]: Starting Dropbear SSH server: dropbear.
Dec 25 00:41:52 DietPiProd systemd[1]: Started LSB: Lightweight SSH server.
Dec 25 00:41:52 DietPiProd dropbear[621]: Running in background
Dec 25 00:48:28 DietPiProd dropbear[1031]: Child connection from 192.168.0.31:59041
Dec 25 00:48:32 DietPiProd dropbear[1031]: Password auth succeeded for 'root' from 192.168.0.31:59041
Dec 25 01:03:58 DietPiProd dropbear[1031]: Exit (root): Exited normally
Dec 25 02:08:54 DietPiProd dropbear[3255]: Child connection from 192.168.0.31:62717
Dec 25 02:08:58 DietPiProd dropbear[3255]: Password auth succeeded for 'root' from 192.168.0.31:62717
Dec 25 02:10:16 DietPiProd dropbear[3255]: Exit (root): Exited normally
Dec 25 21:15:34 DietPiProd dropbear[13426]: Child connection from 192.168.0.134:54265
Dec 25 21:15:43 DietPiProd dropbear[13426]: Password auth succeeded for 'root' from 192.168.0.134:54265
Dec 25 21:16:06 DietPiProd dropbear[13426]: Exit (root): Exited normally
Dec 26 11:44:59 DietPiProd dropbear[22443]: Child connection from 192.168.0.31:49975
Dec 26 11:45:04 DietPiProd dropbear[22443]: Password auth succeeded for 'root' from 192.168.0.31:49975
Dec 26 11:47:02 DietPiProd dropbear[22443]: Exit (root): Exited normally
Dec 26 21:47:09 DietPiProd dropbear[27628]: Child connection from 192.168.0.134:50779
Dec 26 21:47:13 DietPiProd dropbear[27628]: Password auth succeeded for 'root' from 192.168.0.134:50779
Dec 26 21:47:18 DietPiProd dropbear[27628]: Exit (root): Exited normally
Dec 27 21:29:55 DietPiProd dropbear[8722]: Child connection from 192.168.0.31:55901
Dec 27 21:29:58 DietPiProd dropbear[8722]: Password auth succeeded for 'root' from 192.168.0.31:55901
Dec 27 21:30:29 DietPiProd dropbear[8722]: Exit (root): Exited normally
Dec 28 11:10:41 DietPiProd dropbear[15987]: Child connection from 192.168.0.134:55659
Dec 28 11:10:48 DietPiProd dropbear[15987]: Bad password attempt for 'root' from 192.168.0.134:55659
Dec 28 11:10:51 DietPiProd dropbear[15987]: Password auth succeeded for 'root' from 192.168.0.134:55659
Dec 28 11:18:49 DietPiProd dropbear[15987]: Exit (root): Exited normally
Dec 28 11:28:21 DietPiProd dropbear[16286]: Child connection from 192.168.0.134:56276
Dec 28 11:28:26 DietPiProd dropbear[16286]: Password auth succeeded for 'root' from 192.168.0.134:56276
Dec 28 11:32:14 DietPiProd dropbear[16286]: Exit (root): Exited normally
Dec 28 17:27:02 DietPiProd dropbear[21231]: Child connection from 192.168.0.134:51803
Dec 28 17:27:08 DietPiProd dropbear[21231]: Password auth succeeded for 'root' from 192.168.0.134:51803
Dec 28 17:31:19 DietPiProd dropbear[21231]: Exit (root): Exited normally
Dec 28 18:36:20 DietPiProd dropbear[21833]: Child connection from 192.168.0.134:50477
Dec 28 18:36:25 DietPiProd dropbear[21833]: Password auth succeeded for 'root' from 192.168.0.134:50477
root@DietPiProd:~#