twokay

Im also wanting the gateway to work. Ive tried running the latest console version (0.0.11) on the remote host as well as manually patching the vmoptions on the remote machine. When using gateway with a goland project it fails to activate. Also the jetbrainser console version fails to find the vmoptions on the remote host. Can you provide step by step instructions for Gateway? Gateway launched project (GoLand) Remote vmoptions

I tried, managed to get GoLand working using the 0.0.7 build from scratch from github. Unfortunately remote development doesn't work. I tried putting the vmoptions, agent etc into the right locations, and then got a popup asking for a licence - it was complaining about not being able to contact the licence server. ``` Cannot obtain ticket from https://127.0.0.1:1337 due to connectivity problem: Connection refused: no further information ``` This happens with both Linux and WSL remote debugging on windows. I posted a github issue. Fingers crossed. What is strange is that if you setup a trial licence, then create a new remote debugging session, the remote version uses the trial licence whilst the local GoLand uses the agent.jar. When I removed the agent.jar I got an error about a missing file from the vmoptions. It appears the agent.jar loads correctly in the remote system, so this might be impossible to solve since we will need an updated agent.jar I also tried updating the *.key files to point to the remote servers ip address.

Same for me, Webstorm 2020.3 all methods do not work.