Search Unity

  1. The 2022.1 beta is now available for testing. To find out what's new, have a look at our 2022.1 beta blog post.
    Dismiss Notice

Cannot open Dashboard (WebGL + IIS workflow)

Discussion in 'Unity Accelerator' started by KamilDA, Sep 10, 2020.

  1. KamilDA

    KamilDA

    Joined:
    May 21, 2020
    Posts:
    208
    Hello,

    I noticed that I can no longer open my dashboard page after installing a local IIS web server alongside Unity's accelerator. I am getting a simple ERR_CONNECTION_REFUSED error. Otherwise, the accelerator appears to be working in Unity (connection successful with "localhost" as URL).

    "unity-accelerator dashboard url"
    returns: http://127.0.0.1:5678/dashboard/

    LastUsedIP / Port validates this and I have no website running on port 5678 in IIS. No firewall rules to block it, no VPN, no proxy. Local install, workstation configured with Windows 10. Did a DNS flush, no dice.

    Running Unity Accelerator v1.0.502+g903ad1c.

    Thanks for any help.
     
  2. gregoryh_unity

    gregoryh_unity

    Unity Technologies

    Joined:
    Oct 1, 2018
    Posts:
    50
    There should be no reason IIS and the unity-accelerator should conflict with each other. If Unity can connect, perhaps try using the port configured there. The accelerator, due to history, listens on two ports but it can handle http or the protobuf protocol the editor uses on either port. LastUsedHTTPPort and LastUsedProtobufPort should give the ports in use. If the other port works then 5678 is being blocked by "something" but I don't know what.
     
    KamilDA likes this.
  3. KamilDA

    KamilDA

    Joined:
    May 21, 2020
    Posts:
    208
    I was surprised by this as well. I suspect IIS as I know Unity Accelerator dashboard was working after initial install. I tried other ports with no success too.

    LastUsedHTTPPort and LastUsedProtobufPort return 5678.

    So I tried using the port that Unity uses, which is 10080, and voila! It works. I am really confused as to why the config file returns 5678 for the dashboard if it doesn't use it.

    Oh well, thanks!
     
  4. gregoryh_unity

    gregoryh_unity

    Unity Technologies

    Joined:
    Oct 1, 2018
    Posts:
    50
    Oh, it would definitely use 5678 LastUsedHTTPPort for the dashboard url. In much older versions, the dashboard would have only been available on that port. But these days the accelerator will recognize if an http request is being made over the Unity protobuf port and react as if it were the http port.

    If you have it all "working" you might not want to touch anything ;) but --- you could try shutting the accelerator off, running "unity-accelerator config set LastUsedHTTPPort 0" to clear the port it had picked from before, and start the accelerator back up. It will likely pick a new, available port and see if that is cleaner.

    But is weird if both ports gave 5678 earlier. "unity-accelerator config get LastUsedProtobufPort" should definitely give a different value than "unity-accelerator config get LastUsedHTTPPort" -- you can also just view/edit the unity-accelerator.cfg directly.
     
    KamilDA likes this.
unityunity