• Resolved jkester1986

    (@jkester1986)


    I moved my wordpress site to a different folder, and now I get error 500 message of the following when trying to download:

    The website encountered an error while retrieving https://mubetapsi.org/intranet/?mdocs-file=2991&mdocs-url=false. It may be down for maintenance or configured incorrectly.

    Everything else seems to work fine, preview displays the documents as it should, sharing pops up properly, etc. I tried uploading new files thinking it was a linking issue due to the folder change, but that did not resolve anything.

Viewing 15 replies - 1 through 15 (of 21 total)
  • Plugin Author bhaldie

    (@bhaldie)

    try this may help:

    404 Error when trying to access document page
    If you get a 404 error when trying to access your Memphis documents pages try going to Setting>Permalinks and pressing Save. This may solve the issue, if it doesn’t please contact me for more support.

    Thread Starter jkester1986

    (@jkester1986)

    Nope, that didn’t work

    Plugin Author bhaldie

    (@bhaldie)

    can you check you apache error logs for more details, this should give you more of an indication of what the problem might be.

    Thread Starter jkester1986

    (@jkester1986)

    Are you referring to the error.log file that wordpress should be able to generate? It’s not working properly. Had been, but so many errors were getting logged a while back that I deleted it, or the contents, or both – I forget which order – and now, even though the file is there, it’s empty…

    Plugin Author bhaldie

    (@bhaldie)

    no I’m talking about your severs error logs, apache error.logs are usually found in your admin console of your hosts.

    Thread Starter jkester1986

    (@jkester1986)

    Ah, ok, thanks. I will take a look at some point, going out of state so I won’t have a chance to look right away

    Plugin Author bhaldie

    (@bhaldie)

    no big deal, let me know the results when u get a chance.

    Thread Starter jkester1986

    (@jkester1986)

    Actually, looks like I’ve got more time than expected, carpoolers are running late. Here’s the only error message that seems to be directly related to memphis docs:

    A session had already been started – ignoring session_start() in /var/www/vhosts/mubetapsi.org/httpdocs/intranet/wp-content/plugins/memphis-documents-library/mdocs-functions.php on line 244, referer: https://mubetapsi.org/intranet/brothers-hangout/

    tried searching for mdocs-file from the error 500 message, but nothing showing

    Plugin Author bhaldie

    (@bhaldie)

    yeah that is an unrelated warning.

    If you upload a new file, does the 500 error still occur?

    Thread Starter jkester1986

    (@jkester1986)

    yes

    Plugin Author bhaldie

    (@bhaldie)

    make sure that your documents folder has the proper permission on it. To test make the uploads folder 770 the mdocs folder 770 and the files inside the mdocs folder 660

    Thread Starter jkester1986

    (@jkester1986)

    I’m getting an “Operation not permitted” message in FileZilla when trying to change the file permissions (I can change the folder permissions fine)

    Thread Starter jkester1986

    (@jkester1986)

    Oh actually my bad – the mdocs folder won’t change either. I didn’t even bother changing the uploads bc it’s set to 777

    Thread Starter jkester1986

    (@jkester1986)

    (mdocs is set to 755, all the files to 644)

    Plugin Author bhaldie

    (@bhaldie)

    If you still have this issue here is some points that might help.

    Checking for Corrupt .htaccess File

    The first thing you should do when troubleshooting the internal server error in WordPress is check for the corrupted .htaccess file. You can do so by renaming your main .htaccess file to something like .htaccess_old. To rename the .htaccess file, you will need to login to your site using the FTP. Once you are in, the .htaccess file will be located in the same directory where you will see folders like wp-content, wp-admin, and wp-includes.
    Once you have renamed the .htaccess file, try loading your site to see if this solved the problem. If it did, then give yourself a pat on the back because you fixed the internal server error. Before you move on with other things, make sure that you go to Settings ? Permalinks and click the save button. This will generate a new .htaccess file for you with proper rewrite rules to ensure that your post pages do not return a 404.
    If checking for the corrupt .htaccess file solution did not work for you, then you need to continue reading this article.

    Increasing the PHP Memory Limit

    Sometimes this error can happen if you are exhausting your PHP memory limit. Use our tutorial on how to increase PHP memory limit in WordPress to fix that.
    If you are seeing the internal server error only when you try to login to your WordPress admin or uploading an image in your wp-admin, then you should increase the memory limit by following these steps:
    Create a blank text file called php.ini
    Paste this code in there: memory=64MB
    Save the file
    Upload it into your /wp-admin/ folder using FTP
    Several users have said that doing the above fixed the admin side problem for them.
    If increasing the memory limit fix the problem for you, then you have fixed the problem temporarily. The reason why we say this is because there has to be something that is exhausting your memory limit. This could be a poorly coded plugin or even a theme function. We strongly recommend that you ask your WordPress web hosting company to look into the server logs to help you find the exact diagnostics.
    If increasing the PHP memory limit did not fix the issue for you, then you are in for some hard-core trouble shooting.

    Deactivate all Plugins

    If none of the above solutions worked for you, then this error is most likely being caused by a specific plugin. It is also possible that it is a combination of plugins that are not playing nice with each other. Sadly, there is no easy way to find this out. You have to deactivate all WordPress plugins at once.
    Follow the following tutorial on how to deactivate all WordPress plugins without WP-Admin.
    If disabling all plugins fixed the error, then you know it is one of the plugins that is causing the error. Simply go through and reactivate one plugin at a time until you find the one that caused the issue. Get rid of that plugin, and report the error to the plugin author.

    Re-uploading Core Files

    If the plugin option didn’t fix the internal server error, then it is worth re-uploading the wp-admin and wp-includes folder from a fresh WordPress install. This will NOT remove any of your information, but it may solve the problem in case any file was corrupted.
    Ask your Hosting Provider

    If nothing works, then you need to get in touch with your hosting provider. By looking at the server logs, they should be able to get to the bottom of things.
    These are all the possible solutions that may fix the internal server error problem in WordPress. Did any of the above solutions fixed the problem for you? If so, then please let us know in the comments. Did you encounter the internal server error issue in the past? how did you fix it? If you know of a fix that is not listed in the article above, then please contribute in the comments below. We will make sure to keep the article up to date with any new advice from the users.

Viewing 15 replies - 1 through 15 (of 21 total)
  • The topic ‘Documents won't download’ is closed to new replies.