The discussion revolves around issues during the installation of Discourse, specifically related to Redis and port configuration. b11 reports a Redis error indicating that port 6379 is already in use, which halts the installation. pangbo suggests that this warning can be ignored. However, b11 encounters further problems, including a failed connection to port 443 when running curl, despite proper DNS setup and available ports. The issue appears to stem from an incorrect A record in the DNS settings, which was later corrected. b11 acknowledges the help and confirms the problem was due to a misconfigured private IP address.
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:
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
Regarding above, the wrong A address was put in (private IP) instead of public IPV4. Oops! Thank you for helping!
