Search Issue Tracker

Fixed in 2018.3.X

Fixed in 2018.2.X

Votes

1

Found in

Issue ID

1023056

Regression

No

[Linux] 2018.1.0b13 Cannot connect to Unity Package Manager local server while on a closed network

Packman

-

Machine having local network access but no global internet access cannot connect to Packman Server.

Alternative OS reproduction:

(alt repro 1) If on WindowsOS, the user can introduce 100% packet loss which will generate this issue as well.
(alt repro 2) If on WindowsOS, using a closed network (user is connected to a wifi router that is disconnected from the network)
Log in to vote on this issue

Comments (5)

  1. dhresearchlabo

    Aug 08, 2025 03:56

    Buy2cbonline.com - @Buy2cbonline.com/shop/ | your #1 source for top quality premium RC's research chemicals like 2cb powder 2fdck (2-FDCK) 3cmc crystal meth 4mmc eutylone mephedrone ketamine Ephedrine hcl powder A-pvp etizolam bromazolam alprazolam powder Mdphp freebase Coke and more .

  2. gmatthews

    Jul 18, 2018 01:23

    I had this error, and changed from .NET 3.5 to .NET 4.x in Unity, and the error seemed to go away.

  3. bhramunity

    Jun 08, 2018 20:14

    When we are not sign in to my account inside unity.

  4. bhramunity

    Jun 08, 2018 20:04

    it dos'nt work with unity 2018.1 of2 either and says can not connect with package manager local server in the console .

  5. bhramunity

    Jun 08, 2018 20:04

    it dos'nt work with unity 2018.1 of2 either and says can not connect with package manager local server in the console .

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues