500 Internal Server Error on Linux-Apache-MySQL-PHP (LAMP) server almost always indicative of some error(s) in .htaccess. There is some conflict – either is not fully complete, there are errors on .htaccess or some error in PHP is happening. Check the PHP log or ask your webhost to give you, if you have no access to PHP error log.
Login to FTP. Renamed the file .htaccess to __htaccess. Create a blank file with the name .htaccess. Change the permissions on .htaccess to either 770 or 777 (yes). Try to login to WP dash, set permalinks to previous settings. Then change the .htaccess file permission back to 644 or may be 600.
chmod calculator ===> https://www.wwwwdot.com/chmod-calculator/
Please follow my guide to troubleshoot 500 ISE to avoid 500 errors in future. Actually it is difficult to write so much details here, I wanted to point towards solving your current situation.
it is always better to read the Documentation before the upgrade, that is usually hyperlinked on the WP update notification thing, which arrives on your dashboard. Usually someone from core writes them.
Ask the webhost whether they have upgraded properly.
Last way is to repair WordPress or Reinstalling WP (practically replacing all the WordPress files, making wp config inactive and running the installation script with the old database details) to the last back version.
There is a default way for WordPress to get repaired. Usually it is required for issue with database – https://codex.www.ads-software.com/Editing_wp-config.php#Automatic_Database_Optimizing
You have 404, that is probably basic issue. 500 arrived after you edited. 404 on a running WP can happen due to many reasons.