This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 262437 - Unable to connect to the Plugin Portal because of Connection reset
Summary: Unable to connect to the Plugin Portal because of Connection reset
Status: RESOLVED DUPLICATE of bug 262432
Alias: None
Product: updatecenters
Classification: Unclassified
Component: Pluginportal (show other bugs)
Version: 8.1
Hardware: PC Windows 10 x64
: P2 normal (vote)
Assignee: Jiri Kovalsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-15 03:37 UTC by wilmar
Modified: 2016-06-15 06:35 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wilmar 2016-06-15 03:37:14 UTC
I have a direct Internet connection, no use proxy.

This message appear, only Plugin Portal is down for me.

"Check your proxy settings or try again later. The server may be unavailable at the moment. You may also want to make sure that your firewall is not blocking network traffic."

If I try to open this url in a web browser, the page not resolve correctly.
 http://plugins.netbeans.org/nbpluginportal/updates/8.1/catalog.xml.gz.

And if I check the status of the site, this is result:
http://www.downforeveryoneorjustme.com/plugins.netbeans.org/nbpluginportal/updates/8.1/catalog.xml.gz

"It's not just you! http://plugins.netbeans.org looks down from here."

Thank you in advance.

Info about installation:

Product Version: NetBeans IDE 8.1 (Build 201510222201)
Updates: NetBeans IDE is updated to version NetBeans 8.1 Patch 1
Java: 1.8.0_92; Java HotSpot(TM) 64-Bit Server VM 25.92-b14
Runtime: Java(TM) SE Runtime Environment 1.8.0_92-b14
System: Windows 10 version 10.0 running on amd64; Cp1252; es_CO (nb)
User directory: C:\Users\MyUser\AppData\Roaming\NetBeans\8.1
Cache directory: C:\Users\MyUser\AppData\Local\NetBeans\Cache\8.1
Comment 1 Jiri Kovalsky 2016-06-15 05:50:28 UTC
We are aware of this and working on it. Thanks for your report.
Comment 2 Jiri Kovalsky 2016-06-15 06:35:01 UTC
This is actually a duplicate of bug #262437.

*** This bug has been marked as a duplicate of bug 262432 ***