I reset the root/localhost password to phpMyAdmin with SQL commands
directly from a shell session, with these commands:
1. # systemctl stop mariadb
2. # mysqld_safe --skip-grant-tables --skip-networking &
3. # mysql -u root
4. > FLUSH PRIVILEGES;
5. > SET PASSWORD FOR 'root'@'localhost' =
It turns out the problem was NOT with the reset of the root password.
The problem lies with BlueOnyx/CentOS's handling of PHP versions.
The version of PHP installed when the server was set up was 5.4.
Resetting this version to 5.6 causes no problem.
However, resetting the "default version" of
I have the sudden problem that, while I can log into the Blueonyx control,
I cannot use the same login to get to the CentOS shell.
One other thing is that now the user "admin" is gone from Blueonyx and
cannot be used to log into the Linux shell.
Has anyone seen this before and does anyone have
In the "Whitelist" entry-field on the "Login Manager" page (using 5210r), I
cannot enter anything following the pre-filled value "127.0.0.1/32" without
the form immediately throwing up a red complaint that something needs to be
fixed—it doesn't say what needs to be done.
I can't find anything in
What is the best way to block an ip address from accessing the server and
any vsite on the server? Firewall?
I have the ip addresses from which attacks are being staged on vsites on my
server and I need to block them as widely as possible.
___
Blueonyx
Getting the list from systemctl this morning, these two entries look odd:
*run-r8231c29cfedb4aa6984d35c5d73c52ad.service* loaded failed failed
/usr/bin/systemctl start man-db-cache-update
*run-r8bd46e5235f941b9af4fa4d7edfc682c.service* loaded failed failed
/usr/bin/systemctl start
rson managing the list at
> blueonyx-ow...@mail.blueonyx.it
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Blueonyx digest..."
> Today's Topics:
>
> 1. [BlueOnyx:25681] login attempts after IP added to fire
As root, I added IP addresses that the firewall should reject immediately.
Getting status showed that they had been added to the reject list.
However, they are still showing up in BlueOnyx with attempts to login as
root.
For example, I used
firewall-cmd --permanent --add-rich-rule="rule
