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 t…

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 runni…

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

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

Support Self-hosting

pangbo October 28, 2025, 7:00am 2

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

Topic		Replies	Views
Error when starting Discourse, Redis port already in use Self-hosting	12	1216	October 3, 2022
Warning: Could not create server TCP listening socket *:6379: bind: Address already in use Self-hosting	3	6632	April 9, 2023
Problem during ./launcher rebuild, Redis not starting the second time Self-hosting	0	40	February 24, 2026
Error connecting to Redis on localhost:6379 Self-hosting	2	2997	June 10, 2019
Error response on port 443 Support	4	1563	June 12, 2017

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

Related topics