Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Updates / Re: Did 0.9.8.1239 remove extra DB users?
« on: July 03, 2026, 12:09:26 AM »
So, what should we do now regarding `temp_hacker_check`?
I have temporarily added an `exit` at the beginning of the script to prevent it from running. Should I also remove its write/execute permissions?
Honestly, I do not feel comfortable having this script running on my servers. Everything was working fine before, and what I need most is stability. I can take care of security on my side.
In some services, I do have MySQL users with host `%`. Is that really considered so abnormal or dangerous that they should be removed without prior notice or confirmation?
In my opinion, updates like this should not be pushed to the Stable branch, especially if Stable is supposed to mean “at least two weeks tested.”
I would like to know what you plan to do with this script, so I can prepare accordingly and also have an official recommendation on how to proceed. For the past two days, I have been waking up to complaints from clients because they are getting errors when trying to connect to their databases.
I hope that, for now, adding an `exit` at the beginning of the script is enough to prevent further issues, but I do not think this is a proper long-term solution.
I really hope you can review whether something went wrong with this update and adjust it properly. From my side, I want to reiterate that I would prefer to be able to disable this script completely, as I do not need it.
Thank you!
I have temporarily added an `exit` at the beginning of the script to prevent it from running. Should I also remove its write/execute permissions?
Honestly, I do not feel comfortable having this script running on my servers. Everything was working fine before, and what I need most is stability. I can take care of security on my side.
In some services, I do have MySQL users with host `%`. Is that really considered so abnormal or dangerous that they should be removed without prior notice or confirmation?
In my opinion, updates like this should not be pushed to the Stable branch, especially if Stable is supposed to mean “at least two weeks tested.”
I would like to know what you plan to do with this script, so I can prepare accordingly and also have an official recommendation on how to proceed. For the past two days, I have been waking up to complaints from clients because they are getting errors when trying to connect to their databases.
I hope that, for now, adding an `exit` at the beginning of the script is enough to prevent further issues, but I do not think this is a proper long-term solution.
I really hope you can review whether something went wrong with this update and adjust it properly. From my side, I want to reiterate that I would prefer to be able to disable this script completely, as I do not need it.
Thank you!
2
Updates / Re: Did 0.9.8.1239 remove extra DB users?
« on: July 02, 2026, 12:30:13 PM »
Hi,
This update has caused serious problems on my servers. For the last two days, MySQL users have been deleted repeatedly.
As a temporary workaround, I added an `exit` at the beginning of the `temp_hacker_check` script to prevent it from running again, because it was causing damage to my configuration.
Another problem is that the cleanup log is extremely basic. It only shows when the script starts and finishes, but it does not clearly log what users were deleted, what changes were applied, or why those actions were taken. This makes it very difficult to audit the damage or understand exactly what happened.
In my opinion, this script is not at the level of quality and safety expected from CWP. A security cleanup script should not silently delete MySQL users or modify server access without clear logging, confirmation, backups, or at least a safer detection method.
Please review this update and the `temp_hacker_check` script urgently, because it can break production servers and remove legitimate database users.
Thank you.
This update has caused serious problems on my servers. For the last two days, MySQL users have been deleted repeatedly.
As a temporary workaround, I added an `exit` at the beginning of the `temp_hacker_check` script to prevent it from running again, because it was causing damage to my configuration.
Another problem is that the cleanup log is extremely basic. It only shows when the script starts and finishes, but it does not clearly log what users were deleted, what changes were applied, or why those actions were taken. This makes it very difficult to audit the damage or understand exactly what happened.
In my opinion, this script is not at the level of quality and safety expected from CWP. A security cleanup script should not silently delete MySQL users or modify server access without clear logging, confirmation, backups, or at least a safer detection method.
Please review this update and the `temp_hacker_check` script urgently, because it can break production servers and remove legitimate database users.
Thank you.
3
CentOS-WebPanel Bugs / shoutcast manager autodj doesnt work
« on: April 12, 2022, 06:30:05 PM »
Hello everyone!
I always read the forum and this time I have come to ask for your help.
I'm testing Icecast + Autodj. Streaming works fine but autodj doesn't work. I was able to notice the following error in the following command
systemctl status liquidsoap@17000
[My_Station:3] Connecting mount for source@localhost...
[My_Station:2] Connection failed: could not connect to host: Connection refused in connect()
[My_Station:3] Will try again in 3.00 sec.
(repeats every 3 seconds)
Does anyone know what could be wrong?
Thanks in advance
EDIT: this error happens with icecast. I am now testing with shoutcast and it works fine. The fault is with ICECAST
I always read the forum and this time I have come to ask for your help.
I'm testing Icecast + Autodj. Streaming works fine but autodj doesn't work. I was able to notice the following error in the following command
systemctl status liquidsoap@17000
[My_Station:3] Connecting mount for source@localhost...
[My_Station:2] Connection failed: could not connect to host: Connection refused in connect()
[My_Station:3] Will try again in 3.00 sec.
(repeats every 3 seconds)
Does anyone know what could be wrong?
Thanks in advance
EDIT: this error happens with icecast. I am now testing with shoutcast and it works fine. The fault is with ICECAST
Pages: [1]
