Messages

Your domain name is not even linked to HostNed.  I did a trace and got the following:

===
Name: www.hopto.org
IP Address: 204.16.252.98
Location: Las Vegas (36.172N, 115.122W)
Network: VITAL-NOIP
===

Additionally, nothing in the information you provided in your post indicates that the domain name is at all linked to HostNed.  That is most definitely the problem.

Do a trace on the domain name northtexascreationresources.org.  It traces to Nevada.  None of HostNeds servers are in nevada.

Do a trace on mail.northtexascreationresources.org and it traces to 75.36.22.134 in texas.  HostNed does have servers in TX, but not that IP 75.36.22.134.

This means that your web http server and mail server are not being served by hostned due to the way you have things configured.

No more 406 error message so thats good.  You did the .htaccess thing right then.  As for your scripts, we will have to look at each of those individually.  Check your scripts path references again to make sure they are correct.  Additionally, in your Plesk control panel, go to LOG MANAGER -> ERROR_LOG and see what is recorded in there.

Your domain name is not even linked to HostNed.  I did a trace and got the following:

===
Name: www.hopto.org
IP Address: 204.16.252.98
Location: Las Vegas (36.172N, 115.122W)
Network: VITAL-NOIP
===

Additionally, nothing in the information you provided in your post indicates that the domain name is at all linked to HostNed.  That is most definitely the problem.

Hi,

We can help you with this stuff.  I seems like you have 2 different issues here.  The best way to get help here is to make one thread for each individual issue.  Since you included the specific error information here in this thread for your "Not Acceptable" issue, we can follow through with that here.  For help setting up your email, feel free to open a new thread for that.

"Not Acceptable" errors are an Apache error code 406.  From my experience, 406 errors most likely are due to tripping a mod_security rule.  HostNed's servers run mod_security for your protection and I am very glad they do.  The challenge here is to determine which rule your script is breaking.  That would be very hard, but is not impossible.  We can travel that path if willing later.

So can the mod_security be turned off?  Yes, it can.  The best way to do that is through an .htaccess override.  Under your /httpdocs (or root web directory) create a file named .htaccess (if one is already there you can edit it) and include the following lines:

## Disable mod_security
SecFilterEngine Off
SecFilterScanPOST Off

Then save the file and give 'er another go.

Very nice CSS stuff there.  I have no idea about the space prob though.  Maybe include some of the specific code samples here and we can take a look.

Thanks for the comments.  I guess the marquees are a little distracting to a repeat visitor.  I suppose DHTML or Ajax to bring additional information to the forefront might be more appropriate.

Is there any problem with loading your web page in addition to this problem?  If so, such an across-the-board issue would most likely stem from a domain name resolution problem (the domain name is not resolving).  I would check to ensure that the nameserver settings assigned to your domain name match the ones HostNed provided for you in your Welcome email link (I believe it is http://www.hostned.com/setup/ ).  Look into that and let me know.  If that is not he problem, let me know your domain name so I can do some lookups on it and sluth the source of the trouble for you.

[CAFEPRESS REVIEW:]

CAFEPRESS REVIEW:

I have to say, the more I use CafePress the more I like them.  Their products are top-notch. The prining quality is unbeatable.  In my opinion, there is no alternative to CafePress, none of the others come close to the professional solution they have to offer. 

It is really easy to set up a shop for free, and their premium shops are just fabulous... you can even add your own custom HTML!.  It's all just too easy.  CafePress is definitely worth checking out.

I like the site.  Design is simple and navigation is clear.  Loads well in IE and Firefox.  Font is a bit too small on the home page.  I really like the forum skin, but I would like to see the site's color scheme worked in to the forum a little better.

[Disllow Directory Browsing]

Most servers are configured so that directory browsing is not allowed.  This means that if a certain web directory does not contain an index (or default) file, then an error message will be displayed in the web browser.

If Directory Browsing is enabled, then the contents of the directory will be shown in the browser and you can click freely on files and folders therein.

Disllow Directory Browsing
If you want to Disallow Directory Browsing on a server that allows it, create an .htaccess file in the web root directory and add the following line:

Code Select Expand

IndexIgnore */*

Allow Directory Browsing
If you want to Allow Directory Browsing on a server that dies nto allow it by default, create an .htaccess file in the web root directory and add the following line:

Code Select Expand

Options +Indexes

Remember that .htaccess files do not work on Windows Servers, so you will have to have your web host set the configuration for you.  Have fun with your server and htaccess!

[As I see it, SPAM comes through in three different ways:]

As I am sure you already know, keeping your email address hidden from Spammers is very important.  Spiders and bots scour the web and find as many email addresses as possible and add them to databases.  Since these addresses are present on the internet, they typically prove much more successful than dictionary attacks.

Having said this, I would like this thread to be an ongoing, cooperative effort to form an article on the subject.

Let's go:

As I see it, SPAM comes through in three different ways:

1) Spiders scour the web and find emails that are in plain text and database them.

2) Bots get through web forms and send SPAM instead of the honest visitor feedback or occasional goofball as expected.

3) Programs send out dictionary attacks on your domain.

Let's go over these individually to see what can be done to protect yourself and your sanity.

1) Spiders scour the web and find emails that are in plain text and database them.

What you have to do here is go over your web site and make sure your email address is not presented in plain text.  For example, it may exist in this way

Code Select Expand

your@yourdomain.com
or like this

Code Select Expand

<a href="mailto:your@yourdomain.com">
or in some similar way.  AVOID THIS.  SPAMMERS and their spiders adore this as it leaves your email address wide open for collection into their precious database.

What can be done to avoid exposing your email address in plain text?

a) Use an image of your email address and do not link to the email address in the mailto method.
b) Use a quick and easy "(at)" in place of "@" and "(dot)" in place of "." like this:  me(at)mydomain(dot)com.
c) Use javascript to display the email address (my favorite way).  Here is a sample of the code to use:

Code Select Expand


<script language="JavaScript">
<!-- //Go choke on a chicken wing you spammer bastards!
var name = "me";
var domain = "mydomain.com";
document.write('<a href=\"mailto:' + name + '@' + domain + '\">');
document.write(name + '@' + domain + '</a>');
// --></script>
of course replace me & mydomain.com with your actual information.

2) Bots get through web forms and send SPAM instead of the honest visitor feedback or occasional goofball as expected.

To battle this you need to use the correct scripting in your web forms to combat SPAM.  Older forms do not take this into account.  One such script I recommend is Dynaweb's SFEPS located at http://www.dynawebdesigns.com/scripts.htm
It uses PHP which any HostNed account supports.

3) Programs send out dictionary attacks on your domain.

There are a few things you can do to combat dictioaryattacks.

a) Do not use an email catchall.
b) Name your email account names something that is hard to guess.  For example, instead of using the name contact(at)mydomain(dot)com use this instead, c.o.n.t.a.c.t8745(at)mydomain(dot)com

Mailenable released a hotfix and it has been applied to this server.  That should resolve the issue.

In regards to email performance on server WIN2 late January. 

We can confirm that from mid to late January we experienced periods of mail failures.  This occured due to one of the DNSBL blacklist databases we use to filter incoming email to our server having troubles.  Although their failure appears to be due to a problem in their service upgrade and not an issue of negligence, mail problems are not acceptable for HostNed customers.  This type of server-wide filtering is industry standard and the failure was experienced by thousands of servers worldwide.  Needless to say we are very disappointed in the failures of the 3rd party service that we have come to rely upon.  Due to the reliability issue, we have unsubscribed from that database service; however we are still maintaining other databases to protect the server from being flooding by incoming SPAM email.  We regret that we have experienced this and I assure you we have taken proper measures to prevent such a failure in the future.

Sincerely,
HostNed Management

JANUARY SPECIAL: X3 Web Space and $1 Setup, Custom Linux and Windows Plans

How to get the deal:
Purchase a new Custom Web Hosting (Shared Series) now through the end of January.

Great change to get more bang for you buck.  Go to http://www.hostned.com

Hi,

Welcome to the forums.  Check to make sure there is no restriction from an .htaccess file.  Otherwise, make sure the html page or css is not referencing any files within a "protected directory".