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.


Messages - shobhit

Pages: [1]
1
CentOS-WebPanel Bugs / Re: User Panel stopped logging in after update
« on: September 10, 2019, 04:52:51 AM »
Now in the update, there is an issue with FTP account creation. Please go through this thread:
http://forum.centos-webpanel.com/centos-webpanel-bugs/ftp-creation-not-working-after-update

2
CentOS-WebPanel Bugs / FTP Creation not working after update
« on: September 10, 2019, 04:51:27 AM »
In Version 0.9.8.885 User logging in issue got rectified but a new issue has arised. Now user cannot create a FTP account. The Spinner button : Processing goes on infinitely without any results.
Any solutions please?

3
CentOS-WebPanel Bugs / Re: User Panel stopped logging in after update
« on: September 10, 2019, 03:50:41 AM »
Hi,
try to run cwp update two times:

Code: [Select]
sh /scripts/update_cwp
it worked for me

4
CentOS-WebPanel Bugs / Re: User Panel stopped logging in after update
« on: September 09, 2019, 04:22:02 PM »
I think all of us should create support tickets. The support team doesnt look too encouraged regarding this issue. Seems like they havent received enough complaints regarding this so this is not a known issue for them.

5
CentOS-WebPanel Bugs / Re: User Panel stopped logging in after update
« on: September 09, 2019, 12:49:07 PM »
I witnessed the same issue two updates before too. Support team resolved it by throwing another update. Its strange and sad to see that the same error has come up again and they have taken so long to rectify it. My users are asking me again and again to provide them the login to their account and I am helpless.

6
SSL / Re: SSL certificate blocked by antivirus for Apache + NGINX + Varnish
« on: September 09, 2019, 10:01:02 AM »
Yeah,
I started using hostname:2083 instead of userdomainname:2083 and things worked

7
CentOS-WebPanel Bugs / User Panel stopped logging in after update
« on: September 09, 2019, 09:59:11 AM »
Thi si sthe second time I am facing this issue after updating the CWP. Again, when user tries to login, the login button gets changed to Please Wait... for infinite time.
I tried to inspect and found the response which says Please donot use special characters. I removed the special character from password and tried logging in again and this time there was no response in the network tab of inspect element.

Then I jumped to the COnsole Tab of Inspect element window to find out whats happening and I got the following error:

VM523:1 Uncaught SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at Object.complete ((index):207)
    at i (jquery-3.1.1.min.js:2)
    at Object.fireWith (jquery-3.1.1.min.js:2)
    at A (jquery-3.1.1.min.js:4)
    at XMLHttpRequest.<anonymous> (jquery-3.1.1.min.js:4)

The logging in issue is repeated again and again after every update. How to solve this permanently and why doesnt support team test the things deeply before throwing an update?

8
Mod_Security / Re: ModSecurity: Status engine is currently disabled
« on: August 26, 2019, 02:30:11 PM »
Hi, I request you and everyone out here to plesae post the path of configuration file name whenever you suggest anything to be added to a configuration file. It is good that you helped the guy who asked the question, but a detailed answer will help others too. I tried editing the Main Configuraiton file of mod security and got Apache crashed twice. I had to re update mod security to get the things working.

9
SSL / SSL certificate blocked by antivirus for Apache + NGINX + Varnish
« on: August 22, 2019, 11:01:07 AM »
I am using CWPPRO with Apache + NGinx + Varnish installation. Earlier I used only Apache installation. With Apache only, I was able to loginto the Admin GUI and User Dashboard by managing SSL Exceptions when it was showed in the browser. I just had to click "I Understand the Risk and want to visit  URL" and login windows opened up.

Yesterday, I updated the Server to Apache + NGinx + Varnish and since then I am not able to cross the "Connection not protected" error message since the is no option available to pass it. I am using Kaspersky INternet Security on my machine. If I exit this antivirus on my machine, then I get the Manage Exceptions option in browser and I can reach login window. But my client is not convinced with this. He is a less technical guy and doesnot want to close the antivirus and doesnt belive that our server is secure.

I even deleted the existing SSL and reinstalled on his domain but the issue still persists. Kindly suggest some solution, its urgent.

Message I get in Browser:


Connection not protected
The security of your connection is reduced. Criminals can attempt to steal your data from the website. You are advised to leave this website.

URL:

myservername

Reason:

Self-signed certificate View certificate

10
How to / Swap not visible in the dashboard front end
« on: August 17, 2019, 12:56:15 PM »
Hi, I have followed your steps and created a 2 GB SWAP FILE. But when I open the CWP dashboard, I dont see swap activated. However if I visit Disk Quota in Server settings, in the "Your disk status from the file /etc/fstab" section, it shows the swap file present but in partition scheme, it doesnt.
Even when I run df -h in terminal, I dont see the swap activated.
If I try to run swapon /swapfile it says
Code: [Select]
swapon: /swapfile: swapon failed: Device or resource busyIf I execute free -m it shows Mem and Swap but the swap is 100% free

If I execute swapon -s it shows the /swapfile entry with 0 as a value in Used field and -2 in the priority field

How to know swap is working and how to show it in the dashboard also?

11
CentOS 7 Problems / Re: High MySQL Cpu Usage
« on: August 17, 2019, 11:27:40 AM »
Hi, are you using a single website or multiple websites?
You should look for two perspectives: MYSQL configurations and the codes being executed.
Try to figure out the proceses of those users who are active when your CPU is eaten up heavily. They might be trying too many queries and may not be closing the connections well in time.
Also, on your part, you can impose some limitations like number of allowed connections to MYSQL, buffer size of MYSQL Enginer like innoDB, etc. Imposing some limitations might help you out.
I hope this will help.

Pages: [1]