Search results

http://status.x10hosting.com

(don't worry, I'm *pretty* sure it's not your fault)

Annnnndd I found the user that's been causing outbound DoS attacks from absolut to placeholder...

The server is nowhere near full. root@absolut [~]# df -ah Filesystem Size Used Avail Use% Mounted on /dev/sda3 218G 174G 45G 80% / proc 0 0 0 - /proc sysfs 0 0 0 - /sys devpts 0 0 0 - /dev/pts tmpfs...

Oh no, definitely needs updating. The author of that particular post is busy. VERY busy. Just had another kid. :P

This tutorial is a bit old and could probably use some updating, but it definitely is a good starting point. The community over there is also very helpful (though most of the people here can help, too) http://webdevrefinery.com/forums/topic/3280-how-to-make-a-user-account-system/

I don't know what to tell you. Your website works fine.

You never added the database user to your database. I added it for you.

Your website is working fine. androidworld.x10.mx redirects to www.androidworld.x10.mx though, that's completely unnecessary.. almost no one uses the "www" anymore.

No. It won't interfere.

Can I have the link to your website? The URL in your account doesn't point to any website right now (It appears that the nameservers are still set to GoDaddy's)

The turnaround for them is usually within 24 hours. Our Abuse Compliance Officer will look at it when he gets to it. Make sure you check out our TOS -- http://x10hosting.com/terms

You will probably have to change the settings on your forum to reflect the new domain name.

Awesome. Glad you're able to get back in.

You cannot assign port numbers in a DNS entry.

Read: http://business.ftc.gov/documents/bus61-can-spam-act-compliance-guide-business

No -- They should have reported the phishing to the host. Namely, they should have emailed abuse@x10hosting.com. But they didn't. I had to manually call them as a representative of x10 and get the info from them.

I've been in contact with comcast and have taken actions to get them to remove the block. This should be resolved within a couple of hours.

I'm calling Comcast again now.

Sorry, I meant to get back to you about this. The firewall is not to blame for this issue. It must be an issue with your script.