Alright, so a recently I got a message from my Uptime Monitor that my Discourse Forum went down. I checked what was going on. It was offline. Though the server it was running on was online. I rebuilt the app to start it again. Then I got this error: [image] The only error messages I found, were following: [image] [image] I don‘t have anything else running under that port though. Can anyone help me? I do not know what I should do. Thanks in advance.

How was this installed? What else is on the machine if anything?

It was installed a while ago following the install guide. It just randomly went offline. I run a Minecraft Server on the Server too. Though, it does not use Redis and it uses port 19132 so that should not be a problem. It has always worked with it. What I have noticed though, that if I go to the domain to my forum I get a page from nginx saying it works. @Stephen

If you docker ps what do you see? What’s the output of docker info? Which plugins do you have installed?

Sorry for the late response: [image] I only had one plugin installed, the Check Mark thing for support. @Stephen

And if you netstat -tulpn | grep 6379 ?

[image] Stephen: netstat -tulpn | grep 6379 Command not found. Do I need to run it in the discourse folder?

Is the server running ubuntu? If so sudo apt-get install net-tools The path you run it from isn’t important.

It‘s running debian, which is basically ubuntu… Yeah. I‘ll install that then I will run the command.

[image] Nothing happens [image] Stephen: netstat -tulpn | grep 6379

Error when starting Discourse, Redis port already in use

Product Support Self-hosting

MST2 May 20, 2019, 7:52pm 8

Command not found.
Do I need to run it in the discourse folder?

Topic		Replies	Views
Newest Discourse Version breaks rebuild, Redis Port already in use Self-hosting	7	1603	December 2, 2020
Discourse Randomly Does Not run or Rebuild Self-hosting postgres	15	586	March 22, 2025
Port already in use, what to do? Self-hosting	26	20041	March 6, 2020
Error connecting to Redis Self-hosting	17	7463	March 21, 2023
Warning: Could not create server TCP listening socket *:6379: bind: Address already in use Self-hosting	3	6845	April 9, 2023

Error when starting Discourse, Redis port already in use

Related topics