Search results

Hi-- This should be resolved.

This is not possible on Free Hosting for a number of reasons. Secondly, Essellar is an x10Hosting representative.

Your account is currently in violation of our Terms of Service by hosting Copyrighted MP3s on it. Please remove them, or we will be forced to issue a suspension.

Hi-- What browser are you using? The link works fine in every browser I've tested.

Add the following to the htaccess in the folder you wish to disable caching in. Header set Cache-Control "max-age=0, private, no-cache, no-store, must-revalidate"

Caching shouldn't affect new files.... i'll look into this. In the meantime, put this in the htaccess for the folder you don't want cached: Header set Cache-Control "max-age=0, private, no-cache, no-store, must-revalidate"

The article you linked to is the change I made this morning. ;) ...But after about a minute of being dumb... I just realized I forgot to RESTART the FTP service... Try now! :p

It's loading fine on my end.

Your website appears to be up for me.

So--it's doing something different now that it was before?

The superglobal is actually correct on xo2

Can you please try using Active FTPS? Also, are you connecting with Implicit or Explicit SSL?

This is a problem with your "sexybookmarks" plugin. It is sleeping for 10000 seconds, which is causing the backend fetch to fail since there is no response. I've renamed the folder. You'll want to probably update it.

Hi, This should be okay now. Please let me know if it's working (Use an @leafypiggy)

Resolved.

Hello x10! Yesterday we launched a completely new Status page at http://status.x10hosting.com/. The theme and functionality for this theme was a work of love by @Dead-i , and I'd like to take a moment for everyone to appreciate the hard work he puts into making x10Hosting what it is today. He's...

Skyy... There's another one I can't remember right now.

Why not move the wordpress install into the root of the directory?

Hi, Crond had stopped on your server. It should be resolved now.

Yes. We're aware of the issue and are working to find the root cause of the issue and implement a change for it.