Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

zabbix web UI conflicts with Striker Web UI #755

Open
amanjot01 opened this issue Oct 24, 2024 · 0 comments
Open

zabbix web UI conflicts with Striker Web UI #755

amanjot01 opened this issue Oct 24, 2024 · 0 comments
Assignees
@digimer
Labels
3.1 Priorities bug High To be resolved once all urgent issues are clear
Milestone
3.1 Beta - blockers

Comments

@amanjot01
Copy link
Collaborator

amanjot01 commented Oct 24, 2024 •
edited
Loading

Check for the file name :- /etc/zabbix/zabbix_server.conf (which means zabbix server is installed)
Now edit the file to avoid port mismatch. So, that striker and zabbix web UI to work at :- /etc/httpd/conf/httpd.conf
Look for Listen if its :- Listen 80 then change it to Listen 8080

Thank you
Screenshot from 2024-10-24 12-38-34
@amanjot01 amanjot01 added bug High To be resolved once all urgent issues are clear 3.1 Priorities labels Oct 24, 2024
@amanjot01 amanjot01 added this to the 3.1 Beta - blockers milestone Oct 24, 2024
digimer pushed a commit that referenced this issue Oct 25, 2024
@digimer-bot
Updated anvil-daemon to auto-resolve port 80 conflicts with Zabbix.
a0e94a6 
Closes issue #755

Signed-off-by: Madison Kelly <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@digimer digimer

Labels
3.1 Priorities bug High To be resolved once all urgent issues are clear
Projects
None yet
Milestone
3.1 Beta - blockers
Development

No branches or pull requests
2 participants
@digimer @amanjot01