Right after Redis starts in the installation, it outputs this: Warning: Could not create server TCP listening socket *:6379: bind: Address already in use then Failed listening on port 6379 (TCP), aborting. I have no clue why this happens. I’ve switched the ports in the Redis configuration file and this problem still occurs. Other articles have not helped. Raw log: y23qwgerghfds - Pastebin.com Any help is appreciated!

You can simply ignore this line, as the end of your raw log shows the rebuilding succeeded.

Hi! Thank you, and this did help very much. However, I am also encountering this problem: when running ./discourse-setup the site returns this: [image] I do have the A address properly setup in my DNS records. Ports 443 and 80 are not in use and available when I run the setup command. When running curl https://mywebsite.app- curl: (7) Failed to connect to mywebsite.app port 443 after 33 ms: Couldn’t connect to server After killing what was using port 443 (it was being used during setup), and running curl again, it returned the same thing (the only difference being the times- 33ms → 2ms before outputting) Raw log - abc - Pastebin.com (I’m not sure if it’s supposed to output Discourse installed or something along those lines, however it does not do that) Running Ubuntu 24.04.3 LTS, Digital Ocean droplet

"Failed listening on port 6379 (TCP)" stops installation

Product Support Self-hosting

b11 (b ) October 29, 2025, 2:27am 4

Regarding above, the wrong A address was put in (private IP) instead of public IPV4. Oops! Thank you for helping!

Topic		Replies	Views
Error when starting Discourse, Redis port already in use Self-hosting	10	1457	May 20, 2019
Warning: Could not create server TCP listening socket *:6379: bind: Address already in use Self-hosting	3	6849	April 9, 2023
Problem during ./launcher rebuild, Redis not starting the second time Self-hosting	0	94	February 24, 2026
Error connecting to Redis on localhost:6379 Self-hosting	2	3117	June 10, 2019
Error response on port 443 Product Support	3	1647	June 11, 2017

"Failed listening on port 6379 (TCP)" stops installation

Related topics