Recent posts

#91

Support Requests / Re: PHP 5.2

Last post by admin - September 19, 2014, 01:48:19 PM

For those that must use PHP 5.2, we can migrate you over to the NYC cPanel server.
That server runs each user in an isolated environment, so the risk of using the older version would only be with your sites.

We will be removing 5.2 and 5.3 from Plesk servers very soon.  The NYC server will continue to offer older versions due to the way it is setup.

#92

Support Requests / Re: New cPanel Server

Last post by admin - September 19, 2014, 01:15:29 PM

I applied for migration via help desk, but i cannot access the ticket anymore because I tried to upgrade my help desk account to a full account. As a result I am as of this post am still waiting for the validation email which until i receive and click on the link won't let me log in. The helpdesk username is the same as my panel username. Any assistance would be greatly appreciated.

Sincerely,

Aleeious

I have forced your Helpdesk account as validated.

Sorry I'm still getting the error:

Sorry, you must validate your account by clicking the link you received in our email to you. If you did not receive and email, click here.

Please go back and try again. If the problem persists, please contact an administrator.

Any assistance would be greatly appreciated.

Sincerely,

Aleeious

If you still can't access the helpdesk, please email plesk at lvcs dot net, that would be much faster then replying to this thread.

There are no pending accounts to be verified as per the helpdesk, so you may just have to continue creating new tickets under guest or we can remove the user and let you try it again.

#93

Support Requests / Re: New cPanel Server

Last post by Scorpion Illuminati - September 19, 2014, 03:42:44 AM

I applied for migration via help desk, but i cannot access the ticket anymore because I tried to upgrade my help desk account to a full account. As a result I am as of this post am still waiting for the validation email which until i receive and click on the link won't let me log in. The helpdesk username is the same as my panel username. Any assistance would be greatly appreciated.

Sincerely,

Aleeious

I have forced your Helpdesk account as validated.

Sorry I'm still getting the error:

Sorry, you must validate your account by clicking the link you received in our email to you. If you did not receive and email, click here.

Please go back and try again. If the problem persists, please contact an administrator.

Any assistance would be greatly appreciated.

Sincerely,

Aleeious

#94

Support Requests / Re: New cPanel Server

Last post by admin - September 19, 2014, 03:19:40 AM

I applied for migration via help desk, but i cannot access the ticket anymore because I tried to upgrade my help desk account to a full account. As a result I am as of this post am still waiting for the validation email which until i receive and click on the link won't let me log in. The helpdesk username is the same as my panel username. Any assistance would be greatly appreciated.

Sincerely,

Aleeious

I have forced your Helpdesk account as validated.

#95

Support Requests / Re: New cPanel Server

Last post by Scorpion Illuminati - September 19, 2014, 03:15:45 AM

I applied for migration via help desk, but i cannot access the ticket anymore because I tried to upgrade my help desk account to a full account. As a result I am as of this post am still waiting for the validation email which until i receive and click on the link won't let me log in. The helpdesk username is the same as my panel username. Any assistance would be greatly appreciated.

Sincerely,

Aleeious

#96

Support Requests / New cPanel Server

Last post by admin - September 03, 2014, 02:06:22 AM

We are testing a new cPanel server at the NYC data center.

If anyone would like to be moved to this server, please let us know by sending a message via the Helpdesk.

This server is running CloudLinux so it allows various PHP versions to be selected, modules to be included/excluded, PHP settings changed, etc.

If you are on EAST, this server should provide more performance as it is SSD based.

#97

Support Requests / Re: PHP 5.2

Last post by admin - August 16, 2014, 04:27:55 AM

Reminder: PHP 5.2 and 5.3 are slated to be removed from this system once 5.6 goes to release.

PHP 5.3 is now officially EOL'd, so no more security updates are coming to it.

#98

Support Requests / Re: Not worth the aggravation

Last post by admin - August 13, 2014, 02:49:48 AM

...My app uses where clauses for user.username, username.password, matchindex.id, matchindex.challenger and matchindex.defender. You can see how everything works on my github page. Any assistance would be greatly appreciated....

As long as the fields you have listed are indexed along with any fields used in your JOIN statements, you will be fine.

#99

Support Requests / Re: Not worth the aggravation

Last post by Scorpion Illuminati - August 12, 2014, 03:14:22 AM

As long as your site isn't taking multiple seconds per page load, you are generally fine.  (We are not talking about time waiting on downloading files to the client computer, Nginx offloads that part from Apache very well, but time waiting on your pages to generate due to waiting for MySQL, waiting for a remote API, etc.)

For the most part, we try to keep the load low on the servers.  We let users exceed CPU-I/O time limits for a period of time in case they are working with their site or are getting a traffic spike.  When we get complaints on the performance of a specific server, if we find these high resource users and the reason they are using resources is Google is crawling their site (because their site takes 10 seconds to load on each pageview), we generally disable the user and attempt to help them index their tables or explain what processes are using too many resources.

If your site loads fast, you will likely never fall into this group.

By replying to this topic, we didn't want to send the message that we were thinking of discontinuing the service, because we are not.  We may need to consolidate it further in an effort to lose less money, but there is no reason the service will need to be discontinued in the near future.

I'm sorry but everytime i see:

I guess our only choice will be to shut this down.

I start to fear the worst.

You should create indexes for any column your are sorting or filtering by.  If you are not sorting by that column (i.e. using it in an ORDER BY clause) or filtering by that field (using it in a WHERE clause), this will not be necessary.  [This should also be done if joining tables using these fields.]

My app uses where clauses for user.username, username.password, matchindex.id, matchindex.challenger and matchindex.defender. You can see how everything works on my github page. Any assistance would be greatly appreciated.

Sincerely,

Aleeious

#100

Support Requests / Re: Not worth the aggravation

Last post by admin - August 11, 2014, 12:29:55 AM

As long as your site isn't taking multiple seconds per page load, you are generally fine.  (We are not talking about time waiting on downloading files to the client computer, Nginx offloads that part from Apache very well, but time waiting on your pages to generate due to waiting for MySQL, waiting for a remote API, etc.)

For the most part, we try to keep the load low on the servers.  We let users exceed CPU-I/O time limits for a period of time in case they are working with their site or are getting a traffic spike.  When we get complaints on the performance of a specific server, if we find these high resource users and the reason they are using resources is Google is crawling their site (because their site takes 10 seconds to load on each pageview), we generally disable the user and attempt to help them index their tables or explain what processes are using too many resources.

If your site loads fast, you will likely never fall into this group.

By replying to this topic, we didn't want to send the message that we were thinking of discontinuing the service, because we are not.  We may need to consolidate it further in an effort to lose less money, but there is no reason the service will need to be discontinued in the near future.