4457: Ubuntu: SSL: CERTIFICATE_VERIFY_FAILED

cantrianbear 
What version are you running?


2.5.6.1


What's the URL of the page containing the problem?




What steps will reproduce the problem?


    

  1. Run ReviewBoard Ubuntu and have repo with an unsecure SSL session (unverified: self signed certificate)
    2. 

  2. Now try 'rbt post <revnum>'
    3. 

  3. You get asked username and password and then I get 'ERROR: Error validating diff\n pathirrelevant/someProject.vcxproj: The file was not found in the repository. (HTTP 400, API Error 207)
    4. 





What is the expected output? What do you see instead?


Posting a new diff should work, but I get error messages every time and the repository path is correct.


What operating system are you using? What browser?


Reviewboard on latest Ubuntu release and rb-tools on Windows Server 2012


Please provide any additional information below.


In the Reviewboard log file, I see the following:

2016-08-25 13:36:39,083 - ERROR -  - Unexpected error fetching file from https:\

//ip:8181/path/\

path/someProject.vcxproj: <urlopen error [SSL: \

CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)>

2016-08-25 13:36:39,083 - INFO -  - Fetching file from https://ip:81\

81/pathirrelevent/someProject.vcxproj

2016-08-25 13:36:39,102 - ERROR -  - Unexpected error fetching file from https:\

//ip:8181/path/path.../someProject.vcxproj: <urlopen error\

 [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)>
#1 cantrianbear 
I also tried 'rbt post --disable-ssl-verification', but I still get the same error.
#2 jamie
  • +Release-2.5.x
david
#3 david 
What version control system? Looks like SVN? If so, are you using the PySVN or Subvertpy backend?
  • -New
    +NeedInfo
berquist
#4 berquist 
I had this problem as well, with Ubuntu 18.04 and Review Board 3.0.20:


>>> Error data: {'stat': 'fail', 'err': {'msg': "Unable to connect to a repository at URL 'https://remote.com/svnroot/repo/branches/rdm2/include/qinks_main.h'\nServer SSL certificate verification failed: issuer is not trusted", 'code': 224}}



and the problem was that the remote's certificate had expired and been updated, so command-line Subversion usage worked, but Review Board didn't know about the updated certificate. I had to go to the Admin panel, click "Repositories", click on the offending repository, save, and accept the new certificate.


Is there a way to do that from the CLI, rather than the Admin panel?
david
#5 david
  • -NeedInfo
    +SetupIssue
  • -Release-2.5.x