Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-65667

PR_CONNECT_ABORTED_ERROR when saving a project

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None
    • 2.277.4
    • 2.289.2

      After system upgrade (Debian 10), my Jenkins was updated to 2.277.4 version.

      It's configured with HTTPS protocol and a certificate signed with a custom CA.
      I have followed this instruction: https://wiki.jenkins.io/pages/viewpage.action?pageId=135468777

      Sometimes, when I try to update a project configuration I catch a browser exception with "PR_CONNECT_ABORTED_ERROR" notification. The server didn't give me response after the POST.

      I use Firefox but I have the same problem with Chrome.

      With 2.277.2 version I had no problem. Because of this, I installed the backport to 2.277.2.

          [JENKINS-65667] PR_CONNECT_ABORTED_ERROR when saving a project

          Mark Waite added a comment -

          deafeningquiet if you're willing to run the Jenkins 2.289.2 release candidate, it includes Jetty 9.4.41. It was announced in the developer mailing list including a download link for the war file. It lists that it resolves JENKINS-65624. I would love to have confirmation that it also resolves this issue for you.

          Mark Waite added a comment - deafeningquiet if you're willing to run the Jenkins 2.289.2 release candidate, it includes Jetty 9.4.41. It was announced in the developer mailing list including a download link for the war file. It lists that it resolves JENKINS-65624 . I would love to have confirmation that it also resolves this issue for you.

          Matt added a comment -

          Oh, great news! Just found the download link for the RC. I will give it a go this afternoon and monitor if we continue seeing the issue and update here.

          Matt added a comment - Oh, great news! Just found the download link for the RC. I will give it a go this afternoon and monitor if we continue seeing the issue and update here.

          Matt added a comment -

          Unfortunately, I can confirm that I still receive the error when updating config files from Manage Jenkins > Managed Files.

          We have the latest 3.8.0 version installed for the Config File Provider for this. Would this require a plugin update as well?

          https://plugins.jenkins.io/config-file-provider/

          Interestingly enough, it seems this may only fail to save for some of our larger config files (~1700+ lines) as I've been able to successfully save for some shorter ones after some testing.

          Any logs that would be helpful from our instance to help troubleshoot?

           

          The jury is still out on if the RC build fixed saving changes to project settings.

          Matt added a comment - Unfortunately, I can confirm that I still receive the error when updating config files from Manage Jenkins > Managed Files. We have the latest 3.8.0 version installed for the Config File Provider for this. Would this require a plugin update as well? https://plugins.jenkins.io/config-file-provider/ Interestingly enough, it seems this may only fail to save for some of our larger config files (~1700+ lines) as I've been able to successfully save for some shorter ones after some testing. Any logs that would be helpful from our instance to help troubleshoot?   The jury is still out on if the RC build fixed saving changes to project settings.

          Mark Waite added a comment -

          I had problems with large forms with my Jenkins instance that is running behind an nginx reverse proxy. In that case, I had to adjust a configuration value in nginx that would allow the larger form size to be passed through nginx to Jenkins. I assumed from your description that you are not running behind a reverse proxy. Is my assumption correct?

          Mark Waite added a comment - I had problems with large forms with my Jenkins instance that is running behind an nginx reverse proxy. In that case, I had to adjust a configuration value in nginx that would allow the larger form size to be passed through nginx to Jenkins. I assumed from your description that you are not running behind a reverse proxy. Is my assumption correct?

          Matt added a comment -

          That's correct. The instance is also installed/running on Windows Server 2016.

          Matt added a comment - That's correct. The instance is also installed/running on Windows Server 2016.

          There is also an issue with large files in parameterized builds with file paramter. Upload files larger than approx. 20 KB results in PR_CONNECT_ABORTED_ERROR

          Torsten Boelting added a comment - There is also an issue with large files in parameterized builds with file paramter. Upload files larger than approx. 20 KB results in PR_CONNECT_ABORTED_ERROR

          We've installed LTS 2.289.2 yesterday and I can confirm that both errors (save config and upolad files) are fixed in this version.

          Torsten Boelting added a comment - We've installed LTS 2.289.2 yesterday and I can confirm that both errors (save config and upolad files) are fixed in this version.

          Mark Waite added a comment -

          torstenboelting thanks for reporting that 2.289.2 resolved your issue. deafeningquiet can you confirm that the final release of 2.289.2 resolved the issue for you as well?

          Mark Waite added a comment - torstenboelting thanks for reporting that 2.289.2 resolved your issue. deafeningquiet can you confirm that the final release of 2.289.2 resolved the issue for you as well?

          Mark Waite added a comment -

          Based on report from torstenboelting, one of the cases may be resolved by the upgrade of Jetty that is included in Winstone 5.18 that is included in Jenkins 2.289.2.

          Based on the comment from deafeningquiet, the Winstone 5.18 upgrade of Jetty may not be enough to resolve the case that he is seeing.

          Mark Waite added a comment - Based on report from torstenboelting , one of the cases may be resolved by the upgrade of Jetty that is included in Winstone 5.18 that is included in Jenkins 2.289.2. Based on the comment from deafeningquiet , the Winstone 5.18 upgrade of Jetty may not be enough to resolve the case that he is seeing.

          Matt added a comment -

          Hey Mark - I was finally able to upgrade our instance today. It looks like this latest build of 2.289.2 resolved the issue for me as well. During initial testing, I've been able to save our largest config file multiple times in a row. I've also been able to save changes to one of our larger job configs.

          Matt added a comment - Hey Mark - I was finally able to upgrade our instance today. It looks like this latest build of 2.289.2 resolved the issue for me as well. During initial testing, I've been able to save our largest config file multiple times in a row. I've also been able to save changes to one of our larger job configs.

            Unassigned Unassigned
            fra Francesco
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: