localhost doesn't work on Yosemite - osx-yosemite

I have just today upgraded to Yosemite. I've not had a mac long. But with the update my localhost doesn't work. Chrome returns This webpage is not available. I've tried
sudo apachectl start to try and get it back but no luck. I'm a new mac user and haven't had to undergo an OS update, so not really sure where to start.

I've stolen the following from
https://github.com/liip/php-osx/issues/75 and http://php-osx.liip.ch/#uninstall
1. reinstall PHP
homebrew helps with this
brew update
brew upgrade
brew uninstall --force php54
brew unlink php54
brew uninstall --force php55
brew unlink php55
rm -rf /usr/local/php5*
brew install php55
2. where is libphp5.so?
please comment out the existing 'LoadModule php5_module' in /private/etc/apache2/httpd.conf and add this
LoadModule php5_module /path/to/lib/libphp5.so
3. delete +php-osx.conf and +entropy-php.conf
delete the files
+php-osx.conf
+entropy-php.conf
in
/etc/apache2/other
4. testing if everything works
try to start apache with
sudo apachectl start

did you try
apachectl configtest
to see if it really is running?
I've just found this:
http://macosx.com/threads/apache-wont-start-up.299851/
-> summary
'Apache couldn't find a certain log file'
cd /private/var/log
sudo mkdir apache2

I'm just upgraded my mac into yosemite, and boom my apache isn't working. i follow the instruction from here, and my localhost is back to normal again, here the simple steps i did.
Open your httpd.conf located on /etc/apache2, please open with sudo like sudo vi httpd.conf (i'm using vim to open the file, for most simple steps)
Find the line with this value LoadModule php5_module libexec/apache2/libphp5.so, you will found it marked with #, so delete the hash (#) and save the file by press ESC => type :wq (command for write and quit)
Restart your apache by using command sudo apachectl restart
See your localhost on browser
*tips:
For fast on searching you can press ESC and then /, and type php5_module => ENTER
You can also remove the mark (hash) fot these line, if you need to enable rewrite_module to activate mod_rewrite and vhost_alias_module for virtual-host on your machine.
*warning
If your MOD_REWRITE still doesn't work, in order to use .htaccess try to check this.
Find the section and change
AllowOverride None to AllowOverride All

Solution in Jan 2016 for El Capitan
None of the other answers worked for me.
run sudo apachectl configtest
I got an error:
AH00526: Syntax error on line 20 of /private/etc/apache2/extra/httpd-mpm.conf: Invalid command 'LockFile', perhaps misspelled or defined by a module not included in the server configuration
That lead me to https://apple.stackexchange.com/questions/211015/el-capitan-apache-error-message-ah00526 and the solution
Edit the file /etc/apache2/extra/httpd-mpm.conf to remove this part:
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
<IfModule !mpm_winnt_module>
<IfModule !mpm_netware_module>
LockFile "/private/var/log/apache2/accept.lock"
</IfModule>
</IfModule>
I commented that out, rolled back all the other changes(except brew update/upgrade).

My problem here was the httpd.conf file and this line
Include /private/etc/apache2/other/*.conf
Where it tried to load the osx version of PHP I had. I needed to change it to my PHP version
Include /private/etc/apache2/other/php5.conf
Permissions seem to be an issue now however.

I just did:
brew update
brew upgrade
and
sudo apachectl restart
..."It works!"

I ran into this too after upgrading Yosemite recently. Neither localhost nor 127.0.0.1 would resolve. Apparently Yosemite activated or reconfigured a Firewall (System Preferences > Security & Privacy > Firewall [tab]).
I resolved the issue by accessing the Firewall Options and unchecking the box labelled 'Block all incoming connections'. Probably more importantly - that caused the 'Enable stealth mode' option below it to be switched off. That, stealth mode, was likely the culprit.
After saving above changes localhost & 127.0.0.1 worked fine for me again.

Related

How can I resolve Homebrew openssl conflicts?

I am on High Sierra 10.13.6 and I recently ran into an issue with my Homebrew environment for local dev work. I can't seem to figure out what is the problem. Any Composer or Drush commands will give this
dyld: Library not loaded: /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib
Referenced from: /usr/local/bin/php
Reason: image not found
Abort trap: 6
I restarted my computer and when I try to start apachectl; I get
httpd: Syntax error on line 179 of /usr/local/etc/httpd/httpd.conf: Cannot load /usr/local/Cellar/php71/7.1.12_23/libexec/apache2/libphp7.so into server: dlopen(/usr/local/Cellar/php71/7.1.12_23/libexec/apache2/libphp7.so, 10): Library not loaded: /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib\n Referenced from: /usr/local/Cellar/php71/7.1.12_23/libexec/apache2/libphp7.so\n Reason: image not found
I think this is because the path is looking for openssl, but in the Brew list, I don't have openssl anymore, it is now openssl#1.1
Bash profile has the following:
export PATH="/usr/local/opt/openssl#1.1/bin:$PATH"
export LDFLAGS="-L/usr/local/opt/openssl#1.1/lib"
export CPPFLAGS="-I/usr/local/opt/openssl#1.1/include"
$which openssl returns
/usr/local/opt/openssl#1.1/bin/openssl
What can I do to resolve this? Maybe I'm missing the obvious.
So in case anyone runs into this. I managed to fix this myself.
First I commented out the following line in my usr/local/etc/httpd/httpd.conf file
LoadModule php7_module /usr/local/Cellar/php71/7.1.12_23/libexec/apache2/libphp7.so
Next I ran
$brew install php#7.3
I added the following lines to .bash_profile
export PATH="/usr/local/opt/php#7.3/bin:$PATH"
export PATH="/usr/local/opt/php#7.3/sbin:$PATH"
Then added the following line to usr/local/etc/httpd/httpd.conf file
LoadModule php7_module /usr/local/Cellar/php#7.3/7.3.13/lib/httpd/modules/libphp7.so
Then I restarted my computer then ran
$brew services start php#7.3
$brew services restart httpd
$sudo apachectl -k restart
Then I had some sql connection issues.
$brew upgrade mariadb
$brew services restart mariadb
$brew services restart httpd
$sudo apachectl -k restart
And everything came together. Hope this helps.
If that helps somebody else not willing to reinstall PHP:
ln -s /usr/local/Cellar/openssl/1.0.2s/lib/libcrypto.1.0.0.dylib /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib
ln -s /usr/local/Cellar/openssl/1.0.2s/lib/libssl.1.0.0.dylib /usr/local/opt/openssl/lib/libssl.1.0.0.dylib

phpmyAdmin admin page displays only "demo server"

Linux Mint 18
Apache2 server
MYSQL Server
Hello! Does anyone have a moment to advise me?
Here's my problem in brief: I am trying to configure phpMyAdmin on a Linux Mint 18 computer, but when I try to view http://localhost/phpmyadmin/, I get a "phpMyAdmin demo server" screen.
Details:
The phpMyAdmin web page begins with an addJSON statement, and echoes this message:
'You are using the demo server. You can do anything here, but please do not change root, debian-sys-maint and pma users'
I understand I am viewing some sort of demonstration page for phpMyAdmin, but I would rather view the actual, familiar phpMyAdmin administration page.
Do I need to edit the Apache2.conf file? Or something else? Thank you very much for your time.
Eric
i had this problem with ubuntu 16.04
fix
1# Remove phpmyadmin completely
sudo apt-get remove phpmyadmin
2# Install phpmyadmin with this command
sudo apt-get install phpmyadmin apache2-utils
3# add phpmyadmin to the apache configuration
sudo nano /etc/apache2/apache2.conf
And put below line to end of the file
Include /etc/phpmyadmin/apache.conf
4# restart apache2
sudo systemctl restart apache2
or
sudo service apache2 restart
I had the same problem, but my error was because I commented the Handler in php.ini
<FilesMatch \.php$>
SetHandler application/x-httpd-php
</FilesMatch>
I just enable php on apache and start work normal
a2enmod php7.3
I had to disable mpm_event because it was causing some comflict
a2dismod mpm_event
Perhaps PHP code is not being executed, instead code shows on the page or Apache shows php code instead of executing may help.
Linux Mint is similar to Ubuntu/Debian, so you need the libapache2-mod-php5 package installed (assuming you've used the package manager to install the rest of your PHP/Apache stack): sudo apt-get install php5 libapache2-mod-php5.
You can test this further by adding a file (called test.php or phpinfo.php or whatever else suits you) in the main phpMyAdmin folder with the content <?php phpinfo(); ?> -- then try to load that file directly and see if you get a long list of system status or simply the contents of the file displayed. The main reason to put it in the phpMyAdmin folder is that your Apache configuration might handle different folders differently, this is the simplest way to test what happens on that particular folder.

After install OS X El Capitan, Apache not working

I just installed in my MacBook pro "El capitan" and I can't type any host set it in vhost. Everything was working perfectly before in Yosemite. When I type one of my virtualhost I get:
403 "Forbidden You don't have permission to access / on this server."
What did I try ?
go to /etc/apache2/httpd.conf
and uncoment this lines:
Include /private/etc/apache2/extra/httpd-vhosts.conf
LoadModule vhost_alias_module libexec/apache2/mod_vhost_alias.so
/etc/apache2/extra/httpd-vhosts.conf is the same file that was working before in Yosemite since long time ago, so I haven't modified.
To install everything in Yosemite I used homebrew.
Another problem related with "El capitan", before I was able to type http://localhost/~myuser/ and I could access to any folder in /Users/myuser/Sites now I get this message: 404 not found.
I hope some help, I am not specialist in servers and it's really difficult to me to set it up, and is very annoying to waste a lot of time anytime there is a new upgrade in the OS.
The upgrade process keeps a copy of your old httpd.conf. Unless you were way out of date, just overwrite the new file with your old one. Keep a copy of the new just in case...
sudo cp /etc/apache2/httpd.conf /etc/apache2/httpd.conf.after-update
sudo mv /etc/apache2/httpd.conf.pre-update /etc/apache2/httpd.conf
sudo apachectl restart
I had the same trouble.
Type this command line you will have the error from apache :
apachectl configtest
If you have this error :
AH00526: Syntax error on line 20 of /private/etc/apache2/extra/httpd-mpm.conf: Invalid command 'LockFile', perhaps misspelled or defined by a module not included in the server configuration.
so this link can help : https://apple.stackexchange.com/questions/211015/el-capitan-apache-error-message-ah00526
I experienced that after the upgrade to El Capitan the line
Include /private/etc/apache2/extra/httpd-userdir.conf
in
/private/etc/apache2/httpd.conf
was commented again. After uncommenting it and restarting apache, everything worked alright again.
I have merged to two versions (httpd.conf and http.conf~previous) and after that I discovered that the v-host wasn't working anymore.
After disabling rule 19 #NameVirtualHost *:80 in /private/etc/apache2/extra/httpd-vhosts.conf everything worked again!
LockFile is a directive of Apache ≤ 2.2. El Capitan comes with Apache version 2.4. so, you need to disable LockFile
First, just to be sure apache is stopped:
sudo apachectl stop
Then edit your httpd-mpm.conf:
Comment this lines
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
<IfModule !mpm_winnt_module>
<IfModule !mpm_netware_module>
LockFile "/private/var/log/apache2/accept.lock"
</IfModule>
</IfModule>
Start apache sudo apachectl start and that's all
As some have mentioned the problem is that the upgrade to El Capitan backed up your previous httpd.conf and renamed it httpd.conf~previous and gave you a new httpd.conf. What you need to do though with these files to fix your problem is:
Use nano or other editor to open httpd.conf~previous and look for these 2 lines:
DocumentRoot "/Users/my-machine-name/Prev-Localhost-Path
<Directory "/Users/my-machine-name/Prev-Localhost_path">
Copy them and then using nano open httpd.conf and look for these 2 lines:
DocumentRoot "/Library/WebServer/Documents"
<Directory "/Library/WebServer/Documents">
Comment them out by entering the '#' character in front of each one, and then below them paste in the two lines you copied from your original file. Save the file and exit.
After that you'll need to reboot. My setup would not work until I made these changes and then rebooted. But perhaps the suggestion by DSG to restart apache will suffice:
sudo apachectl restart

phpmyadmin "Not Found" after install on Apache, Ubuntu

Setting up a development environment with Ubuntu 14.04 running in VirtualBox, following this guide: http://klau.si/dev
After installing phpmyadmin, it seems I should be able to access it at http://localhost/phpmyadmin but apache returns a Not Found error. Did this guide leave out a configuration step somewhere? I have already tried restarting the apache service.
There is no phpmyadmin.conf file in apache2/sites-enabled or apache2/sites-available, is this required?
If so, where can I find these files?
using 127.0.0.1 instead of localhost returns the same error. The default apache page at http://localhost works just fine.
the console in the browser shows nothing of value, simply Not Found.
I have also tried rerunning the install script with dpkg-reconfigure -plow phpmyadmin
This issue was resolved thanks to this guide: https://help.ubuntu.com/community/ApacheMySQLPHP#Troubleshooting_Phpmyadmin_.26_mysql-workbench by adding
Include /etc/phpmyadmin/apache.conf
...to the /etc/apache2/apache2.conf file and restarting the service.
Try this
sudo ln -s /etc/phpmyadmin/apache.conf /etc/apache2/conf-available/phpmyadmin.conf
sudo a2enconf phpmyadmin.conf
sudo systemctl restart apache2
sudo dpkg-reconfigure -plow phpmyadmin
Select No when asked to reconfigure the database. Then when asked to choose apache2, make sure to hit space while [ ] apache2 is highlighted. An asterisk should appear between the brackets. Then hit Enter. Phpmyadmin should reconfigure and now http://localhost/phpmyadmin should work. for further detail https://www.howtoforge.com/installing-apache2-with-php5-and-mysql-support-on-ubuntu-13.04-lamp
The easiest way to do in ubuntu (I tested in ubuntu-20.04):
Step 1. Open the file:
sudo nano /etc/apache2/apache2.conf
Step 2: Add the following line at the end of file:
Include /etc/phpmyadmin/apache.conf
Step 3: Restart apache2:
sudo systemctl restart apache2.service
Create a link in /var/www like this:
sudo ln -s /usr/share/phpmyadmin /var/www/
Note: since 14.04 you may want to use /var/www/html/ instead of /var/www/
If that's not working for you, you need to include PHPMyAdmin inside apache configuration.
Open apache.conf using your favorite editor, mine is nano :)
sudo nano /etc/apache2/apache2.conf
Then add the following line:
Include /etc/phpmyadmin/apache.conf
For Ubuntu 15.04 and 16.04
sudo ln -s /etc/phpmyadmin/apache.conf /etc/apache2/conf-available/phpmyadmin.conf
sudo a2enconf phpmyadmin.conf
sudo service apache2 reload
Finally I got the solution
sudo ln -s /etc/phpmyadmin/apache.conf /etc/apache2/conf-available/phpmyadmin.conf
sudo a2enconf phpmyadmin
sudo service apache2 reload
More about
https://askubuntu.com/questions/55280/phpmyadmin-is-not-working-after-i-installed-it
Create a link in /var/www/html like this to fix the error:
sudo ln -s /usr/share/phpmyadmin /var/www/html
For anyone still running into issues with this- check that you're actually using apache! I knocked my head against this for 20 minutes or so before I remembered...I use NginX on this server...=). #john-smith, this one's for you buddy.
To get it working on nginx, all you should have to do is create a sim link and restart php:
sudo ln -s /usr/share/phpmyadmin /var/www/html
Note that for you, it may be /var/www/ and not /var/www/html, depending on your dir structure.
sudo ln -s /etc/phpmyadmin/apache.conf /etc/apache2/conf-available/phpmyadmin.conf
sudo ln -s /usr/share/phpmyadmin /var/www/html/phpmyadmin
sudo service apache2 restart
Run above commands issue will be resolved.
Run the following command in terminal:
sudo ln -s /usr/share/phpmyadmin /var/www/html/
It seems like sometime during the second half of 2018 many php packages such as php-mysql and phpmyadmin were removed or changed. I faced that same problem too. So you'll have to download it from another source or find out the new packages
You will need to configure your apache2.conf to make phpMyAdmin works.
sudo nano /etc/apache2/apache2.conf
Then add the following line to the end of the file.
Include /etc/phpmyadmin/apache.conf
Then restart apache
sudo service apache2 restart
I had the same issue where these fixes didn't work.
I'm on Ubuntu 20.04 using hestiaCP with Nginx.
Today after adding
Include /etc/phpmyadmin/apache.conf
into both Apache and Nginx, Nginx failed to restart. It was having an issue with "proxy_buffers" value.
Yesterday I had to modify the Nginx config to add and increase these values so Magento 2.4 would run. Today I altered "proxy_buffers" again
proxy_buffers 3 64k;
proxy_buffer_size 128k;
proxy_busy_buffers_size 128k;
After the second alteration and the removal of "Include /etc/phpmyadmin/apache.conf" from both Apache and Nginx, Magento 2.4 and PHPMyAdmin are working as expected.
I didn't try Rashmi Jain's symlink answer. It seems like it would work. But if it doesn't work for you, perhaps try this.
I just created the file `/etc/apache2/conf-available/phpmyadmin.conf' and added this line to it:
Include /etc/phpmyadmin/apache.conf
(rather than putting it into /etc/apache2/apache2.conf as in Anonymous Man's answer)
Then:
sudo a2enconf phpmyadmin
sudo systemctl reload apache2
I had the same problem after installing mysql, apache2, php and finally phpmyadmin after each other. In my case it was solved by restarting apache2 (no need to update any configuration file):
sudo systemctl restart apache2
#John smith, I was facing the same issue of not being able to access phpmyadmin for 3 days, I found the solution.
-- Get xampp, check this tutorial https://youtu.be/VHfij95yOpo
-- Run this command before starting xampp app
sudo /etc/init.d/apache2 stop
sudo service mysql stop
That's it, it worked for me
first go to the location of phpmyadmin via terminal then type this
code php -S localhost:8001
First check PhpMyAdmin is install or not. If it is installed then search PhpMyadmin folder. After search cut and paste that folder in location Computer->var->www->html->paste folder. Open browser and type localhost/phpMyAdmin and login using username and password.
If you are having this problem in 2019, go to your 000-default.conf file, by typing this subl /etc/apache2/sites-enabled/000-default.conf (in your terminal to open the file in sublime editor)
When the file loads, locate "The ServerName directive sets the request scheme" and place this "Include /etc/phpmyadmin/apache.conf" on top .
Then restart your apache with the command...service apache2 restart That will certainly fix the issue. Hope it helps!

Munin server with apache - You don't have permission to access /munin on this server

On a fresh apache and munin server install when I to to domain.com/munin I get this error.
Forbidden
You don't have permission to access /munin on this server.
for these directories I did a chown -R munin:munin
dbdir /var/lib/munin
htmldir /var/cache/munin/www
logdir /var/log/munin
rundir /var/run/munin
What am I supposed to do with apache? I restated apache with /etc/init.d/apache restart but still get forbidden. I have made no changes to the apache config files from a fresh apache install.
Apache < 2.4
Open the Munin Apache config file:
vim /etc/munin/apache.conf
change the the following lines:
Order allow,deny
Allow from localhost 127.0.0.0/8 ::1
Options None
like so:
Order allow,deny
Allow from all
Options FollowSymLinks SymLinksIfOwnerMatch
Restart Apache and you're golden.
Apache > 2.4
Open the Munin Apache config file:
vim /etc/munin/apache24.conf
change the the following lines:
Require local
Options None
like so:
Require all granted
Options FollowSymLinks SymLinksIfOwnerMatch
Restart Apache and you're golden.
sudo service apache2 restart
For Apache 2.4 (which ships with Ubuntu 13.10), the /etc/munin/apache.conf configuration file syntax has changed:
Order allow, deny
Allow from all
needs to be changed to
Require all granted
Additional detail regarding upgrading from Apache 2.2 to Apache 2.4 can be found in the Apache upgrade notes.
I had the same problem, and none of the advices were helpful.
So I've browsed a little bit in the directory tree, and found the apache24.conf file. So I've add to this /etc/munin/apache24.conf file the following, as j7nn7k described:
Require all granted
Options FollowSymLinks SymLinksIfOwnerMatch
And of course I deleted the old values.
Now It's working!
I don't know if it's the same problem but I found a solution that fixed it for me.
I followed the tutorial here (from the italian ubuntu wiki), and changed the string from:
htmldir /var/cache/munin/www
To:
htmldir /var/www/munin
Then I edited the file:
vim /etc/munin/apache.conf
Allowing from all, as Johe Green did. But then take a close look to the Directory path, since it must be modified as the htmldir path in the munin conf.
Alias /munin /var/www/munin
<Directory /var/www/munin>
Order allow, deny
Allow from all
[...]
I had the same issue, after a clean install of apache2, munin and munin-node on Ubuntu 12.04LTS. Tried all the suggested options above with no effect. Found in the end that I had to
chmod 755 /var/www/munin
chown -R munin:munin /var/www/munin
That solved it for me.
cd /pub
more beer
I'm using apache 2.4.10 and munin 2.0.25-1 on ubuntu 15.04
To solve the problem, I followed Lars' sugestion, i.e. using Require all granted, but applying the changes to the file /etc/munin/apache24.conf
Changing /etc/munin/apache.conf had no effect for me. I have tried to grep me to the file determining which apache config file is chosen without success. But at list I solve the problem.
I faced the same problem and changed the /etc/munin/apache.conf line to Allow from all but still got the same 403 Forbidden error, I also had to change munin-node.conf
Comment block from munin-node.conf file where I made a change
#A list of addresses that are allowed to connect. This must be a
regular expression, since Net::Server does not understand CIDR-style
network notation unless the perl module Net::CIDR is installed. You
may repeat the allow line as many times as you'd like
Added my munin IP here in similar format and it worked
allow ^127.0.0.1$
P.S I am running munin master and node on the same box when testing this.
I have the same issue when create a soft link named 'share' under the root document and let it point to a package like /Users/me/desktop/share
firstly I do
chmod 655 /Users/me/desktop/share
I can not work
then I do
chmod 655 /Users/me/desktop
It works, I can see the 'share' listed under the root document path.
I user Mac Yosemite 10.10.3 and its in build Apache 2.4
hope its helpful
I was having the same problem as the OP using Ubuntu 14.04 and the stock versions available with apt-get. I tried the official Ubuntu documentation, the DigitalOcean instructions, and couldn't get graphs to show up (403 errors). I uninstalled (purged)/reinstalled munin since it was supposedly a random bug. I finally had luck when following this howtoforge writeup. It does not aim to move munin data from /var/cache/munin/www. Rather, it ensures:
Extra plugins are installed: apt-get install munin munin-node munin-plugins-extra
Apache fcgid is enabled: a2enmod fcgid
A sparse /etc/munin/apache.conf file is used (see below)
Replace your entire /etc/munin/apache.conf file contents with:
Alias /munin /var/cache/munin/www
<Directory /var/cache/munin/www>
# Require local
Require all granted
Options FollowSymLinks SymLinksIfOwnerMatch
Options None
</Directory>
ScriptAlias /munin-cgi/munin-cgi-graph /usr/lib/munin/cgi/munin-cgi-graph
<Location /munin-cgi/munin-cgi-graph>
# Require local
Require all granted
Options FollowSymLinks SymLinksIfOwnerMatch
<IfModule mod_fcgid.c>
SetHandler fcgid-script
</IfModule>
<IfModule !mod_fcgid.c>
SetHandler cgi-script
</IfModule>
</Location>
I had the same issue and solved it.
I was using Munin with Apache 2.4.18 so there was a seperate configuration file (/etc/munin/apache24.conf) which I had to edit.
Editing /etc/munin/apache.conf had NO effect.
Here is my complete install procedure for installing Munin on Linux Mint 17.3 (kernal 3.19), and should also work with recent Ubuntu.
Unlike Monit, Munin does not have its own web server, so is a bit more complicated to install.
#!/bin/bash
# Install script for Apache 2 with MySQL, PHP 5, etc.
# Update the Package Lists
apt-get update
# Install the MySQL Server and Client before installing Apache
apt-get install mysql-server mysql-client
# Install Apache
apt-get install apache2
# Install PHP5
apt-get install php5 libapache2-mod-php5
# Restart Apache
/etc/init.d/apache2 restart
# Install some extras
apt-get install snmp php5-mysql php5-curl php5-gd php5-idn php-pear php5-imagick php5-imap php5-mcrypt php5-memcache php5-ming php5-ps php5-pspell php5-recode php5-snmp php5-sqlite php5-tidy php5-xmlrpc php5-xsl
# Once again, restart
/etc/init.d/apache2 restart
# Install the Munin Server and the Client
apt-get install munin munin-node
# Restart the machine
shutdown -r now
Ignore the uninstall part and replace your entire /etc/munin/apache.conf file contents as hamx0r says earlier in this thread (please vote up his post):
https://stackoverflow.com/a/35656044/5178979
"Allow from all" makes sense to me, but it no longer works.
Maybe because I installed Munin prior to installing Apache2, I was missing the following symbolic links:
/etc/apache2/conf-available/munin.conf -> ../../munin/apache.conf
/etc/apache2/conf-enabled/munin.conf -> ../conf-available/munin.conf
cd /etc/apache2/conf-available && ll
If you do not see the link, create it:
ln -s ../../munin/apache.conf munin.conf && ll
If the first file is missing, this one is probably also missing
cd /etc/apache2/conf-enabled/ && ll
Create the link:
ln -s ../conf-available/munin.conf munin.conf && ll
Restart Apache2, wait 5 minutes, and hopefully it works.
If you want to monitor a machine other than the one running Munin, you simply install munin-node, and then add a line to /etc/munin/munin-node.conf
Find this line
allow ^127.0.0.1$
Add another similar line that includes the address of the munin server like:
allow ^192.168.1.100$
This is not necessary for Windows clients running munin-node.
Don't forget to add machines you want to monitor to your Munin server
/etc/munin/munin.conf
# MyMachine
[MyMachineName.mydomain]
address 127.0.0.1
use_node_name yes
Now for a question for the experts. Why do some machines not report hard drive temperature? I know that is a vague question and probably needs more details.
Edit /etc/munin/apache.conf and uncomment the 4 lines following from AuthUserFile.
AuthUserFile /etc/munin/.htpasswd
AuthName "Munin"
AuthType Basic
require valid-user