Installation failure

Title: GpgOL/Web 0.9.2: add-in listed in Outlook on the web but never activates; loopback blocked by Edge Local Network Access by default

Environment

  • Gpg4win v5.1.1, GpgOL/Web client 0.9.2, manifest version 0.9.0.0
  • Windows 11 Enterprise build 26300.9457 Windows Feature Experience Pack 1000.26100.360.0, domain-managed Microsoft 365 tenant
  • Microsoft Edge 154 (Outlook on the web at https://outlook.cloud.microsoft) and New Outlook
  • Kleopatra holds a secret key matching the mailbox address

Summary

After resolving several setup issues, the GnuPG add-in is installed on the mailbox and listed in the in-message Apps panel of Outlook on the web, and its icon loads from the broker. However, clicking the add-in (or pinning it) does nothing: no request is made to localhost:5656, nothing is logged in the browser console, and the tray client continues to report “Web extension is unavailable”. The add-in never appears at all in New Outlook.

What works

  • Certificate setup completed: %LOCALAPPDATA%\Gpg4win\gpgol-web\tls contains certificate-key.pem, certificate.pem and root-ca.pem, and the local root CA is present in Cert:\CurrentUser\Root.
  • The broker listens on https://127.0.0.1:5656/, the native client connects over WebSocket and registers successfully.
  • The tray client shows “Proxy process is running” and “Proxy is connected”.

Issues found during setup

  1. “Broker disconnected” on first start. Immediately after certificate installation, the client reported the broker as disconnected. Fully closing the client (including the tray instance) and restarting it resolved this; the server did not appear to restart itself after the certificate was installed.

  2. “Copy manifest” produces a malformed Windows path. The path copied to the clipboard uses forward slashes and a double separator:
    C:/Users/<user>/AppData/Local/Gpg4win/gpgol-web/manifest//gpgol-web-manifest.xml
    This looks like the same path-joining issue seen previously for gpgol-web/tls//certificate-key.pem.

  3. Manifest references URLs that the broker does not serve (404):

    • https://localhost:5656/index.html?version=… (DesktopSettings/SourceLocation)
    • https://localhost:5656/assets/script.js (JSRuntime.Url); server log: "No such file or directory" ":/assets/script.js"

    All other manifest URLs return 200, including /home?version=… (used by Commands.Url, EventsRuntime.Url, the FunctionFile and the ShowTaskpane action) and all icons. I understand these two may be unused by New Outlook and Outlook on the web, but they may affect other clients.

  4. Edge Local Network Access blocks all loopback requests by default. With default settings, every request from Outlook to the broker failed, with this console error:

    Access to fetch at ‘https://localhost:5656/assets/logo.png’ from origin ‘https://outlook.office.com’ has been blocked by CORS policy: Permission was denied for this request to access the loopback address space.

    Requests from Outlook’s service worker failed in the same way. Adding the Outlook origins to the Edge policy LocalNetworkAccessAllowedForUrls resolved this for the icons:

    • https://outlook.office.com
    • https://outlook.cloud.microsoft (Outlook on the web now redirects here)

    After that change and a clean session (InPrivate, to avoid Outlook’s cached add-in list), the GnuPG tile showed its icon and both logo.png requests returned 200.

    I expect this to affect every organisation trying GpgOL/Web with current Edge, so it may be worth documenting. It is also unclear whether New Outlook (WebView2) honours this Edge policy at all.

Current blocker

With the add-in listed and its icon loading, clicking the tile in the in-message Apps panel (or the pinned button) produces:

  • no request to localhost:5656 in the Network panel (no home?version=… load, no WebSocket);
  • no related error or warning in the console, including at Verbose level;
  • no change in the tray client, which still reports “Web extension is unavailable”.

Removing and re-adding the manifest, and testing in a fresh InPrivate session, made no difference.

Questions

  1. Is there an additional step required for Outlook to open the task pane, for example a consent or trust step specific to custom add-ins served from localhost?
  2. Is this a known limitation of New Outlook or Outlook on the web with current Edge versions, and is there a recommended configuration (policies or origins) for enterprise deployments?
  3. Is there any diagnostic logging in the client or broker that would show whether Outlook attempts to contact it when the add-in is invoked?

I am happy to run further tests or provide logs.

Thanks for your very detailed report! Some preliminary answers:

“Broker disconnected” on first start.

I will investigate this.

“Copy manifest” produces a malformed Windows path.

True, the path is not normalized, but as you found out, it works nonetheless. Will be fixed in the next version.

Manifest references URLs that the broker does not serve (404)

Thanks for pointing this out. These are unused, but of course they should be removed from the manifest, too.

Edge Local Network Access blocks all loopback requests by default.

Yes. Chrome and Edge introduced this policy, earlier this year, and it is very unfortunate in our context, where we want to keep sensitive communication local. We have documented this - and a few further items - in our FAQ: FAQ on User Issues . Note that Outlook urls seem to change, occasionally, e.g. you may also need to whitelist https://outlook.office365.com . In general, I would suggest to make sure the default policy is set to “Ask”, while you are troubleshooting the installation.

Current blocker

What you should see is a task-pane opening, similar to this:

Is there an additional step required for Outlook to open the task pane, for example a consent or trust step specific to custom add-ins served from localhost?

Depending on your tenant configuration, newly installed Add-Ins may require administrator approval, but this should usually show as a message. It is also possible to limit Add-Ins to only a specific allowed set, and I do suspect this may be the problem in your case. (I will have to do some research on where, how this can be configured, myself, so I cannot give you detailed instructions, right now). Do other Add-Ins work as expected?

Is this a known limitation of New Outlook or Outlook on the web with current Edge versions, and is there a recommended configuration (policies or origins) for enterprise deployments?

Apart from the local network access problem, I am not aware of any such problem, current versions of Edge (and other mainline browsers such as Chrome and Firefox) are expected to work. Providing enterprise-centered configuration instructions is on our work list, but is currently still lacking.

Is there any diagnostic logging in the client or broker that would show whether Outlook attempts to contact it when the add-in is invoked?

You can control debug logging at Settings->Troubleshooting from the client’s status window. However, from the debugging you have already done, it seems the problem is that the Add-In is blocked in Outlook/the browser itself, so there is not anything to diagnose/log from the outside.

In summary, I do suspect, your tenant configuration includes a whitelist of Add-Ins, and will need to add GpgOL/Web to this list. One way to test this hypothesis is by trying to install the plugin in an external testing account (e.g. a personal outlook account; you will have to repeat the step of installing the manifest with that account, but you do not need a new TLS certificate).

Update: tenant add-in controls verified

To rule out tenant-side restrictions, I audited the Exchange Online add-in controls (read-only, via the ExchangeOnlineManagement module):

  • Get-OrganizationConfig: AppsForOfficeEnabled is True, so add-ins are enabled organisation-wide.
  • The mailbox uses the Default Role Assignment Policy, which has all three add-in roles enabled:
    • My Custom Apps: Enabled
    • My Marketplace Apps: Enabled
    • My ReadWriteMailbox Apps: Enabled (relevant, as the GnuPG manifest requests ReadWriteMailbox)
  • The organisation-deployed add-ins are standard Microsoft ones, with no restrictive scoping.

So Exchange is not blocking installation or activation, and I believe a tenant policy can be ruled out as the cause of the add-in being listed but never activating.

Next test in progress: I have removed the user-installed copy and deployed the same manifest through the Microsoft 365 admin centre (Integrated apps → Upload custom apps), assigned to my account only. I am waiting for it to propagate, and will report whether the admin-managed route behaves differently from the user-installed one.