Title: HTTP 500
Last modified: April 18, 2021

---

# HTTP 500

 *  [gentlerv](https://wordpress.org/support/users/gentlerv/)
 * (@gentlerv)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/http-500-5/)
 * Dear all,
 * using:
    1) Ubuntu 20.04 2 2) Nginx 1.18 3) MariaDB 4) vsFTP 5) wordpress
 * I installed on a already working server the last three items in the list
    The
   NGINX server can display .html and php information under /var/www/html SSl is
   installed using certbot but not activated
 * When change the root path to /var/www/html/wordpress I receive the http 500 error
   
   The database is tested with credentials by adding a remote IP address to the 
   database and used the MYSQL working set to test the connection, this went fine
   I added the php.ini file with memory=128M, removed the standard html file from/
   var/www/html directory As everything looks normal and no errors in any logfile/
   var/log/error.log Everything I could test I did, only changing the root from 
   one file to the other give me the http 500 error. The user rights are recursive
   from /var/www/html and uploading by filezilla and overwrite the existing files
   dind’t help The .htaccess file is filled with information but all comment out,
   wp-config.php is created with the right information (the same as used in the 
   remote testing).
 * Please tell me what todo to get this working
 * Thanks
 * gentlerv
    -  This topic was modified 5 years, 1 month ago by [gentlerv](https://wordpress.org/support/users/gentlerv/).
    -  This topic was modified 5 years, 1 month ago by [gentlerv](https://wordpress.org/support/users/gentlerv/).
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fhttp-500-5%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Moderator [t-p](https://wordpress.org/support/users/t-p/)
 * (@t-p)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/http-500-5/#post-14333573)
 * Internal server errors (error 500) are often caused by plugin or theme function
   conflicts, so if you have access to your admin panel, try deactivating all plugins.
   If you don’t have access to your admin panel, try [manually resetting your plugins](https://wordpress.org/support/article/faq-troubleshooting/#how-to-deactivate-all-plugins-when-not-able-to-access-the-administrative-menus)(
   no Dashboard access required). If that resolves the issue, reactivate each one
   individually until you find the cause.
 * If that does not resolve the issue, try switching to the default theme for your
   version of WordPress to rule-out a theme-specific issue. If you don’t have access
   to your admin panel, access your server via [SFTP or FTP](https://wordpress.org/support/article/ftp-clients/),
   or a file manager in your hosting account’s control panel, navigate to `/wp-content/
   themes/` and rename the directory of your currently active theme. This will force
   the default theme to activate and hopefully rule-out a theme-specific issue.
 * If that does not resolve the issue, it’s possible that a `.htaccess` rule could
   be the source of the problem. To check for this, access your server via SFTP 
   or FTP, or a file manager in your hosting account’s control panel, and rename
   the `.htaccess` file. If you can’t find a `.htaccess` file, make sure that you
   have set your SFTP or FTP client to view invisible files.
 * If you weren’t able to resolve the issue by either resetting your plugins and
   theme or renaming your `.htaccess` file, we may be able to help, but we’ll need
   a more detailed error message.
 * **Internal server errors are usually described in more detail in the server error
   log. If you have access to your server error log, generate the error again, note
   the date and time, then immediately check your server error log for any errors
   that occurred during that time period. If you don’t have access to your server
   error log, ask your hosting provider to look for you.**
 *  Thread Starter [gentlerv](https://wordpress.org/support/users/gentlerv/)
 * (@gentlerv)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/http-500-5/#post-14334369)
 * Thank you,
    Yes I can reach my own server and installed all using ssl putty connection.
   Error logs does not reveal any problems. This let me decide to remove the Virtual
   machine and start with a fresh image from Ubuntu 20.04. Will keep this forum 
   updated after the new installation is finished.
 *  Thread Starter [gentlerv](https://wordpress.org/support/users/gentlerv/)
 * (@gentlerv)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/http-500-5/#post-14344507)
 * Here we go what I did and found out.
    I use Hyper-V as platform with the latest
   updates until now. The Ubuntu image I used before could not install: Ubuntu 18.04.
   Downloading Ubuntu 18.04 version 5 .iso solved that problem. Installed Nginx 
   1.18, Nariadb 15.1, PHP7.4-FPM and configured the user in Unix to cope with permissions.
   The basic NGINX site was working including php, then copied my old wordpress 
   with the wp-config.php file to /var/www/html/ Received again http500 error but
   now got a parsing error in the log file. expecting end of file in /var/www/html/
   wordpress/wp-config.php Found a double block starting again with <php. After 
   removing the extra information up to the second <php, everything started to work.
   Now going to learn wordpress …YEAH

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘HTTP 500’ is closed to new replies.

## Tags

 * [Property](https://wordpress.org/support/topic-tag/property/)

 * In: [Installing WordPress](https://wordpress.org/support/forum/installation/)
 * 3 replies
 * 2 participants
 * Last reply from: [gentlerv](https://wordpress.org/support/users/gentlerv/)
 * Last activity: [5 years, 1 month ago](https://wordpress.org/support/topic/http-500-5/#post-14344507)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
