News:

Go to HostNed.com Home
Welcome.  This is a place to get user-to-user support, learn more, and share ideas.  If you can't find your answers here, feel free to ask by creating a new topic or visit the support ticket system at https://my.hostned.com :)  Have fun here!

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Dynaweb

#211
It seems that we often get the comment from users "My site has been hacked.  My web forum index page was replaced (or erased).  Please make it so that hackers cannot get in."

The kind of problem you are experiencing often happens when you have PHP or ASP scripts on your web space that is insecure.  The server must do what the script calls for and if the script itself is insecure, then it could seriously jeopardize your data.  It is not uncommon for popular web scripts like forums, blogs, CMS scripts and others to contain vulnerabilities that allow malicious users to access or edit or delete files.  If you are using a common web script and believe it is insecure, contact the author of the script for information on applying security patches and/or upgrading to the latest version of the script.

From my experience, the most insucure scripts are:

Subdreamer
PHP Nuke
PHPBB

Although almost any popular GPL web script can be vulnerable, even the most vulnerable can be made secure.  It takes a lot of attention and research.  Again, the most important thing you can do is go to the support site for the script you are using and apply all security patches.  Also find if the script designer recommends if Register_Globals be set to OFF.  If so, disable register globlas using .htaccess file.
#212
In your CSS, try adding "margin: 0 auto" to make the alignation (is that even a word?) in Firefox and other browsers.
#213
Linux Hosting / Re: Okay, Now what'd I do?
June 06, 2007, 09:39:57 PM
No, nameserver settings would be unaffected by deletingthe folder.  For more info on nameserver settings, see here http://www.hostned.com/members/faqs_domain_names_dns.html#How_do_I_set_my_nameservers_for_my_domain_name
#214
Linux Hosting / Re: Okay, Now what'd I do?
June 06, 2007, 05:23:57 PM
Well, look here http://whois.domaintools.com/northtexascreationresources.org

See at the bottom, you have your nameservers set to

Name Server:NS3.NO-IP.COM
Name Server:NS2.NO-IP.COM
Name Server:NS1.NO-IP.COM
Name Server:NS4.NO-IP.COM
Name Server:NS5.NO-IP.COM

Why is that?  That would be the reason why things are screwed up in this way.  Why not just use the nameservers HostNed provides:

YIN.SSL1.US
YANG.SSL1.US
#215
Looks like the way that it installed was a bit strange.  Looks like it may work from non-www.  I mean from http://northtexascreationresources.org/forum/index.php but not from http://www.northtexascreationresources.org/forum/index.php
#216
Linux Hosting / Re: Back to the e-mail problem
June 05, 2007, 11:29:53 AM
Go ahead and open a new thread for the forum thing.  Make sure you post there the URL for the forum since when I go to the site I do not see a link to the forum from there.
#217
Linux Hosting / Re: Back to the e-mail problem
June 04, 2007, 10:35:57 PM
I hope that works for you.  Seems to me like that would be the ringer.  Good luck.
#218
Linux Hosting / Re: Back to the e-mail problem
May 21, 2007, 10:23:03 AM
Quote from: Dragonfighter on May 20, 2007, 08:25:49 PM
Okay, I think I'm beginning to grasp the situation.  One question, is there anyway to move the domain registration over to hostned?


Sure, just go into the MyHostNed area [ https://my.hostned.com ] and open a ticket for sales there for it.
#219
Linux Hosting / Re: Back to the e-mail problem
May 04, 2007, 09:57:17 AM
OK, this should help you.  Go to this address
http://www.dnsreport.com/tools/dnsreport.ch?domain=northtexascreationresources.org
There you can see that your domain nameservers are set to no-ip.com
(Be aware that the nameservers are set at your domain name registrar and take a couple days to become effective)
It is possible that you are confusing the nameservers with the DNS zone which is on the HostNed server and accessible through your control panel (Plesk).
Think of them both as roadsigns that tell internet traffic where to go.  Nameservers are an earlier stop before the DNS zone.  In your case, the internet traffic is going to to the no-ip.com direction first and is not being directed back to HostNed.  If you replace the no-ip.com nameservers with HostNed's nameservers:
yin.ssl1.us
yang.ssl1.us
then internet traffic will be directed to here and eventually find your DNS zone and all will be linked up and good to go.
#220
Linux Hosting / Re: Back to the e-mail problem
May 03, 2007, 08:57:12 PM
Quote from: Dragonfighter on April 20, 2007, 01:39:19 PM
Okay, here is where I need some help then.  The space and domain are being hosted by Hostned, what configuration can I affect to change this.  How did the IP's get pointed that direction in the first place?  I'm really lost here.

Sorry, I didnt notice your last reply here right away.  Are your nameservers set to the ones HostNed provided?  That would be the most common reason.
#221
Linux Hosting / Re: Cron Jobs
May 03, 2007, 08:55:14 PM
Hi,

This can be done through cron.

*** Updated 4/23/25 for new compatibility and details ***
Here's How to Add the Cron Job You Described


To delete files older than 3 days in a specific directory (e.g.
/home/username/tmpfiles), you can use the
find command in your cron job like this:

find /home/username/tmpfiles -type f -mtime +3 -delete
Explanation:
  • find: The command to search files.
  • /home/username/tmpfiles: Replace this with the actual directory path.
  • -type f: Only looks for files (not directories).
  • -mtime +3: Only selects files modified more than 3 days ago.
  • -delete: Deletes them.
IMPORTANT: Make absolutely sure you've tested this in a safe way (e.g. remove
-delete and add
-print to test which files would be deleted).

🕑 How to Set This to Run Daily
In the cPanel Cron Jobs section, under "Add New Cron Job", choose:
  • Common Settings:
    Once Per Day
  • Command:
    find /home/username/tmpfiles -type f -mtime +3 -delete
(Again, replace
/home/username/tmpfiles with the real path.)

Permissions

As for file ownership, our new cPanel servers should be configured to allow access without any problem. If you need help, feel free to open a support ticket.
#222
General Hosting / Re: Complete Noob - Email Question
April 20, 2007, 12:09:48 PM
Check the nameservers for the domain name.  Make sure they are set correctly.  Also make sure the DNS zone is set up correctly.  The DNS zone can be found in your server control panel.
#223
Linux Hosting / Re: I Must Realllly Be Ignorant
April 20, 2007, 12:07:47 PM
Sorry, but what exactly is your question?
#224
Linux Hosting / Re: Back to the e-mail problem
April 20, 2007, 12:06:43 PM
Quote from: Dynaweb on April 05, 2007, 05:20:34 PM
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.
#225
Linux Hosting / Re: I Must Realllly Be Ignorant
April 05, 2007, 05:33:54 PM
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.