Please provide more details so that others can duplicate the problem that you are reporting.

I pressed the "Proceed" button in the console log today for the Jenkins 2.346.2 release build. It worked very well.

I created a Pipeline job with Jenkins 2.346.2 using the most recent releases of the Pipeline plugins and this job definition:

pipeline {
    agent any

    stages {
        stage('Hello') {
            steps {
                echo 'Hello World'
                input message: 'You say goodbye, I say hello', ok: 'Hello, hello'
                echo 'Goodbye World'
            }
        }
    }
}

I was able to click the "Hello, hello" button (proceed button with a custom name) in the build log and the job continued to completion.

I've been able to reproduce this issue on my development instance.
It happens if you contact via the wrong URL. I was using the default "http://localhost:8080/jenkins/" Jenkins URL configured in the global config. But I accessed the server via 127.0.0.1. The console is executing an XHR to the configured base URL instead of the origin which fails with a CORS error. The stage view is using the origin of the request (127.0.0.1) and succeeds. This error message is not shown unfortunately. Maybe JENKINS-45355 would help.

hickstein as far as I understand it, there are many places in Jenkins that rely on a correctly configured URL. That's why Jenkins reports "misconfigured proxy" and has help pages to guided users to access the service with the correct URL.

This problem is due to the wrong jenkins URL under the settings. We had the issue after assigning an elastic IP to the instance but not changing it under /manage/configure