The easiest way to work around this is if you have read-only access to the
repository over http. If you do, then set that read-only HTTP URL as your
Path in the repository configuration, and set your HTTPS URL as the Mirror
If not, then it gets a little more tricky. Essentially (and this may vary a
bit between installs on different distros), you'll need to sudo to the
Apache user, using its home directory and environment variables, and then do
an svn checkout of your repository somewhere. This should store the
certificate where the Apache user can get to it.
We're looking into making this work in a much smoother manner in a future
release without having to use any workarounds.
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com
On Tue, Aug 25, 2009 at 3:16 AM, Pubudu Rathnayake <dmpub...@gmail.com>wrote:
> when i tried to make a new review request ,i got the following message,
> HTTPS certificate not accepted. Please ensure that the proper certificate
> exists in ~/.subversion/auth for the user that reviewboard is running as.
> Any advice how to diagnose it is highly appreciated.
You received this message because you are subscribed to the Google Groups
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to
For more options, visit this group at