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…

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

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

포트 6379(TCP) 리스닝 실패로 설치 중단

지원 자체 호스팅

pangbo 10월 28, 2025, 7:00오전 2

이 줄은 무시하셔도 됩니다. 원시 로그의 끝부분을 보면 재구성이 성공했음을 알 수 있습니다.

글		댓글	조회수
Error when starting Discourse, Redis port already in use Self-hosting	10	1302	5월 20, 2019
Warning: Could not create server TCP listening socket *:6379: bind: Address already in use Self-hosting	3	6772	4월 9, 2023
Problem during ./launcher rebuild, Redis not starting the second time Self-hosting	0	74	2월 24, 2026
Error connecting to Redis on localhost:6379 Self-hosting	2	3064	6월 10, 2019
Error response on port 443 Support	3	1607	6월 11, 2017

포트 6379(TCP) 리스닝 실패로 설치 중단

Related topics