It's a bit of a challenge for us to help for the following reasons:
1. The photos you're posting are very low resolution, which makes it difficult for us to see your port settings. In the future, can you please use something like the built-in Windows snipping tool (screen capture)?
https://support.microsoft.com/en-ca/help/13776/windows-use-snipping-tool-to-capture-screenshots2. The log indicates that VC is trying to connect to Kodi on port 9090, and being refused. The one photo of the xJson plugin where the port field is legible says 8080.
a. Do you have the HTTP port set to 9090 or to 8080 in the xJson plugin?
b. Is Kodi open when you try to test the connection?
In brief:
a. Kodi needs to be running in order for VC to connect to it. You'll get a timeout error if Kodi is not running.
b. The HTTP port in the xJson plugin needs to match the port you set in Kodi's web server settings (e.g., 8080, assuming you're not already using that port for other services on this machine). Your log is indicating that you're trying to connect to Kodi via port 9090. That is not advisable, as Kodi uses this port for other purposes, but I don't actually know what problems might result.
c. Once you've tested the connection in the xJson plugin and it is working, be sure to *save* your plugin settings by clicking the Save Options button.
d. The TCP plugin has nothing to do with your communication with Kodi, except insofar as the port you are using to communicate with Alexa must be different from the one you're using to communicate with Kodi. In the photos you posted, in one photo it looks like you might have the TCP port set to 8080, but in another it looks like 8096. Which are you using?
8096 for the TCP plugin/Amazon, and 8080 for xJson/Kodi would be good.
EDIT: I may be misinterpreting the log. Kodi sends its notifications on 9090, and that could be what the log is indicating. So ignore my comments about port 9090 if you haven't done anything with that port yourself.
