-
Notifications
You must be signed in to change notification settings - Fork 6
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.
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
zabbix web UI conflicts with Striker Web UI #755
Milestone
Comments
amanjot01
added
bug
High
To be resolved once all urgent issues are clear
3.1 Priorities
labels
Oct 24, 2024
digimer
pushed a commit
that referenced
this issue
Oct 25, 2024
Closes issue #755 Signed-off-by: Madison Kelly <[email protected]>
Tested successfully. |
@fabbione - We spoke about this before the holidays... Do you recall what the suggested approach should be? |
Deal with this using apache reverse proxy; link / example to follow. |
|
Coordinate with @ylei-tsubame to have Striker detect Zabbix install and add an icon in Striker to link to Zabbix. Perhaps use NextJS for the 8080 reverse proxy. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: