1. Advertising
    y u no do it?

    Advertising (learn more)

    Advertise virtually anything here, with CPM banner ads, CPM email ads and CPC contextual links. You can target relevant areas of the site and show ads based on geographical location of the user if you wish.

    Starts at just $1 per CPM or $0.10 per CPC.

500 internal error after migrating site to new server

Discussion in 'Site & Server Administration' started by bfree74, Oct 19, 2012.

  1. #1
    I just migrated my site cheapbeanbags.net from a shared server on GoDaddy to a VPS server. I transferred all my files over and got a 500 error. Then I cleaned out all files and installed WordPress through my VPS and then added back in themes, plugins, etc. I changed the wp-config file to point to my database. Still getting 500 error. This site was a test before I migrate my bigger wordpress site over. Please help me determine what is wrong.
     
    bfree74, Oct 19, 2012 IP
  2. SolidShellSecurity

    SolidShellSecurity Banned

    Messages:
    262
    Likes Received:
    3
    Best Answers:
    1
    Trophy Points:
    45
    #2
    Sounds like a PHP configuration error. Might be running differently.
     
    SolidShellSecurity, Oct 19, 2012 IP
  3. bfree74

    bfree74 Active Member

    Messages:
    119
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    51
    #3
    How do I fix?
     
    bfree74, Oct 19, 2012 IP
  4. SolidShellSecurity

    SolidShellSecurity Banned

    Messages:
    262
    Likes Received:
    3
    Best Answers:
    1
    Trophy Points:
    45
    #4
    Are you running CPanel? How was the server setup? Do you know what are in the error_logs? This is just a short amount of questions that need to be answered.
     
    SolidShellSecurity, Oct 19, 2012 IP
  5. bfree74

    bfree74 Active Member

    Messages:
    119
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    51
    #5
    No, I am running Plesk.

    Here are some examples:

    [Thu Oct 18 10:51:06 2012] [warn] [client 206.160.141.74] mod_fcgid: read data timeout in 45 seconds
    [Thu Oct 18 10:51:06 2012] [error] [client 206.160.141.74] Premature end of script headers: index.php
    [Wed Oct 17 20:43:33 2012] [warn] [client 78.158.11.226] mod_fcgid: stderr: PHP Warning: require(/var/www/vhosts/ip-50-62-72-148.ip.secureserver.net/cheapbeanbags/wp-includes/load.php): failed to open stream: No such file or directory in /var/www/vhosts/ip-50-62-72-148.ip.secureserver.net/cheapbeanbags/wp-settings.php on line 19, referer: http://evuln.com/tools/malware-scanner/cheapbeanbags.net/
    [Wed Oct 17 20:43:33 2012] [warn] [client 78.158.11.226] mod_fcgid: stderr: PHP Fatal error: require(): Failed opening required '/var/www/vhosts/ip-50-62-72-148.ip.secureserver.net/cheapbeanbags/wp-includes/load.php' (include_path='.:') in /var/www/vhosts/ip-50-62-72-148.ip.secureserver.net/cheapbeanbags/wp-settings.php on line 19, referer: http://evuln.com/tools/malware-scanner/cheapbeanbags.net/
    [Wed Oct 17 20:45:08 2012] [warn] [client 76.174.155.25] mod_fcgid: stderr: PHP Warning: require(/var/www/vhosts/ip-50-62-72-148.ip.secureserver.net/cheapbeanbags/wp-includes/load.php): failed to open stream: No such file or directory in /var/www/vhosts/ip-50-62-72-148.ip.secureserver.net/cheapbeanbags/wp-settings.php on line 19
    [Wed Oct 17 20:45:08 2012] [warn] [client 76.174.155.25] mod_fcgid: stderr: PHP Fatal error: require(): Failed opening required '/var/www/vhosts/ip-50-62-72-148.ip.secureserver.net/cheapbeanbags/wp-includes/load.php' (include_path='.:') in /var/www/vhosts/ip-50-62-72-148.ip.secureserver.net/cheapbeanbags/wp-settings.php on line 19
     
    bfree74, Oct 19, 2012 IP
  6. SolidShellSecurity

    SolidShellSecurity Banned

    Messages:
    262
    Likes Received:
    3
    Best Answers:
    1
    Trophy Points:
    45
    #6
    For the first error:

    Edit the file:
    /etc/httpd/conf.d/fcgid.conf
    Specifically, change
    FcgidIOTimeout 45
    to
    FcgidIOTimeout 3600
    3600 seconds = 1 hour. Should be long enough for most but adjust upwards if required. I saw one example quoting 7200 seconds in there.
    Finally, restart Apache to make the new setting active.

    Ypu may also want to look at:
    http://rickchristie.com/blog/2011/note/apache-mod_fcgid-read-data-timeout-error/
    http://www.danielecesarini.com/2012...-read-data-timeout-in-40-seconds-in-centos-5/
     
    SolidShellSecurity, Oct 19, 2012 IP
  7. bfree74

    bfree74 Active Member

    Messages:
    119
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    51
    #7
    I dont have access to the root of my server, so I dont think I can make that change, is there anything else I can do? The only file I see in the /etc/ folder is php.ini
     
    bfree74, Oct 19, 2012 IP
  8. webmaster1189

    webmaster1189 Well-Known Member

    Messages:
    460
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    110
    #8
    the error displayed here is not what causing the 500 error, and the suggestion made by solidshellsecurity is totally useless, he is getting 500 error which normally the cause of server misconfiguration or apache being compiled in an inproper way, icreasing timeout won't fix it at all. can you tell me with what option you compiled your server? i can have it fixed but you don't have root access
     
    webmaster1189, Oct 19, 2012 IP
  9. bfree74

    bfree74 Active Member

    Messages:
    119
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    51
    #9
    Now I have root access through SSH, can you help please?
     
    bfree74, Oct 20, 2012 IP
  10. SolidShellSecurity

    SolidShellSecurity Banned

    Messages:
    262
    Likes Received:
    3
    Best Answers:
    1
    Trophy Points:
    45
    #10
    If you would read what I posted it aligns with what the OP is dealing with. People on Google would also agree if you did a search on the subject matter. Until we no more about his setup we don't know exactly what is wrong so you can't rule out what I said without proper justification. And what I posted above is a configuration issue especially what I read on Plesk forums.
     
    Last edited: Oct 20, 2012
    SolidShellSecurity, Oct 20, 2012 IP
  11. bfree74

    bfree74 Active Member

    Messages:
    119
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    51
    #11
    So what should I do then? Would love to learn how to fix the issue and prevent it any future migrations.
     
    bfree74, Oct 20, 2012 IP
  12. zacharooni

    zacharooni Well-Known Member

    Messages:
    346
    Likes Received:
    20
    Best Answers:
    4
    Trophy Points:
    120
    #12
    From the looks of it, it still has the same path configuration for GoDaddy's server in there, you may want to check the vhost, and your wordpress path configuration to ensure that it points to where your site currently sits on the server (e.g: /home/user/www/wordpress/)
     
    zacharooni, Oct 21, 2012 IP
  13. kevinp2012

    kevinp2012 Greenhorn

    Messages:
    2
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    11
    #13
    Yeah.. that error itself getting confused so what should be suggest here?
     
    kevinp2012, Oct 22, 2012 IP
  14. 123addme

    123addme Active Member

    Messages:
    171
    Likes Received:
    3
    Best Answers:
    0
    Trophy Points:
    58
    #14
    You should run php as module (faster for personal use)
    Go to Websites & Domains > Website Scripting Security then select PHP support (run as Apache module)
     
    123addme, Oct 25, 2012 IP
  15. ggoyal

    ggoyal Greenhorn

    Messages:
    5
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    11
    #15
    The most common reasons for this error are:
    1) error in permissions on the files
    2) error in .htaccess files, if any
     
    ggoyal, Oct 25, 2012 IP
  16. badolfus

    badolfus Greenhorn

    Messages:
    41
    Likes Received:
    1
    Best Answers:
    0
    Trophy Points:
    8
    #16
    I believe it is a problem with the .htaccess file.

    Please try the following steps:

    Rename the file to __htaccess
    Upload an empty file and rename it to .htaccess
    Change the permissions on .htaccess to 666 (rw-rw-rw)
    Set permalinks to a different setting, save it, then switch it back to your usual setting.
    change the .htaccess file permissions back to 644 (rw-r--r--)

    I hope it would resolve your problem
     
    badolfus, Oct 25, 2012 IP
  17. coder77

    coder77 Peon

    Messages:
    11
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #17
    Remove your .htaccess file and rewrite back.
     
    coder77, Nov 1, 2012 IP