RFC Server errors block SSL certificate installations

2 posts, 0 answers
  1. Sterling
    Sterling avatar
    2 posts
    Member since:
    Sep 2018

    Posted 06 Sep 2018 Link to this post

    The beginning of the problem:


    For months my computer would take about five minutes for HTTPS connections to function. As a result, Skype could not connect during this time and any HTTPS web requests would be stuck in "Establishing Secure Connection" during this time. I finally fixed the issue by removing all the DO_NOT_TRUST_FiddlerRoot certificates that I found in the "Personal" store.


    Since then, fiddler is unable to decrypt HTTPS requests properly. Instead, Chrome displays a Privacy Error. I have seen other people on this forum with this problem fix the issue by upgrading Fiddler, checking a dll, or trusting the root certificate. On these points:

    My Fiddler Web Debugger is v5.0.20182.28034 for .NET 4.6.1 (Running ELEVATED)
    I do not understand what DLL I should be looking for in order to ensure that I have the right certificate authority. I have the CertEnroll engine.
    In Tools > Options > HTTPS > Action:

    • I have never noticed a change when I choose "Reset All Certificates".
    • "Trust Root Certificate" does not work, the log shoes an error message: "The RFC server is unavailable"
    • I am able to "Export Root Certificate to Desktop" and install these certificates in the "Personal" store, but not "Trusted Certificate authorities".

    As far as I can see, the basic problem is a permissions issue:

    • I can't delete a FiddlerRoot certificate (a certificate that I do not believe is the current root) from Trusted Certificate Authorities. (error: RFC server)
    • I cannot install a new root into "Trusted Certificate authorities" (error: store is read only, or did not open properly)

    Any ideas on what permissions specifically are neededfor these RFC server error messages to be fixed?


    Appreciate your help.

  2. Sterling
    Sterling avatar
    2 posts
    Member since:
    Sep 2018

    Posted 06 Sep 2018 in reply to Sterling Link to this post

    Correction: 'The RPC server is unavailable' (not RFC)
Back to Top