Opened 3 years ago

Last modified 3 years ago

#2146 open defect

Ensure proxy tunnel is active before checking for plugin updates after major i2p update

Reported by: Reportage Owned by:
Priority: minor Milestone: 0.9.35
Component: router/update Version: 0.9.32
Keywords: plugins, updater, proxy check Cc:
Parent Tickets: Sensitive: no


There should be a check to ensure that the http proxy tunnel is up after a major router update (or a delay before checking?), otherwise an error will appear in the sidepanel indicating that the plugin check has failed because the proxy is not reachable, which can happen on slower systems or where bandwidth is constrained. Alternatively, if the proxy is unreachable, provide a manual "Check for plugin updates" button underneath the sidebar error.


Change History (2)

comment:1 Changed 3 years ago by zzz

Milestone: undecided0.9.35
Status: newopen

Yeah we just have a delay in there now. It actually displays 'checking for updates' during the delay so it's not completely honest.

We don't have a mechanism now for ensuring the proxy is ready (we have PortMapper? for the registration but that doesn't ensure the tunnels are ready). The router doesn't really know anything about the specific functions of the clients. But we need it for Tails #1697 so it will be easier after that.

Another button on the side bar might be helpful but more buttons over there are messy both for UI and implementation. Not sure.

comment:2 Changed 3 years ago by Reportage

As a workaround, a couple of ideas:

  • ping a hard-coded .i2p domain at intervals and wait for success before attempting update
  • if plugin update check fails on first try, repeat a couple of times at 5 minute intervals before publishing message to sidebar

If another sidebar button is more clutter than needed, link to the plugins page in the error message?
eg: "Plugin check failed. To manually check for updates, see the plugins page."

Note: See TracTickets for help on using tickets.