MAguero641070 (Community Member) asked a question.

September 17, 2020 at 8:23 PM
I have a veracode scan integration done on my cloudbees pipeline: Error writing request body to server. I just dismissed firewall blocks

[20.09.17 XX:XX:XX] Error writing request body to server

 

 

Error- Returned code from wrapper:2

  • 5 answers
  • 1.01K views

  • Jason M., Veracode Support (Veracode)

    It seems that the issue was looked at by Veracode Support and it was caused by using CloudBees Jenkins Enterprise and was resolved by two ways. 

     

    • First support wanted to rule out the Cloudbees server by executing from an on-premise system using the Java wrapper, or HMAC file with CLI with aid from this Help Article.
    • Second was that the engineers found out that connections were being blocked in the Firewall to the Veracode domain and could be resolved by modifying the rule, to base it on their FQDN instead of the URL.

     

    Jason

    Community Support Engineer

    Expand Post
    Selected as Best

  • Jason M., Veracode Support (Veracode)

    Hello @MAguero641070 (Community Member)​ ,

     

    I would check the basics to make sure everything is setup properly like the credentials are valid, is there a proxy in the network path, etc. Also, what were you trying to do exactly and what were the parameters to the wrapper?

     

    Jason

    Community Support Engineer

    Expand Post

    • MAguero641070 (Community Member)

      Hello @Jason M., Veracode Support (Veracode)​ 

      These verifications are performed and changed by the service user, there is no proxy on the network, there is no firewall blocking, etc. the plugin parameters are the same that I have been using for a year.

       

      Warm regards!

       

      Expand Post

      • Jason M., Veracode Support (Veracode)

        Hello @MAguero641070 (Community Member)​ ,

         

        I am going to need more information if I am going to assist you. Can you please let me know which wrapper are you using? What action are you attempting to do? Any other additional information would be most helpful.

         

        Jason

        Community Support Engineer

        Expand Post

      • MAguero641070 (Community Member)

        Jason, thank you for your prompt reply! Sorry for my somewhat ambiguous answer. This is the java wrapper log, which is the one we use with the CloudBees plugin.

        Invoking the following command in remote workspace:

        $ java -jar /app/jenkins/int-master01-agent/veracode-jenkins-plugin/VeracodeJavaAPI.jar -action UploadAndScan -vid **** -vkey ******** -scantimeout 180 -appname XXXXXXX -createprofile false -criticality VeryHigh -sandboxname XXXX-XXXXXXX-int_XXXXXX-web -createsandbox true -version XXXXXXX-web_1.0.5_1600698348837.zip -autoscan true -maxretrycount 5 -filepath /app/jenkins/int-master01-agent/workspace/XXXXXXX-int/XXXX-XXXX-int-XXXXXXX-web2int/XXXXXX-web_1.0.5_1600698348837.zip -useragent "VeracodeJenkinsPlugin/20.2.6.1 (Jenkins/2.235.2.3; Java/1.8.0_242)"

         

         

        Expand Post

      • Jason M., Veracode Support (Veracode)

        It seems that the issue was looked at by Veracode Support and it was caused by using CloudBees Jenkins Enterprise and was resolved by two ways. 

         

        • First support wanted to rule out the Cloudbees server by executing from an on-premise system using the Java wrapper, or HMAC file with CLI with aid from this Help Article.
        • Second was that the engineers found out that connections were being blocked in the Firewall to the Veracode domain and could be resolved by modifying the rule, to base it on their FQDN instead of the URL.

         

        Jason

        Community Support Engineer

        Expand Post
        Selected as Best

Topics (2)

No articles found
Loading

Ask the Community

Get answers, share a use case, discuss your favorite features, or get input from the community.