Ignition Gateway cannot be found

I am having an issue with my gateway. I was given a gateway from a customer to review. Come to find out it was a 7.9 gateway. I tried to open it in my 8.1 but after restoring the customer gateway on my computer I lost the ability to get the gateway running. I tried the gwcmd commands and got errors with -r, -i, and anything else I tried. It tried restoring a known gateway, but could not access.
So I installed a new version and tried to fix it that way. I can get the new version installed but it errors at the gateway and mentions being able to look at logs. However, that button does not work. I made sure the java file was unzipped from what I saw in other threads. I will attach the wrapper logs if I can here.

wrapper.log (6.4 MB)

Looks like you have a port conflict. The last error in your logs indicates that port 80 is in use by something else. You'll have to shut down whatever is using port 80 and it should start up, then you can change the port Ignition is using to something else.

I have disabled what was using port 80, but using the gwcmd commands I get:
-i: No response from gateway
-r: Error: java.lang.exception: gateway could not be reached, restart was not performed.

Are you trying to revive your v8.1 install or still trying to load the v7.9 gateway?

You should be restoring such a backup into the same version of Ignition that the client uses. Otherwise, you cannot accurately review what they've provided, and if they ask for edits, you cannot provide any exports compatible with their system. Use separate Ignition gateways for each client system, matching their kit as closely as you can (matching installed modules, too).

Thanks for that. Looks like there is something corrupted in the backup they sent me twice. The gateway just goes unknown and I have to do a full uninstall to get anything back up. I have tried version 7.9 and 8.1 and it does the same thing for both.

Surely there is an explanation in the wrapper.log files.

Do a fresh 7.9 install, attempt the restore, and then go get the log after it fails to start.