Announcement

Collapse
No announcement yet.

500 Internal Server Error after setup SSL

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [Bug / Issue] 500 Internal Server Error after setup SSL

    Hello everyone,

    I got an error: HTTP ERROR 500 after I upgraded to Vbulletin 5 with SSL.

    I still can use Vbulletin 5 with non-SSL.

    This is my site: https://ebook4vn.com/
    https://ebook4vn.com/info-ebook4vn.php

    I hope someone can help me.

    I wish you a Happy New Year.

  • #2
    Try to rebuild styles in AdminCP -> Maintainance -> Gerneral Update Tools -> Rebuild Styles (.../admincp/misc.php?do=chooser&)
    vBulletin-Forum.de closed!

    Comment


    • vietdotseo
      vietdotseo commented
      Editing a comment
      I can not login to admincp: HTTP ERROR 500

  • #3
    Do you have the original .htaccess file in the forum-root directory? Please rename it from htaccess.txt to .htaccess if you didn't yet.
    mod_rewrite seems to be activated on the server.

    Did you following this https://www.vbulletin.com/forum/arti...forum-to-https ?
    vBulletin-Forum.de closed!

    Comment


    • #4
      Yes. I have the original .htaccess file.

      PHP Code:
      <IfModule mod_rewrite.c>
          
      RewriteEngine On

          
      # In some cases where you have other mod_rewrite rules, you may need to remove the 
          # comment on the following RewriteBase line and change it to match your folder name. 
          # This resets the other mod_rewrite rules for just this directory
          # If your site was www.example.com/forum, the setting would be /forum/
          
      RewriteBase /

          
      #To redirect users to the secure version of your site, uncomment the lines below 
          
      RewriteCond %{HTTPS} !=on
          RewriteRule 
      .* https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]

          # Send css calls directly to the correct file VBV-7807
          
      RewriteRule ^css.phpcore/css.php [NC,L]

          
      # Redirect old install path to core.
          
      RewriteRule ^installcore/install/ [NC,L]

          
      # Main Redirect
          
      RewriteCond %{REQUEST_URI} !\.(gif|jpg|jpeg|png|css)$
          
      RewriteCond %{REQUEST_FILENAME} !-f
          RewriteCond 
      %{REQUEST_FILENAME} !-d
          RewriteRule 
      ^(.*)$ index.php?routestring=$[L,QSA]

          
      # Because admincp is an actual directory.
          
      RewriteRule ^(admincp/)$ index.php?routestring=$[L,QSA]

      </
      IfModule
      I upgraded from vbulletin 4 with ssl to vbulletin 5. That's mean I didn't edit this:

      vBulletin 5
      Go to vBulletin Options > vBulletin Options > Site Name / URL / Contact Details.
      Edit these three settings: 'vBulletin URL'; 'Login URL'; 'Core URL' and add the 's' into the URL.
      For example, if your URL is http://www.contoso.com/forum, change it to https://www.contoso.com/forum
      NOTE: Do not remove the word 'core' at the end of the core URL. You will break your site!

      Then go to Settings > Options > Server Settings & Optimization Options > Use Remote jQuery
      Set this to Google.

      The key to all three vBulletin versions is that all you do in the URL settings is change http to https. Do not alter any other part of the URL.

      Once you have changed these settings, go to AdminCP > Maintenance > General Update Tools, and rebuild the styles. (In vB3 this is AdminCP > Maintenance > Update Counters). Leave the default settings and just run this update tool.
      Because I can not access admincp after upgraded.


      Originally posted by delicjous View Post
      Do you have the original .htaccess file in the forum-root directory? Please rename it from htaccess.txt to .htaccess if you didn't yet.
      mod_rewrite seems to be activated on the server.

      Did you following this https://www.vbulletin.com/forum/arti...forum-to-https ?

      Comment


      • #5
        That isn't a vBulletin installation on the above URL.

        A 500 server error doesn't provide any information for debugging. It could be a misconfiguration in Apache. It could be a PHP error. In order to determine what the actual error is, you need to look at your httpd and php error logs to find the error. Once we know the error, we can assist in resolving it.
        Translations provided by Google.

        Wayne Luke
        The Rabid Badger - a vBulletin Cloud demonstration site.
        vBulletin 5 API - Full / Mobile
        Vote for your favorite feature requests and the bugs you want to see fixed.

        Comment

        Related Topics

        Collapse

        Working...
        X