Trivi

@pablo Me and my friend tried to diagnose that part of the error "[2020-05-20 19:43:26 ERROR] Network port occupied, can't start server." as being how you said even before I made this post but we had made sure nothing else was running on the VM at all and even went as far as creating a new Cloud Server with a new IP and everything and it running completely fine on a freshly made server world but as soon as I transfer the world file in than both errors would be outputted every time and like the mod above said I think it comes down to a corruption problem. 

Yikes, nope I only had it up for about 2 weeks with my girlfriend, I probably should have backed it up right before the updates but I had done a manual hard restart of the VM server and than rebooted through putty to reconnect to where I accepted the updates and then when I commanded the server to start it got the error. 

There's no way of recovering the world eh? We only had built a lot mostly in a few chunks near spawn like 400 or so blocks from spawn.

Here is the zip file of the server on Google Drive, https://drive.google.com/open?id=1pIeB6U_na_v3nwo0ad18VrGJpE-YugU1

Thanks in advance

No not at all, I had kept everything vanilla and didn't change anything between the time it worked and didn't work besides installing linux updates that I did after a server restart on my VM.