Pages

[ozstar]

Hi, Happy New Year.

Today with the apache2 status command on our home Linux VB server I see this for the first time and I do not know why.

Apache has been running 3 days with no touching.

There is one dom we have wordpress on and it has been fine and untouched for this to happen.

Any help please?

oz

apache2.service - The Apache HTTP Server
     Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-01-03 11:22:01 AEDT; 21h ago
       Docs: https://httpd.apache.org/docs/2.4/
    Process: 630 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
    Process: 3433 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCESS)
   Main PID: 807 (apache2)
      Tasks: 11 (limit: 10660)
     Memory: 62.5M
     CGroup: /system.slice/apache2.service
             ├─ 807 /usr/sbin/apache2 -k start
             ├─3437 /usr/sbin/apache2 -k start
             ├─3439 /usr/sbin/apache2 -k start
             ├─3440 /usr/sbin/apache2 -k start
             ├─3441 /usr/sbin/apache2 -k start
             ├─3547 /usr/sbin/apache2 -k start
             ├─3548 /usr/sbin/apache2 -k start
             ├─3549 /usr/sbin/apache2 -k start
             ├─3550 /usr/sbin/apache2 -k start
             ├─3551 /usr/sbin/apache2 -k start
             └─3552 /usr/sbin/apache2 -k start

Jan 04 04:56:49 zorin162-VirtualBox phpMyAdmin[3437]: user denied: root (mysql-denied) from 134.122.19.42
Jan 04 04:56:50 zorin162-VirtualBox phpMyAdmin[3437]: user denied: root (mysql-denied) from 134.122.19.42
Jan 04 04:56:50 zorin162-VirtualBox phpMyAdmin[3437]: user denied: root (mysql-denied) from 134.122.19.42
Jan 04 04:56:51 zorin162-VirtualBox phpMyAdmin[3437]: user denied: root (mysql-denied) from 134.122.19.42
Jan 04 04:56:51 zorin162-VirtualBox phpMyAdmin[3437]: user denied: root (mysql-denied) from 134.122.19.42
Jan 04 04:56:52 zorin162-VirtualBox phpMyAdmin[3437]: user denied: root (mysql-denied) from 134.122.19.42
Jan 04 04:56:52 zorin162-VirtualBox phpMyAdmin[3437]: user denied: root (mysql-denied) from 134.122.19.42
Jan 04 04:56:53 zorin162-VirtualBox phpMyAdmin[3437]: user denied: root (mysql-denied) from 134.122.19.42
Jan 04 04:56:53 zorin162-VirtualBox phpMyAdmin[3437]: user denied: wordspress (mysql-denied) from 134.122.19.42
Jan 04 04:56:54 zorin162-VirtualBox phpMyAdmin[3437]: user denied: wordpress (mysql-denied) from 134.122.19.42
root@zorin162-VirtualBox:~#

In the URL I get..

192.168.20.83/rootsofausssie
Not Found
Not found apache Port 80
--------------------------

EDIT:

I have just done a apache2 status again and it says it us running but does not show the mysql or wordpress erros above.
It still does not resolve the wp site though.

[mario]

What error do you get on the page when you visit it?

[ozstar]

Thank you for the inquiry.

The normal URL I am using as I build the site is 192.168.20.83/mysite and the reply I now get is..

Not Found
The requested URL was not found on this server.
Apache/2.4.41 (Ubuntu) Server at 192.168.20.83 Port 80

I have tried many things in my search however it is still the same.

I do have root access to the terminal and I do have access to phpmyadmin if that helps.

I see that there are 2 users to the db one is webmaster % and the other is root localhost. and I do know both pwds.

I am not sure what else to do.  I hope you can help.

Thanks

[mario]

The 404 is not found aka the files are not in place. Did you have a symlink in the file system or did you configure an alias in the apache config?

For PHPMyAdmin itself "denied: root (mysql-denied) from 134.122.19.42". Either You add another root user for 134.122.19.42 or you have to login as webmaster since the "%" is a wild card for any host.

[ozstar]

Thank you Mario.

I changed a few lines in the hosts and apache2 config files and the Wordpress Home page appeared, albeit a few images not showing.

I notice that I still get a 404 when I try to go to another page, in both admin and front sides.

So the search is on to fix this now 

[mario]

What is the access log of that vhost about the 404 errors?