The error is:

If you re-run the command, which is:
The command might fail again with the same error, or it will run with no problem.

firewalld isn't running and selinux is disabled. There aren't any errors in the apache logs. I've restarted httpd and the vm itself. Are there any more things I can look at before asking the networking team if anything is being blocked on that end?

[root@]# curl --head --show-error "ipaddr"
HTTP/1.1 200 OK
Date: Wed, 07 Sep 2022 15:51:11 GMT
Server: Apache/2.4.6 (CentOS) mod_wsgi/3.4 Python/2.7.5
Last-Modified: Wed, 07 Sep 2022 15:50:03 GMT
ETag: "6-5e818441e2915"
Accept-Ranges: bytes
Content-Length: 6
Content-Type: text/html; charset=UTF-8

[root@]# curl --head --show-error "ipaddr"
curl: (7) Failed connect to ipaddr:80; Connection refused

If it only fails sometimes then it seems either a networking or server load issue. Repeating the command should work, and sudo should not be needed with curl unless it is necessary at all times to write the output.

If you can help identify when and with what address it fails then it would be easier to trouble shoot. The "-L" option does do redirect so the failure may not have anything to do with you or the command, but may have to do with the way the initial server is performing the redirect and/or with the server and permissions at the final location.

I propose you contact the local network team since it is likely within their ballpark for the solution.

That last post seems to show that port 80 is not open on the server. Maybe firewall or maybe address error or maybe the web server is not running.

Thanks.

I asked the networking team so we'll see. There shouldn't be a boundary between subnets since they're in the same VRF but who knows. Is there another log location besides /var/log/httpd/ that might show curl refused connection attempts? This is just a base install of apache to serve a few files out.

If I do an nmap to the IP, sometimes it returns with 80 and sometimes it returns without 80 (or even 22).

Nmap scan report for hostname (ipaddr)
Host is up (0.00029s latency).
Not shown: 996 closed ports
PORT STATE SERVICE
53/tcp open domain
80/tcp open http
443/tcp open https
8080/tcp open http-proxy

Nmap done: 1 IP address (1 host up) scanned in 0.28 seconds
[root@]# nmap -sT ipaddr

Starting Nmap 6.40 ( http://nmap.org ) at 2022-09-07 11:34 CDT
Nmap scan report for hostname (ipaddr)
Host is up (0.00026s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
53/tcp open domain
443/tcp open https
5000/tcp open upnp

that can be a lot of things, like incorrect route, proxy, firewall or just unstable hardware (or dns error, dhcp problem or ....)
You are using VM, so this can be a problem inside the VM, or on the host or somewhere else (router?).