Launch Windows agent with Linux (RHEL) controller is NOT working

Using Jenkins Ask a question
1

Hi, I am unable to see disable workdir and internal data directory option in launch agent by connecting it to the controller while launching windows node on jenkins. I am trying it from 2 days and unable to connect it. Also, from my windows node I’m getting an error message as similar to the below:

C:\jenkins\remote-root-dir>java -jar agent.jar -url http://13.232.226.131:8080/ -secret 47fd45b7cea893a34f9ea685fcce63d2c134d3c7629a0d01f77df47ae9db599d -name "Windows_agent" -workDir "C:\jenkins\remote-root-dir"
Feb 29, 2024 4:14:55 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using C:\jenkins\remote-root-dir\remoting as a remoting work directory
Feb 29, 2024 4:14:55 PM org.jenkinsci.remoting.engine.WorkDirManager setupLogging
INFO: Both error and output logs will be printed to C:\jenkins\remote-root-dir\remoting
Feb 29, 2024 4:14:55 PM hudson.remoting.Launcher createEngine
INFO: Setting up agent: Windows_agent
Feb 29, 2024 4:14:55 PM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 3206.vb_15dcf73f6a_9
Feb 29, 2024 4:14:55 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using C:\jenkins\remote-root-dir\remoting as a remoting work directory
Feb 29, 2024 4:14:56 PM hudson.remoting.Launcher$CuiListener status
INFO: Locating server among [http://13.232.226.131:8080/]
Feb 29, 2024 4:14:56 PM hudson.remoting.Launcher$CuiListener status
INFO: Could not locate server among [http://13.232.226.131:8080/]; waiting 10 seconds before retry
java.io.IOException: http://13.232.226.131:8080/tcpSlaveAgentListener/ is invalid: 404 Not Found
        at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:222)
        at hudson.remoting.Engine.innerRun(Engine.java:809)
        at hudson.remoting.Engine.run(Engine.java:563)
2
  1. Verify the Jenkins controller URL: Make sure that the Jenkins controller is running and accessible at the URL http://13.232.226.131:8080/. You can do this by opening the URL in a web browser.
  2. Check the network connection: Ensure that the machine running the Jenkins agent has a stable network connection and can reach the Jenkins controller. You can test this by pinging the IP address of the Jenkins controller from the agent machine.
  3. Check the Jenkins controller configuration: Make sure that the Jenkins controller is correctly configured to accept connections from agents. This is usually done in the “Configure Global Security” section of the Jenkins controller settings.
  4. Update the Jenkins agent: If you’re using an older version of the Jenkins agent, it might not be compatible with the Jenkins controller. Try updating the Jenkins agent to the latest version.