Search results

Simply searching for 'http://example.com' and replacing it with your domain will do. Also, do create a page for where it would land if it were to fail or succeed.

*.whatever.tld is considered a sub-domain. If you want to use the way you're wanting to use then use a custom domain (*.tld), else you'll have to use the method @bdistler had mentioned which supports sub-domains.

If you have your own domain then there's a few things you can do: If you have a .uk domain, you're able to hide such information for free by visiting the registry's site If your domain isn't that, then you'll need to pay for domain privacy. Note that this does NOT protect you from the whois...

Your form is going to http://example.com which is, an example domain. Change the redirect path set in 'sendmixed.php' to your domain and the 'thankyou.html' page you may have stored under your account as something else.

You had exceeded your quota. Try deleting any files/folders you don't need around.

Have you checked your IP if it had been blacklisted using the sites linked by @bdistler in his reply?

It's likely to be the actual server storage that there's a lack of.

Your ISP can also has DNS caching. You can try using a different network with a different ISP. Or you could try using a mobile network.

Are you using a proxy or a VPN by any chance?

Delete any files/folders you don't need to be there. Doing that should drop you under the inode limit.

When you first registered, you agreed to this: If you do apply but haven't contacted them then that's what you should've done.

So you're getting a 403?

If you're trying to execute a PHP script then that's not how it's done. You're basically trying to execute it as if it's a shell script.

In addition to what @essellar said, you should have client and (if you're going to use PHP for the submission handling) server side validation for that. So, you could use the 'url' input type (so not 'text') or use JavaScript to pick it up before completing a submission. If you need server-side...

The post_max_size directive is basically the size of the content going through a POST request. As you had set your maximum upload size to 30M, you should use the same for post_max_size. I would probably also say 'higher' but you don't really want to be able to post over 30M(i)B of text, do you? :P

Oops. I didn't make that clear. For things such as name text boxes, it's of course important for those. What I was referring to previously was the text fields that would be used to submit content to places such as blogs which can have URL(s) in their posts from time-to-time. When the rule gets...

By default, it's 2M for the 'upload_max_filesize' directive. If the file you're uploading is larger than 2M (2MiB) then change the following directives: upload_max_filesize post_max_size Edit in the php.ini file with the appropriate sizes, save and then restart the web server (in your case...

This checks if it's able to reach the server. It does not check the HTTP response code.

This is part of the active rules set in mod_security2. This rule is supposed to prevent things like remote file execution (using external URLs) and a XSS method. It can be very useless in the type of situation which you had pointed out.

You could use PHP to help accomplish the task. This documentation should help out: http://php.net/manual/en/ziparchive.extractto.php