It looks like this is a web page, not a feed. I looked for a feed associated with this page, but couldn't find one. Please enter the address of your feed to validate.

Source: http://www.noorgate.info/external.php?type=RSS2

  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  2. <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  3. <head profile="http://gmpg.org/xfn/11">
  4.        <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  5.        <title>500 - INTERNAL SERVER ERROR</title>
  6.  
  7. <!-- Add Slide Outs -->
  8. <script src="http://code.jquery.com/jquery-3.3.1.min.js"></script>        
  9. <script src="/cgi-sys/js/simple-expand.min.js"></script>
  10.        
  11.        <style type="text/css">
  12.        body{padding:0;margin:0;font-family:helvetica;}
  13.        #container{margin:20px auto;width:868px;}
  14.        #container #top500{background-image:url('/cgi-sys/images/404top_w.jpg');background-repeat:no-repeat;width:868px;height:168px;}
  15.        #container #mid500{background-image:url('/cgi-sys/images/404mid.gif');background-repeat:repeat-y;width:868px;}
  16.        #container #mid500 #gatorbottom{position:relative;left:39px;float:left;}
  17.        #container #mid500 #xxx{float:left;padding:30px 347px 10px; margin: auto auto -10px auto}
  18.        #container #mid500 #content{float:left;text-align:center;width:868px;}
  19.        #container #mid500 #content #errorcode{font-size:30px;font-weight:800;}
  20.        #container #mid500 #content #banner{margin:20px 0 0 ;}
  21.        #container #mid500 #content #hostedby{font-weight:800;font-size:25px;font-style:italic;margin:20px 0 0;}
  22.        #container #mid500 #content #coupon{color:#AB0000;font-size:22px;font-style:italic;}
  23.        #container #mid500 #content #getstarted a{color:#AB0000;font-size:31px;font-style:italic;font-weight:800;}
  24.        #container #mid500 #content #getstarted {margin:0 0 35px;}
  25.        #container #bottom500{background-image:url('/cgi-sys/images/404bottom.gif');background-repeat:no-repeat;width:868px;height:14px;}
  26.        #container #mid500 #content #faq_container {margin: 5px auto 5px auto; padding: 10px 0 10px 0; clear:both;}
  27.        #container #mid500 #content #accordion{font-size: 90%; width: 650px; min-height: 100px; margin: 0 auto; text-align: center;}
  28.        #container #mid500 #content #accordion ul {text-align: left;}
  29.        #container #mid500 #content #accordion ol {text-align: left;}
  30.        #container #mid500 #content #accordion li {font-size: 90%;}
  31.        #container #mid500 #content #accordion p {font-size: 95%; text-align: left;}
  32.        #container #mid500 #content #accordion h3 {font-weight: bold;}
  33.  #container #mid500 #content #accordion h4 {font-weight: bold; font-style: italic; text-align: left;}
  34.  .content {display:none;}
  35.  .first {color: #ff6600;}
  36.  .second {color: #3b5998;}
  37.  .third {color: #198c19;}
  38.  .code { background-color: #e5e5e5; border: 2px solid #ede1d1; padding: 5px 5px 5px 5px; text-align: left;}
  39.  .shell{ border: 2px solid gray; background-color: black; color: white; text-align: left;}
  40.        </style>
  41.        
  42. </head>
  43. <body>
  44. <div id="container">
  45.        <div id="top500"></div>
  46.        <div id="mid500">
  47.  
  48.                <div id="xxx"><img src="/cgi-sys/images/e.png" alt="" /></div>
  49.        <div id="content">
  50.              <div id="errorcode">ERROR 500 - INTERNAL SERVER ERROR</div>
  51.              <div id="faq_container">
  52. <div id="accordion">
  53. <div id="why">
  54. <h3><a class="expander" href=#>Why am I seeing this page?</a></h3>
  55. <div class="content">
  56. <p>500 errors usually mean that the server has encountered an unexpected condition that prevented it from fulfilling the request made by the client. This is a general error class returned by a web server when it encounters a problem in which the server itself can not be more specific about the error condition in its response to the client.</p>
  57. <p>In many cases this is not an indication of an actual problem with the server itself but rather a problem with the information the server has been instructed to access or return as a result of the request. This error is often caused by an issue on your site which may require additional review by your web host.</p>
  58. <p>Please contact your web host for further assistance.</p>
  59. </div>
  60. </div>
  61. <div id="what_to_do">
  62. <h3><a class="expander" href=#>Is there anything that I can do?</a></h3>
  63. <div class="content">
  64. <p>There are a few common causes for this error code including problems with the individual script that may be executed upon request. Some of these are easier to spot and correct than others.</p>
  65. <h4><u>File and Directory Ownership</u></h4>
  66. <p>The server you are on runs applications in a very specific way in most cases. The server generally expects files and directories be owned by your specific user <strong>cPanel user</strong>. If you have made changes to the file ownership on your own through SSH please reset the Owner and Group appropriately.</p>
  67. <h4><u>File and Directory Permissions</u></h4>
  68. <p>The server you are on runs applications in a very specific way in most cases. The server generally expects files such as HTML, Images, and other media to have a permission mode of <strong>644</strong>. The server also expects the permission mode on directories to be set to <strong>755</strong> in most cases.</p>
  69. <p><strong>(See the Section on Understanding Filesystem Permissions.)</strong></p>
  70. <h4><u>Command Syntax Errors in .htaccess file</u></h4>
  71. <p>In the .htaccess file, you may have added lines that are conflicting with each other or that are not allowed.</p>
  72. <p>If you would like to check a specific rule in your .htaccess file you can comment that specific line in the .htaccess by adding # to the beginning of the line. You should always make a backup of this file before you start making changes.</p>
  73. <p>For example, if the .htaccess looks like</p>
  74. <div class="code">
  75. DirectoryIndex default.html<br />
  76. AddType application/x-httpd-php5 php
  77. </div>
  78. <p>Then try something like this</p>
  79. <div class="code">
  80. DirectoryIndex default.html<br />
  81. #AddType application/x-httpd-php5 php
  82. </div>
  83. <p><strong>Note:</strong> Due to the way in which the server environments are setup you may not use <strong>php_value</strong> arguments in a .htaccess file.</p>
  84. <h4><u>Exceeded Process Limits</u></h4>
  85. <p>It is possible that this error is caused by having too many processes in the server queue for your individual account. Every account on our server may only have 25 simultaneous processes active at any point in time whether they are related to your site or other processes owned by your user such as mail.</p>
  86. <div class="shell">
  87. ps faux
  88. </div>
  89. <p>Or type this to view a specific user's account (be sure to replace <em>username</em> with the actual username):</p>
  90. <div class="shell">
  91. ps faux |grep <i>username</i>
  92. </div>
  93. <p>Once you have the process ID ("pid"), type this to kill the specific process (be sure to replace <em>pid</em> with the actual process ID):</p>
  94. <div class="shell">
  95. kill <i>pid</i>
  96. </div>
  97. <p>Your web host will be able to advise you on how to avoid this error if it is caused by process limitations. Please contact your web host. Be sure to include the steps needed to see the 500 error on your site.</p>
  98. </div>
  99. </div>
  100. <div id="understand_perms">
  101. <h3><a class="expander" href=#>Understanding Filesystem Permissions</a></h3>
  102. <div class="content">
  103. <h4><u>Symbolic Representation</u></h4>
  104. <p>The <strong>first character</strong> indicates the file type and is not related to permissions. The remaining nine characters are in three sets, each representing a class of permissions as three characters. The <strong><span class="first">first set</span></strong> represents the user class. The <strong><span class="second">second set</span></strong> represents the group class. The <strong><span class="third">third set</span></strong> represents the others class.</p>
  105. <p>Each of the three characters represent the read, write, and execute permissions:</p>
  106. <ul>
  107. <li><strong>r</strong> if reading is permitted, <strong>-</strong> if it is not.</li>
  108. <li><strong>w</strong> if writing is permitted, <strong>-</strong> if it is not.</li>
  109. <li><strong>x</strong> if execution is permitted, <strong>-</strong> if it is not.</li>
  110. </ul>
  111. <p>The following are some examples of symbolic notation:</p>
  112. <ul>
  113. <li><strong>-<span class="first">rwx</span><span class="second">r-x</span><span class="third">r-x</span></strong> a regular file whose user class has full permissions and whose group and others classes have only the read and execute permissions.</li>
  114. <li><strong>c<span class="first">rw-</span><span class="second">rw-</span><span class="third">r--</span></strong> a character special file whose user and group classes have the read and write permissions and whose others class has only the read permission.</li>
  115. <li><strong>d<span class="first">r-x</span><span class="second">---</span><span class="third">---</span></strong> a directory whose user class has read and execute permissions and whose group and others classes have no permissions.</li>
  116. </ul>
  117. <h4><u>Numeric Representation</u></h4>
  118. <p>Another method for representing permissions is an octal (base-8) notation as shown. This notation consists of at least three digits. Each of the three rightmost digits represents a different component of the permissions: <strong><span class="first">user</span></strong>, <strong><span class="second">group</span></strong>, and <strong><span class="third">others</span></strong>.</p>
  119. <p>Each of these digits is the sum of its component bits As a result, specific bits add to the sum as it is represented by a numeral:</p>
  120. <ul>
  121. <li>The read bit adds 4 to its total (in binary 100),</li>
  122. <li>The write bit adds 2 to its total (in binary 010), and</li>
  123. <li>The execute bit adds 1 to its total (in binary 001).</li>
  124. </ul>
  125. <p>These values never produce ambiguous combinations. each sum represents a specific set of permissions. More technically, this is an octal representation of a bit field – each bit references a separate permission, and grouping 3 bits at a time in octal corresponds to grouping these permissions by <strong><span class="first">user</span></strong>, <strong><span class="second">group</span></strong>, and <strong><span class="third">others</span></strong>.</p>
  126. <p><strong>Permission mode 0<span class="first">7</span><span class="second">5</span><span class="third">5</span></strong></p>
  127. <dl class="code">
  128. <dt><strong><span class="first">4+2+1=7</span></strong>
  129. <dd>Read, Write, eXecute</dd>
  130. </dt>
  131. <dt><strong><span class="second">4+1=5</span></strong>
  132. <dd>Read, eXecute</dd>
  133. </dt>
  134. <dt><strong><span class="third">4+1=5</span></strong>
  135. <dd>Read, eXecute</dd>
  136. </dt>
  137. </dl>
  138. <p><strong>Permission mode 0<span class="first">6</span><span class="second">4</span><span class="third">4</span></strong></p>
  139. <dl class="code">
  140. <dt><strong><span class="first">4+2=6</span></strong>
  141. <dd>Read, Write</dd>
  142. </dt>
  143. <dt><strong><span class="second">4</span></strong>
  144. <dd>Read</dd>
  145. </dt>
  146. <dt><strong><span class="third">4</span></strong>
  147. <dd>Read</dd>
  148. </dt>
  149. </dl>
  150. </div>
  151. </div>
  152. <div id="edit_access">
  153. <h3><a class="expander" href=#>How to modify your .htaccess file</a></h3>
  154. <div class="content">
  155. <p>The .htaccess file contains directives (instructions) that tell the server how to behave in certain scenarios and directly affect how your website functions.</p>
  156. <p>Redirects and rewriting URLs are two very common directives found in a .htaccess file, and many scripts such as WordPress, Drupal, Joomla and Magento add directives to the .htaccess so those scripts can function.</p>
  157. <p>It is possible that you may need to edit the .htaccess file at some point, for various reasons.This section covers how to edit the file in cPanel, but not what may need to be changed.(You may need to consult other articles and resources for that information.)</p>
  158. <h4><u>There are Many Ways to Edit a .htaccess File</u></h4>
  159. <ul>
  160. <li>Edit the file on your computer and upload it to the server via FTP</li>
  161. <li>Use an FTP program's Edit Mode</li>
  162. <li>Use SSH and a text editor</li>
  163. <li>Use the File Manager in cPanel</li>
  164. </ul>
  165. <p>The easiest way to edit a .htaccess file for most people is through the File Manager in cPanel.</p>
  166. <h4><u>How to Edit .htaccess files in cPanel's File Manager</u></h4>
  167. <p>Before you do anything, it is suggested that you backup your website so that you can revert back to a previous version if something goes wrong.</p>
  168. <h4><u>Open the File Manager</u></h4>
  169. <ol>
  170. <li>Log into cPanel.</li>
  171. <li>In the Files section, click on the <strong>File Manager</strong> icon.</li>
  172. <li>Check the box for&nbsp;<strong>Document Root for</strong> and select the domain name you wish to access from the drop-down menu.</li>
  173. <li>Make sure&nbsp;<strong>Show Hidden Files (dotfiles)</strong>" is checked.</li>
  174. <li>Click&nbsp;<strong>Go</strong>. The File Manager will open in a new tab or window.</li>
  175. <li>Look for the .htaccess file in the list of files. You may need to scroll to find it.</li>
  176. </ol>
  177. <h4><u>To Edit the .htaccess File</u></h4>
  178. <ol>
  179. <li>Right click on the <strong>.htaccess file</strong> and click&nbsp;<strong>Code Edit</strong> from the menu. Alternatively, you can click on the icon for the .htaccess file and then click on the <strong>Code Editor</strong> icon at the top of the page.</li>
  180. <li>A dialogue box may appear asking you about encoding. Just click&nbsp;<strong>Edit</strong> to continue. The editor will open in a new window.</li>
  181. <li>Edit the file as needed.</li>
  182. <li>Click&nbsp;<strong>Save Changes</strong> in the upper right hand corner when done. The changes will be saved.</li>
  183. <li>Test your website to make sure your changes were successfully saved. If not, correct the error or revert back to the previous version until your site works again.</li>
  184. <li>Once complete, you can click&nbsp;<strong>Close</strong> to close the File Manager window.</li>
  185. </ol>
  186. </div>
  187. </div>
  188. <div id="edit_permissions">
  189. <h3><a class="expander" href=#>How to modify file and directory permissions</a></h3>
  190. <div class="content">
  191. <p>The permissions on a file or directory tell the server how in what ways it should be able to interact with a file or directory.</p>
  192. <p>This section covers how to edit the file permissions in cPanel, but not what may need to be changed.(See the section on what you can do for more information.)</p>
  193. <h4><u>There are Many Ways to Edit a File Permissions</u></h4>
  194. <ul>
  195. <li>Use an FTP program</li>
  196. <li>Use SSH and a text editor</li>
  197. <li>Use the File Manager in cPanel</li>
  198. </ul>
  199. <p>The easiest way to edit file permissions for most people is through the File Manager in cPanel.</p>
  200. <h4><u>How to Edit file permissions in cPanel's File Manager</u></h4>
  201. <p>Before you do anything, it is suggested that you backup your website so that you can revert back to a previous version if something goes wrong.</p>
  202. <h4><u>Open the File Manager</u></h4>
  203. <ol>
  204. <li>Log into cPanel.</li>
  205. <li>In the Files section, click on the <strong>File Manager</strong> icon.</li>
  206. <li>Check the box for&nbsp;<strong>Document Root for</strong> and select the domain name you wish to access from the drop-down menu.</li>
  207. <li>Make sure&nbsp;<strong>Show Hidden Files (dotfiles)</strong>" is checked.</li>
  208. <li>Click&nbsp;<strong>Go</strong>. The File Manager will open in a new tab or window.</li>
  209. <li>Look for the file or directory in the list of files. You may need to scroll to find it.</li>
  210. </ol>
  211. <h4><u>To Edit the Permissions</u></h4>
  212. <ol>
  213. <li>Right click on the <strong>file or directory</strong> and click&nbsp;<strong>Change Permissions</strong> from the menu.</li>
  214. <li>A dialogue box should appear allowing you to select the correct permissions or use the numerical value to set the correct permissions.</li>
  215. <li>Edit the file permissions as needed.</li>
  216. <li>Click&nbsp;<strong>Change Permissions</strong> in the lower left hand corner when done. The changes will be saved.</li>
  217. <li>Test your website to make sure your changes were successfully saved. If not, correct the error or revert back to the previous version until your site works again.</li>
  218. <li>Once complete, you can click&nbsp;<strong>Close</strong> to close the File Manager window.</li>
  219. </ol>
  220. </div>
  221. </div>
  222. </div>
  223. </div>
  224.        </div>
  225.  
  226.        <div style="clear:left;"></div>
  227.        </div>
  228.        <div id="bottom500"></div>
  229. </div>
  230.  
  231.    <script type="text/javascript">
  232.        $(function () {
  233.            $('.expander').simpleexpand();
  234.            prettyPrint();
  235.        });
  236.    </script>
  237.  
  238. </body>
  239.  
  240. </html>
  241.  
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda