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

          Francesco created issue -

          Same here.

          2.277.2 works fine. Issue appears with 2.277.3.

          Nearly every edit and save of a job config that lasts more then 10 seconds results in PR_CONNECT_ABORTED_ERROR. Under 10 seconds it appears sporadically.
          After refreshing the page 2 or 3 times the config is saved.

          Running on RHEL7. Firefox 78.6.1esr and 88.0.1, Chrome 90.0.4430.212

          Torsten Boelting added a comment - Same here. 2.277.2 works fine. Issue appears with 2.277.3. Nearly every edit and save of a job config that lasts more then 10 seconds results in PR_CONNECT_ABORTED_ERROR. Under 10 seconds it appears sporadically. After refreshing the page 2 or 3 times the config is saved. Running on RHEL7. Firefox 78.6.1esr and 88.0.1, Chrome 90.0.4430.212

          Mark Waite added a comment -

          https://www.jenkins.io/changelog-stable/#v2.277.3 says that the change was to update Jetty from 9.4.38.v20210224 to 9.4.39.v20210325 for bug fixes and enhancements. You might check the Jetty team to see if there are known issues in 9.4.39 with SSL termination in the Java process. torstenboelting is your instance also terminating SSL in the Java process like fra is doing?

          If you're using the Docker image, there was an additional implicit change in 2.277.4 to use Java 8u292 for Java 8 and JDK 11.0.11 for Java 11. In 2.277.2 and 2.277.3 we used Java 8u282 for Java 8 and JDK 11.0.10 for Java 11.

          Mark Waite added a comment - https://www.jenkins.io/changelog-stable/#v2.277.3 says that the change was to update Jetty from 9.4.38.v20210224 to 9.4.39.v20210325 for bug fixes and enhancements. You might check the Jetty team to see if there are known issues in 9.4.39 with SSL termination in the Java process. torstenboelting is your instance also terminating SSL in the Java process like fra is doing? If you're using the Docker image, there was an additional implicit change in 2.277.4 to use Java 8u292 for Java 8 and JDK 11.0.11 for Java 11. In 2.277.2 and 2.277.3 we used Java 8u282 for Java 8 and JDK 11.0.10 for Java 11.

          markewaite Instance is running with SSL and Java (OpenJDK 1.8.0_242)

          Torsten Boelting added a comment - markewaite Instance is running with SSL and Java (OpenJDK 1.8.0_242)

          John added a comment -

          I am seeing this issue as well when I try to update (PUSH?) a job's instructions.

          An observation is that it seems that after a reboot of the server the first submission will work but not any after that.

          Running our Jenkins 2.289.1 Windows 2019 server & openjdk-11+28_windows-x64.

          I have enabled TLS 1.2  and on my browser as well.

          John added a comment - I am seeing this issue as well when I try to update (PUSH?) a job's instructions. An observation is that it seems that after a reboot of the server the first submission will work but not any after that. Running our Jenkins 2.289.1 Windows 2019 server & openjdk-11+28_windows-x64. I have enabled TLS 1.2  and on my browser as well.

          Matt added a comment -

          Also having the same issue updating job configurations or updating managed/config files.

          Started for me when I updated to 2.289.1. Unfortunately, didn't notice until after I had removed the server snapshot to easily revert and don't have file-level backups of our Jenkins config. Lesson learned.

          I tried downgrading to 2.277.2 as suggested above. While it did fix the problem (lending credence that this may be in the Jetty update after that version), I ran into too many plugin dependency issues to stay there since there doesn't seem to be an easy way to resolve those on a downgrade.

          As a workaround I ended up re-enabling access to our instance over http and updating the Jenkins URL setting in Manage Jenkins > Configure System to reflect http instead of https.

          Not ideal having to auth over http now, but at least this allows saving of configurations until this is fixed.

          Matt added a comment - Also having the same issue updating job configurations or updating managed/config files. Started for me when I updated to 2.289.1. Unfortunately, didn't notice until after I had removed the server snapshot to easily revert and don't have file-level backups of our Jenkins config. Lesson learned. I tried downgrading to 2.277.2 as suggested above. While it did fix the problem (lending credence that this may be in the Jetty update after that version), I ran into too many plugin dependency issues to stay there since there doesn't seem to be an easy way to resolve those on a downgrade. As a workaround I ended up re-enabling access to our instance over http and updating the Jenkins URL setting in Manage Jenkins > Configure System to reflect http instead of https. Not ideal having to auth over http now, but at least this allows saving of configurations until this is fixed.

          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?

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

              Created:
              Updated:
              Resolved: