Ashoat

NetFreak: please state your issue succinctly. jje: I'm seeing a blank page.

Okay, done.

Glad everything worked out!

What exactly do you need me to chown? Anyways, all of the listed problems should be corrected now.

There shouldn't be a significant delay. This might be due to server load issues.

Okay, should be working now.

Okay, I've changed your IP address. Your site should become visible to you within 24 hours.

Okay, I've increased Johnny's memory_limit to 128 MiB.

I've added that line on both Stevie and Johnny and I don't think the problem has been resolved...

Okay guys, try now. Let me know if there are any other pages returning the hacked HTML.

Should be up now. The hackers seem to have replaced random files with their HTML page, so I'm not sure but that might have happened to you guys too. If it did... sorry, but we have no backups.

I haven't purchased anything from the upstream provider yet, so don't worry about it.

Hmm... and you're sure the files have good permissions and are in the cgi-bin folder?

Yeah, I was taking a look. I'm currently running a fsck on /home... hopefully when that finishes everything will be alright, as df and du definitely reported different filesystem usage on /home (du only reported ~46 GiB, which is reasonable).

Okay, done.

Closing due to inactivity.

Okay, it's set up. Can you send $12 to admin@heliohost.org via PayPal?

jje: Good catch! Romero: try again now.

Before the change in my last post, the HelioHost homepage wasn't doing it right.

Okay, should be fixed. Let me know if the problem continues.

Because this doesn't have to do with them? Besides, they probably won't have any solutions we haven't thought of.

Glad it worked out

I'm not sure what is the "cache problem" in here, but I use something like this: header('Expires: Mon, 01 Jan 2001 00:00:00 GMT'); // date in the past header('Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0, max-age=0'); header('Pragma: no-cache'); Of course if in such cases like above mentioned redirection takes a place - such headers have to be sent with the redirection "page", not with the landing page where visitors are redirected to. If redirection is done with .htaccess or with some other method (not with PHP script) - I don't know how to attach these headers, unfortunatelly. If you're using Chrome, take a look at view-source:http://65.19.143.3/. We're using the same headers, but as HTML meta http-equivs.

This is weird, considering that we had brute force protection disabled.

I thought I updated the time recently. Looks like Stevie's hardware clock is off... Should be good now.