Closed Bug 564360 Opened 15 years ago Closed 15 years ago

Trying to add this addon "Weave" which I installed on my laptop using the same version of firefox but now on my home PC I am getting the error below.

Categories

(Firefox :: General, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: UNTGuy82, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729) I am getting this error when trying to install "Weave" "Firefox could not install the file at https://addons.mozilla.org/en-US/firefox/downloads/latest/10868/addon-10868-latest.xpi?src=search because: Unexpected installation error Review the Error Console log for more details. -203" So I tried to even update my current addons and the same thing on all of them. Reproducible: Always Steps to Reproduce: 1.Go to https://addons.mozilla.org/en-US/firefox/search?q=weave&cat=all 2.Click on the link to install 3. wait for it to install when the error pops up Actual Results: I get the error "Firefox could not install the file at https://addons.mozilla.org/en-US/firefox/downloads/latest/10868/addon-10868-latest.xpi?src=search because: Unexpected installation error Review the Error Console log for more details. -203" Expected Results: For there to not have been an error and it would have installed the first time. Default Theme
Yeah I tried using the support before but got this " Repairs in Progress The service you’re looking for is unavailable at the moment. We’ll be back up and running again before long, so please try again soon. Thanks for your patience!" So I thought I would try my luck here. Thanks anyways.
wait until the planned outage is over ?
obviously I will have to. Thank you for that.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.