Save Web Hosting Settings takes a long time

[LennyM]

Panel-Version 11.5.30 Update #38
BS Debian 7.4

Save Web Hosting Settings takes a long time. The Domains (Apache Server) are not reachable for 36 seconds.

 

[abdi]

What are the specs for your VPS? And are you hosting many domains with it?

 

[LennyM]

What are the specs for your VPS? And are you hosting many domains with it?

Processor: 4x Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
Kernel: 3.2.0-4-amd64
Memory: 24162 MB

I currently hosting 3 Domains.

 

[LennyM]

Does anyone have an idea? I desperately need a solution.

 

[IgorG]

Do you have any related error messages in /var/log/sw-cp-server/error_log ?

 

[LennyM]

Do you have any related error messages in /var/log/sw-cp-server/error_log ?

No, no related error messages.

My sw-cp-server Listen on Port 443. Can this be the problem?

Note: The control panel must be available at the port 443.

 

[IgorG]

Check at least that you have switched port of control panel correctly - http://kb.parallels.com/en/138

 

[LennyM]

Check at least that you have switched port of control panel correctly - http://kb.parallels.com/en/138

I have changed the port as described in the instructions.

 

[LennyM]

the problem still exists

 

[yabado]

I am seeing the same thing. Creating sites and saving settings takes a very long time. Also, logging into ftp takes quite a bit longer as well.
I only have a couple test sites right now.

Was there ever any resolution to this thread?

 

[IgorG]

Is this problem actual for Plesk 12 as well?

 

[yabado]

Yes I am using 12.0.8 . I am just testing at this point, but the slowness has me concerned.

I also just restarted the server from within the panel and now all I get is a 502 nginx error page?

UPDATE: Rebooting server instance brought everything back.

 

[IgorG]

Yes I am using 12.0.8 . I am just testing at this point, but the slowness has me concerned.

I also just restarted the server from within the panel and now all I get is a 502 nginx error page?

There are a lot of KB articles regarding "502 nginx error". Just try to use KB search. A lot of different reasons of this error and it is very difficult suggest something without deep investigation directly on your server. Support is much more effective with resolving these complex issues. Much more than forum discussions.