(I believe I responded directly to Mark, and that's why the answer ended up not appearing here for everyone to see, sorry) Hi,
First of all, thanks for the help and tips. A few hours after making this post, I managed to speak personally with the team that manages the University's firewall, and after explaining my situation in more detail, they found that there was a network block in communication between the internal and external IP. After the situation was resolved, the website was live and available both internally and externally. I was really out of ideas on what to check, trying to figure out what could be wrong with the system settings, but luckily everything is working fine now. Thank you very much. Em terça-feira, 30 de julho de 2024 às 11:47:16 UTC-3, [email protected] escreveu: > On Mon, Jul 29, 2024 at 03:33:03PM +0000, Leonardo Figueiredo wrote: > > - /var/log/apache2/error.log: > > > > [Mon Jul 29 11:32:05.836354 2024] [proxy:error] [pid 345333:tid > 140116479678144] (111)Connection refused: AH00957: http: attempt to connect > to 127.0.0.1:4000 (localhost:4000) failed > > [Mon Jul 29 11:32:05.836460 2024] [proxy_http:error] [pid 345333:tid > 140116479678144] [client 40.77.167.51:11411] AH01114: HTTP: failed to > make connection to backend: localhost > > [Mon Jul 29 11:32:05.860228 2024] [proxy:error] [pid 345492:tid > 140115657619136] (111)Connection refused: AH00957: http: attempt to connect > to 127.0.0.1:4000 (localhost:4000) failed > > [Mon Jul 29 11:32:05.860310 2024] [proxy_http:error] [pid 345492:tid > 140115657619136] [client 52.167.144.231:30290] AH01114: HTTP: failed to > make connection to backend: localhost > > [Mon Jul 29 11:32:06.461271 2024] [proxy:error] [pid 345492:tid > 140115632441024] (111)Connection refused: AH00957: http: attempt to connect > to 127.0.0.1:4000 (localhost:4000) failed > > [Mon Jul 29 11:32:06.461365 2024] [proxy_http:error] [pid 345492:tid > 140115632441024] [client 40.77.167.51:11393] AH01114: HTTP: failed to > make connection to backend: localhost > > "Connection refused" means that nothing is listening to port 4000 on > localhost. I would start by figuring out why. I would try to find > out what the front-end *is* listening for, and correct that if > necessary. Here 'netstat -tlnp | grep PM2' worked for me. > > When certain that the front end is listening properly, if the problem > persists then I would next check for firewall REJECT rules that might > be blocking connections. > > > PS: sorry for my English, I hope you can understand me well > > Your English is quite good enough for me to understand. > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 <(317)%20274-0749> > library.indianapolis.iu.edu > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/308f4c01-c41a-4986-b3fd-40d033e03af4n%40googlegroups.com.
