Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Unity Accelerator connection failed

Discussion in 'Unity Accelerator' started by ChenySchmeling, Feb 7, 2020.

  1. ChenySchmeling

    ChenySchmeling

    Joined:
    Jan 24, 2017
    Posts:
    6
    Hello everyone.

    Looks like I can't connect to the Unity Accelerator and I don't know why.

    I've done these steps:
    1. Installed Unity 2019.3.0f6
    2. Installed the Unity Accelerator for Windows (Win10 64bits) from https://docs.unity3d.com/2019.3/Documentation/Manual/UnityAccelerator.html
    3. Got the IP and Port at the end of the installation (ex: localhost : port)
    4. Opened Unity with empty project
    5. Edit -> Preferences -> Cache Server (global) upload_2020-2-7_12-24-51.png
    6. Tried localhost and 127.0.0.1 and both shows "Connection failed"
    7. Checked the service if it was running. It was: upload_2020-2-7_12-25-52.png
    8. Disabled all firewall

    What I noticed is that when I open Unity it pops 02 errors:

    - Socket: bind failed, error: An attempt was made to access a socket in a way that is prohibited by access permissions. (10013)
    - Unable to join player connection multicast group.

    Anyone faced the same problem and found a solution?

    Best,
     
  2. bradunity

    bradunity

    Joined:
    Nov 12, 2013
    Posts:
    195
    @ChenySchmeling, in your picture of the settings, it appears you have not included the port number that the Accelerator is listening on (default choice is 10080): upload_2020-2-7_8-54-8.png

    This might be the problem. For example, if you are running the Accelerator on the same host as your Editor is running, you'd use something like localhost:10080 in that box.

    Additionally, there's no real benefit of using the Accelerator for a local Unity Editor outside of testing the functionality. The new Asset Import Pipeline now caches internally to achieve the same results (e.g. to make it painless to switch builds between platforms).
     
  3. ChenySchmeling

    ChenySchmeling

    Joined:
    Jan 24, 2017
    Posts:
    6
    @bradunity Thanks for the reply!

    I've went to another machine and opened Unity (same version) and tried as you said:
    upload_2020-2-7_14-14-31.png

    The pcs are in the same network and I can access the Accelerator machine remotely, share files, ping etc but the connection still fails.

    Any thoughts?
     
  4. bradunity

    bradunity

    Joined:
    Nov 12, 2013
    Posts:
    195
    Hmm, not sure. Another test you can try is to access the Accelerator's health endpoint. It's usually hosted on port 80, so often you can try something like http://192.168.0.69/api/agent-health (the actual port value is listed as the value of LastUsedHTTPPort found in the unity-accelerator.cfg file in the storage directory you chose, in case it couldn't listen on 80). You should also be able to access it from a browser running on the same machine using localhost.

    Might be worth a peek into the unity-accelerator.log file or the editor log file for more clues. Additionally, you can enable extra logging by editing the unity-accelerator.cfg and changing the Debug value to true and restarting the service.
     
  5. ChenySchmeling

    ChenySchmeling

    Joined:
    Jan 24, 2017
    Posts:
    6
    The health check also does not work, looks like the server did not compile correctly.

    By changing the Debug to true and checking the logs I could see some "SyntaxError" and "failed to execute". Should I post them here or send a PM?
     
  6. bradunity

    bradunity

    Joined:
    Nov 12, 2013
    Posts:
    195
    Sounds like whatever change you made to the file may not have been saved in a format the Accelerator can read. Possibly might be line endings since you're on windows, or perhaps you didn't follow the value with a comma? The app itself doesn't compile anything, it's a standard executable.
     
  7. lastcode

    lastcode

    Joined:
    Sep 3, 2012
    Posts:
    7
    Hello. When installing, uncheck the Asset pipeline v1 and it will work.
     
  8. Dorice

    Dorice

    Joined:
    Mar 3, 2020
    Posts:
    5
    I can see the unity-accelerator is listening 80 and 10080, and I can open 80 port in browser. But the check connection always fail on 10080 port.
     
  9. Dorice

    Dorice

    Joined:
    Mar 3, 2020
    Posts:
    5
    When I enter 80 port in the Default IP Address box, check connection is successful. But I think the right port should be 10080.
     
  10. Evorowy

    Evorowy

    Joined:
    Dec 27, 2018
    Posts:
    5
    Same problem here, from newest version of Unity (2019.4.7f1) it hangs out on :80, and on :10080 reports that "Connection failed" even though the accelerator instance is up and running. It was working previously when it first connects to :80 then I manually change :80 to :10080 and never click Check Connection again.
     
    Last edited: Aug 10, 2020
  11. gregoryh_unity

    gregoryh_unity

    Unity Technologies

    Joined:
    Oct 1, 2018
    Posts:
    50
    Thank you for the report -- I'm guessing you meant to type 2019.4.7f1? The accelerator is only supported from 2019.3 onward.
     
  12. Evorowy

    Evorowy

    Joined:
    Dec 27, 2018
    Posts:
    5
    Yes! Sorry for that. If there is anything that I can provide, please let me now!