Announcement

Collapse
No announcement yet.

Internal Server error 500 after move to new dedicated server

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

  • [CMS] Internal Server error 500 after move to new dedicated server

    Hello,

    im using vbulletin long time ago, to my old server, all working fine to this old server ( Centos 5 - 32bit), yesterday i decide to upgrade my server to 32gb ram with more power Cpu and 64BIT of Centos.

    im login to my new server WHM (cPanel) to transfer my old accounts (websites) to the new server. There i have two wordpress blogs and the vbulletin Forum.

    this 2 blogs working ok to the new server but the vBulletin shows me internal server error 500...

    can someone take a look? i have the same php, apache, mysql the same apache and php modules. The only deference is the OS version (32bit vs 64bit) is this problem? i have to restore my server to 32 bit?

    thanks

  • #2
    Internal Server errors are generally related to either a server problem, or added code to the vB files and/or templates.

    To troubleshoot this, first reupload all the original vB non-image files (except install.php). Make sure you upload these in ASCII format and overwrite the ones on the server. Also be sure to upload the admincp files to whichever directory you have set in your config.php file. Then run 'Suspect File Versions' in Diagnostics to make sure you have all the original files for your version and that none show 'File does not contain expected contents':

    Admin CP -> Maintenance -> Diagnostics -> Suspect File Versions

    [Note: In some cases you may also need to remove any of the listed .xml files in the includes/xml directory.]

    Next, disable all products (except vB Blog and vB CMS if you are running the Suite.)

    Admin CP -> Plugins & Products -> Manage Products -> Disable

    Then manually uncheck all plugins that are not for 'vBulletin Blog' and vBulletin CMS' here:

    Admin CP -> Plugins & Products -> Plugin Manager

    Then if you still have this problem, create a new style and choose no parent style. This will force it to use the default templates. Finally empty your browser cache, close all browser windows then try again. Make sure you change to the new style and view your forums with it.

    Do you have the same problem?
    Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
    Change CKEditor Colors to Match Style (for 4.1.4 and above)

    Steve Machol Photography


    Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


    Comment


    • #3
      Originally posted by Steve Machol View Post
      Internal Server errors are generally related to either a server problem, or added code to the vB files and/or templates.

      To troubleshoot this, first reupload all the original vB non-image files (except install.php). Make sure you upload these in ASCII format and overwrite the ones on the server. Also be sure to upload the admincp files to whichever directory you have set in your config.php file. Then run 'Suspect File Versions' in Diagnostics to make sure you have all the original files for your version and that none show 'File does not contain expected contents':

      Admin CP -> Maintenance -> Diagnostics -> Suspect File Versions

      [Note: In some cases you may also need to remove any of the listed .xml files in the includes/xml directory.]

      Next, disable all products (except vB Blog and vB CMS if you are running the Suite.)

      Admin CP -> Plugins & Products -> Manage Products -> Disable

      Then manually uncheck all plugins that are not for 'vBulletin Blog' and vBulletin CMS' here:

      Admin CP -> Plugins & Products -> Plugin Manager

      Then if you still have this problem, create a new style and choose no parent style. This will force it to use the default templates. Finally empty your browser cache, close all browser windows then try again. Make sure you change to the new style and view your forums with it.

      Do you have the same problem?
      Cant go to admincp (in the new server) i will go now to the new server and upload the lastest version of vbulletin to see if i can update the version!!!

      Comment


      • #4
        What do you mean? What did you do exactly?
        Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
        Change CKEditor Colors to Match Style (for 4.1.4 and above)

        Steve Machol Photography


        Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


        Comment


        • #5
          Originally posted by Steve Machol View Post
          What do you mean? What did you do exactly?
          is possible to get payble support? to give my root pass, cpanel passes and all that you want to fix my problems?

          Comment


          • #6
            Have you followed those instructions? That is the next step. If you have followed them and ttill have this error, then this is a server issue. You will need to contact your host about this.
            Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
            Change CKEditor Colors to Match Style (for 4.1.4 and above)

            Steve Machol Photography


            Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


            Comment


            • #7
              I've just had exactly the same thing happen to me. I've done a transfer from Centos 5 32bit to a Centos 5 64bit server. I used the WHM transfer feature to copy accounts. All seems to have moved as it should be, all the MySQL and accounts have transferred over too, but as soon as I hit the forum I get a 500 error page and can't access any of the other parts of the site. I have tried a fresh install of the forum files and the database, but neither has worked. I will check it out with my host, see what they say, but they aren't often very useful when it comes to these sort of things. Will let you know if I get anywhere.

              Comment

              widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
              Working...
              X