Hello, I’m not able to open my host, arborhub, in my browser despite being able to start/run checkmk.
I made some configurations to checkmk such as running the program behind nginx server instead of apache.
The error I get, is a 502 Bad Gateway page. When I type in the host in the address bar, I use my IPv4 address followed by arborhub.
Here is my output when I type sudo omd start arborhub and sudo omd status
Temporary filesystem already mounted
Starting agent-receiver...OK
Starting mkeventd...Already running.
Starting rrdcached...Already running.
npcd already started...
Starting nagios...Already running.
Starting apache...(already running: 6839)...OK
Starting redis...Already running.
Initializing Crontab...OK
Doing 'status' on site arborhub:
agent-receiver: running
mkeventd: running
rrdcached: running
npcd: running
nagios: running
apache: running
redis: running
crontab: running
-----------------------
Overall state: running
I’m also using Ubuntu Desktop 24.04, so running locally at the moment and using checkmk raw 2.3.0p30.
I don’t know if I configured something incorrectly in my nginx.conf, I’m willing to share that file if it’ll help. I asked on nginx forum, but they couldn’t figure it out either.
Please I need help with this, thank you.
Short question - why not using the normal supported setup with Apache also in the frontend?
Other question if you are directly on the machine where the site is running, can you access the internal Apache with http://localhost:5000/ ?
1 Like
No I can’t access http://localhost:5000/.
Not sure what you mean by normal setup with apache for the frontend. I chose to use nginx because I like it for a web server, reverse proxy and load balancer.
I decided to run checkmk behind checkmk because this is the only way to have both software applications running
Then in your setup something fundamentally is wrong.
Every single checkmk site is running his own Apache process and this process is listening on a port starting from 5000. You can configure other ports here but this is the default.
This means following the installation instructions as shown here Installation on Debian and Ubuntu
1 Like
Yes I know check runs on port 5000.
I configured that same port for my host within my nginx.conf file so that there wouldn’t be any conflicts between Apache and Nginx.
So there is no reason why this should be happening
At this point, I think I’m stick with Prometheus to monitor the network/traffic of my site
To my understanding, Prometheus doesn’t depend on Apache.
This has nothing to do with your problem that the website is not reachable.
Yes it does. Checkmk was working fine before, that is I was able to open in the browser.
But ever since I configured my nginx.conf for port 8000 for checkmk. This error page 502 started happening.
I don’t think it’s a coincidence
That’s why i said please install the system as it is described in the linked manual article.
The minimum what must work before you can try to use other reverse proxies, instead of Apache, is the localhost connection to the defined port of your site.
Okay, I’ll try this then.
I think that’s strange why it isn’t working, I mean followed this tutorial via YouTube https://www.youtube.com/watch?v=opO-SOgOJ1I, which also follows the checkmk docs.
Plus if it wasn’t installed, wouldn’t it not be running on my Linux Desktop terminal?
In this video is the normal install process described. Normal means with Apache as reverse proxy.
What do you see with an “ss -tulpn” command as open ports on your system?
1 Like
I decided to switch to Prometheus. And I didn’t run that command