# Nginx reverse proxy stopped working after applying upgrade from Rocky 8.4 to Rocky 8.8

**URL:** <https://forums.rockylinux.org/t/nginx-reverse-proxy-stopped-working-after-applying-upgrade-from-rocky-8-4-to-rocky-8-8/10900>\
**Category:** Rocky Linux Help & Support\
**Created:** [August 2, 2023, 2:22pm UTC](https://forums.rockylinux.org/t/nginx-reverse-proxy-stopped-working-after-applying-upgrade-from-rocky-8-4-to-rocky-8-8/10900 "2023-08-02T14:22:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![PREngineer](https://avatars.discourse-cdn.com/v4/letter/p/a587f6/32.png) [@PREngineer](https://forums.rockylinux.org/u/PREngineer)\
**Post date:** [August 2, 2023, 2:22pm UTC](https://forums.rockylinux.org/t/nginx-reverse-proxy-stopped-working-after-applying-upgrade-from-rocky-8-4-to-rocky-8-8/10900/1 "2023-08-02T14:22:07Z")

</div>

After upgrading my Rocky Linux from 8.4 to 8.8, my nginx 1.1.14 1-9 reverse proxy session doesn’t seem to operate as expected anymore. Instead I see a lot of FIN ACK packets (tcpdump) when loading my Graylog landing page such that it shows the below message. But when I directly go to my Graylog installation on port 9000 it loads fine.

Before the upgrade, I tested this and it worked fine. After the upgrade it no longer works. I know the upgrade had some security policy (selinux) upgrade as well. Any idea where I could be going wrong?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/1/1a8c6845e4274f5748e44e13fab8d3f8e3f5d43f.png)

---

<div class="post-metadata">

**Author:** ![PREngineer](https://avatars.discourse-cdn.com/v4/letter/p/a587f6/32.png) [@PREngineer](https://forums.rockylinux.org/u/PREngineer)\
**Post date:** [August 2, 2023, 2:51pm UTC](https://forums.rockylinux.org/t/nginx-reverse-proxy-stopped-working-after-applying-upgrade-from-rocky-8-4-to-rocky-8-8/10900/2 "2023-08-02T14:51:07Z")

</div>

It turns out that upgrade from 8.4 to 8.8 changes the security policy of the firewall. Maybe. I am yet to replicate this. Port 80 in my system was closed off after my upgrade. I had to add port 80 again in the firewall.

I will replicate this with production system update.
