Can't seem to connect from Jetbrains Gateway to Codespace

[sitbon]

Select Topic Area

Bug

Body

I tried to create and open a new codespace for the django/django project and was unable to connect from Jetbrains Gateway, even after numerous attempts and changing the machine type to 16-core. The idea of Codespaces is great but it seems like something is wrong. Could the size of the Django project be causing the remote IDE backend to not start in time?

Log Output

==== FAILURES ====

The following exception failed the deployment
com.jetbrains.gateway.ssh.deploy.DeployException: 

Details:
An error occurred while executing command: 'host-status --ide-path=/workspaces/.codespaces/shared/editors/jetbrains/pycharm-2023.1.1 --project-path=/workspaces/django'
Exit code: 1
	at com.jetbrains.gateway.ssh.DeployFlowUtil$fullDeployCycleImpl$2.invokeSuspend(DeployFlowUtil.kt:299)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at com.intellij.openapi.rd.util.CoroutineProgressContext$Companion$create$task$1$3.invokeSuspend(BackgroundProgressCoroutineUtil.kt:174)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:280)
	at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:85)
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59)
	at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source)
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38)
	at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source)
	at com.intellij.openapi.rd.util.CoroutineProgressContext$Companion$create$task$1.invoke(BackgroundProgressCoroutineUtil.kt:170)
	at com.intellij.openapi.rd.util.CoroutineProgressContext$Companion$create$task$1.invoke(BackgroundProgressCoroutineUtil.kt:160)
	at com.intellij.openapi.rd.util.CoroutineProgressContext$Companion$createModal$1$1.run(BackgroundProgressCoroutineUtil.kt:205)
	at com.intellij.openapi.progress.impl.CoreProgressManager.startTask(CoreProgressManager.java:428)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.startTask(ProgressManagerImpl.java:115)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressSynchronously$9(CoreProgressManager.java:512)
	at com.intellij.openapi.progress.impl.ProgressRunner.lambda$new$0(ProgressRunner.java:87)
	at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:251)
	at com.intellij.openapi.progress.ProgressManager.lambda$runProcess$0(ProgressManager.java:71)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:186)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$13(CoreProgressManager.java:604)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:679)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:635)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:603)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:61)
	at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:173)
	at com.intellij.openapi.progress.ProgressManager.runProcess(ProgressManager.java:71)
	at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$5(ProgressRunner.java:251)
	at com.intellij.openapi.progress.impl.ProgressRunner.lambda$launchTask$18(ProgressRunner.java:465)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699)
	at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: com.jetbrains.gateway.ssh.deploy.DeployException: 

Details:
An error occurred while executing command: 'host-status --ide-path=/workspaces/.codespaces/shared/editors/jetbrains/pycharm-2023.1.1 --project-path=/workspaces/django'
Exit code: 1
	at com.jetbrains.gateway.ssh.DeployFlowUtil$fullDeployCycleImpl$2.invokeSuspend(DeployFlowUtil.kt:294)
	... 37 more
Caused by: com.jetbrains.gateway.ssh.deploy.DeployException: 

Details:
An error occurred while executing command: 'host-status --ide-path=/workspaces/.codespaces/shared/editors/jetbrains/pycharm-2023.1.1 --project-path=/workspaces/django'
Exit code: 1
	at com.jetbrains.gateway.ssh.DeployFlowUtil$fullDeployCycleImpl$2.invokeSuspend(DeployFlowUtil.kt:292)
	... 37 more
Caused by: com.jetbrains.gateway.ssh.RemoteCommandException: 

Details:
An error occurred while executing command: 'host-status --ide-path=/workspaces/.codespaces/shared/editors/jetbrains/pycharm-2023.1.1 --project-path=/workspaces/django'
Exit code: 1
	at com.jetbrains.gateway.ssh.GoHighLevelHostAccessor.createException(GoHighLevelHostAccessor.kt:210)
	at com.jetbrains.gateway.ssh.GoHighLevelHostAccessor.callAndGetError(GoHighLevelHostAccessor.kt:176)
	at com.jetbrains.gateway.ssh.GoHighLevelHostAccessor.access$callAndGetError(GoHighLevelHostAccessor.kt:35)
	at com.jetbrains.gateway.ssh.GoHighLevelHostAccessor$callAndGetError$1.invokeSuspend(GoHighLevelHostAccessor.kt)
	... 37 more



==== ENVIRONMENT ====

INSTALLED PRODUCTS

	


AVAILABLE MEMORY

	7.75GB



==== DIAGNOSTIC ERRORS ====

Could not get host jstack: 

Details:
An error occurred while executing command: 'get-jstack --ide-path=/workspaces/.codespaces/shared/editors/jetbrains/pycharm-2023.1.1 --project-path=/workspaces/django'
Exit code: 1

[Primus66]

1. Check Network Connection: Ensure that your network connection is stable and not blocking any outbound traffic that Codespaces might require.
2. Retry the Creation: Sometimes, issues like this can be transient. Try creating the Codespace again and see if the problem persists. It could have been a temporary issue on the Codespaces infrastructure.
3. Review Configuration: Double-check the configuration settings for your Codespace, especially the paths and settings related to the Python environment and your Django project. Ensure that all paths and configurations are correct.
4. Clean Up Existing Codespaces: If there are any existing Codespaces related to your project, consider cleaning them up or deleting them before creating a new one. Lingering Codespaces might interfere with new ones.

I hope these help

[sitbon]

Thank you for the suggestions but it still doesn't work.

1. Check Network Connection: Ensure that your network connection is stable and not blocking any outbound traffic that Codespaces might require.

Network connection is 100% stable and not blocked or filtered.

2. Retry the Creation: Sometimes, issues like this can be transient. Try creating the Codespace again and see if the problem persists. It could have been a temporary issue on the Codespaces infrastructure.

Retried this twice, and again after many hours.

3. Review Configuration: Double-check the configuration settings for your Codespace, especially the paths and settings related to the Python environment and your Django project. Ensure that all paths and configurations are correct.

All paths and configs are correct (again, this is for the Django repo), and it does not progress to the point of setting up any environments - the process always fails at "Starting the remote IDE Backend". There is not anything else to configure related to the remote backend as far as Gateway or PyCharm are concerned.

4. Clean Up Existing Codespaces: If there are any existing Codespaces related to your project, consider cleaning them up or deleting them before creating a new one. Lingering Codespaces might interfere with new ones.

It's my only Codespace.

At this point, I'm very curious about whether anyone else is currently able to launch a Codespace with that same repo.

[GaryHo34]

Might be issue on jetbrain side. I downgrade my intellij to 2022.2 and it works perfectly. (if you try to downgrade IDE version, remember to install the corresponding github codespace plugin version)

[luq7]

Another approach that worked for me was this

[alita-moore]

The issue for me was that I was running the codespace in a docker container and I needed to install / start sshd:

sudo apt install ssh-server
sudo service ssh start

[adamcloudboss]

@alita-moore this solved it for me - installing openssh-server in my ubuntu container, then starting the service from VSCode. After that I was able to connect to it from the JB Gateway.

[heathdutton]

The Codespaces plugin for Gateway was discontinued. I put together a Toolbox plugin as a replacement:

https://github.com/heathdutton/github-codespaces-jetbrains-toolbox

Codespaces appear in Toolbox and you can connect from there. Uses SSH under the hood.