Ad Widget

Collapse

Zabbix/nginx Dashboard Listening Port Change (help!)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ab310
    Junior Member
    • May 2024
    • 2

    #1

    Zabbix/nginx Dashboard Listening Port Change (help!)

    Hello,

    We just setup Zabbix and it's working great. The only "problem" I seem to be having is, I can't for the life of me figure out how to change the default port for the dashboard from http://hoopy.frood:8080 to just plain old 80 (so, http://hoopy.frood).

    To date, I've tried editing the zabbix.conf and nginx.conf and referencing the nginx docs RE: server blocks, but I apparently cannot figure out the correct configuration to change this. I'm just not sure what I'm missing. I can't seem to find much in the way of similar situations online; usually it's people trying to move from port 80 to something else, though even trying to extrapolate from that leads me to a non-working config. I've done this in the past with Apache, but nginx is new to me and I can't figure this out no matter how many times I RTFMs and trial-and-error changes.

    So, I'm throwing myself upon the kindness of the community. I 100% know it's a nginx config issue, I'm hoping someone here can point me in the right direction. I'm kind of frustrated at this point.

    Setup:
    Zabbix = 6.4.14
    Nginx = 1.20.1
    OS = Rocky Linux 9.3
    There is nothing else running on this server but Zabbix. Everything else is pretty much standard. Zabbix was installed per the docs on the Zabbix site for this OS/web server combo. Nginx was setup out of the box dnf. I've made no changes that weren't in the Zabbix instructions.
  • Hamardaban
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • May 2019
    • 2713

    #2
    Try to search whole fs for config string by "grep -R "listen.*8080" /"

    Comment

    • ab310
      Junior Member
      • May 2024
      • 2

      #3
      I am a complete idiot!

      At some point I apparently didn't tack
      Code:
      --permanent
      on the butt-end of my firewall-cmd commands, so all the changes I made to nginx didn't matter. I was SOOO confident the firewall settings were not the cause and I had double checked that the appropriate services were configured. And they were not. ;_;

      So, apologies for anyone that wasted time reading this.

      My only hope is that perhaps someone else in the future in a similar situation will stumble across this post and save themselves a heap of embarrassment.

      Comment

      Working...