We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 45088
    • 8 Posts
    Google sees an internal error. What do I have to change in the .htacces file. I insert this file . But Google Analytics works.
    Thank you for your help
    Philippe : Newbie with modx


    Googlebot-Typ: Web
    Download-Zeit (in Millisekunden): 139
    HTTP/1.1 500 Internal Server Error


    # MODx supports Friendly URLs via this .htaccess file. You must serve web
    # pages via Apache with mod_rewrite to use this functionality, and you must
    # change the file name from ht.access to .htaccess.
    #
    # Make sure RewriteBase points to the directory where you installed MODx.
    # E.g., "/modx" if your installation is in a "modx" subdirectory. If you have
    # problems with your .htaccess working at all, try un-commenting the first
    # line above the "RewriteEngine On" directive.
    #
    # You may choose to make your URLs non-case-sensitive by adding a NC directive
    # to your rule: RewriteRule ^(.*)$ index.php?q=$1 [L,QSA,NC]

    Options +ExecCGI +FollowSymLinks -Indexes -MultiViews
    RewriteEngine On
    RewriteBase /


    # Fix Apache internal dummy connections from breaking [(site_url)] cache
    RewriteCond %{HTTP_USER_AGENT} ^.*internal\ dummy\ connection.*$ [NC]
    RewriteRule .* - [F,L]


    # Rewrite www.domain.com -> domain.com -- used with SEO Strict URLs plugin
    #RewriteCond %{HTTP_HOST} .
    #RewriteCond %{HTTP_HOST} !^example-domain-please-change\.com [NC]
    #RewriteRule (.*) http://example-domain-please-change.com/$1 [R=301,L]
    #
    # or for the opposite domain.com -> www.domain.com use the following
    # >>> DO NOT USE BOTH THE ABOVE AND BELOW <<<
    #
    RewriteCond %{HTTP_HOST} .
    RewriteCond %{HTTP_HOST} !^www\.urologie-am-bahnhofsplatz\.de [NC]
    RewriteRule (.*) http://www.urologie-am-bahnhofsplatz.de/$1 [R=301,L]



    # Rewrite secure requests properly to prevent SSL cert warnings, e.g. prevent
    # https://www.domain.com when your cert only allows https://secure.domain.com
    #RewriteCond %{SERVER_PORT} !^443
    #RewriteRule (.*) https://example-domain-please-change.com.com/$1 [R=301,L]



    # The Friendly URLs part
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)$ index.php?q=$1 [NC,L,QSA]



    # Make sure .htc files are served with the proper MIME type, which is critical # for XP SP2. Un-comment if your host allows htaccess MIME type overrides.

    #AddType text/x-component .htc



    # If your server is not already configured as such, the following directive
    # should be uncommented in order to set PHP's register_globals option to OFF.
    # This closes a major security hole that is abused by most XSS (cross-site
    # scripting) attacks. For more information: http://php.net/register_globals
    #
    # To verify that this option has been set to OFF, open the Manager and choose
    # Reports -> System Info and then click the phpinfo() link. Do a Find on Page
    # for "register_globals". The Local Value should be OFF. If the Master Value
    # is OFF then you do not need this directive here.
    #
    # IF REGISTER_GLOBALS DIRECTIVE CAUSES 500 INTERNAL SERVER ERRORS :
    #
    # Your server does not allow PHP directives to be set via .htaccess. In that
    # case you must make this change in your php.ini file instead. If you are
    # using a commercial web host, contact the administrators for assistance in
    # doing this. Not all servers allow local php.ini files, and they should
    # include all PHP configurations (not just this one), or you will effectively
    # reset everything to PHP defaults. Consult www.php.net for more detailed
    # information about setting PHP directives.

    #php_flag register_globals Off



    # For servers that support output compression, you should pick up a bit of
    # speed but un-commenting the following lines.

    #php_flag zlib.output_compression On
    #php_value zlib.output_compression_level 5



    # The following directives stop screen flicker in IE on CSS rollovers. If
    # needed, un-comment the following rules. When they're in place, you may have
    # to do a force-refresh in order to see changes in your designs.

    #ExpiresActive On
    #ExpiresByType image/gif A2592000
    #ExpiresByType image/jpeg A2592000
    #ExpiresByType image/png A2592000
    #BrowserMatch "MSIE" brokenvary=1
    #BrowserMatch "Mozilla/4.[0-9]{2}" brokenvary=1
    #BrowserMatch "Opera" !brokenvary
    #SetEnvIf brokenvary 1 force-no-vary
    [ed. note: philingbb last edited this post 12 years, 11 months ago.]
      • 1343 ☆ A M B ☆
      • 2,213 Posts
      Hello,

      The two most common explinations for 500 errors are:

      • Invalid .htaccess code
      • Incorrect File/Folder Permissions

      You can eliminate the first cause quickly by renaming .htaccess to something else (ex: off.htaccess). If you refresh the page and still get a 500 error, then the problem isn't with your .htaccess file. You can rename it back to .htaccess again, as you will likely need some of those settings.

      The next item to check is your permissions, this will vary based on your hosting provider. Typically you see 644/755 used for file/folder (respectively) so make sure all files/folders are set accordingly.

      If the problem persists let us know, and include some details on your hosting environment.
        Patrick | Server Wrangler
        About Me: Website | Tweets |  MODX Hosting
        • 45088
        • 8 Posts
        Hello,

        So I renamed the .htaccess to foo .htaccess and still got the HTTP/1.1 500 Internal Server Error.
        I see that the main folder manager have a 710 permissions.

        Most of the files or folders have 710 or 740 permissions.

        Do I have to change them to 755?
        Thanks
        Philippe


        /.gitignore
        /.htaccess
        /assets
        /google44....acd2ed.html
        /index.php
        /manager
        /manager/.htaccess
        /manager/actions
        /manager/frames
        /manager/help
        /manager/includes
        /manager/index.php
        /manager/media
        /manager/processors
        /robots.txt
        /sitemap.xml
          • 3749
          • 24,544 Posts
          755 for directories and 644 for files are very common these days. They're required on hosts using suPHP, suExec, and some other configurations.
            Did I help you? Buy me a beer
            Get my Book: MODX:The Official Guide
            MODX info for everyone: http://bobsguides.com/modx.html
            My MODX Extras
            Bob's Guides is now hosted at A2 MODX Hosting
            • 45088
            • 8 Posts
            I have had no changes ....
              • 37110
              • 72 Posts
              That's an error with an output filter. If you open firebug you can see the headers and there will be a 500 header.
              Try the following: Remove piece by piece inside your template and reload the page. If the 500 header is gone you know where the error is.

              Most likely it is something like this: [[*someting:notempty=``:else=``]] you have to use there [[*something:eq=``:then=``:else=``]]
                • 45088
                • 8 Posts
                OK thanks i will try it. and will reply you the results.
                Philippe