Search Unity

  1. Unity 6 Preview is now available. To find out what's new, have a look at our Unity 6 Preview blog post.
    Dismiss Notice
  2. Unity is excited to announce that we will be collaborating with TheXPlace for a summer game jam from June 13 - June 19. Learn more.
    Dismiss Notice

Question 0 mention of encryption certs - what to do?

Discussion in 'Unity Accelerator' started by MrLucid72, Nov 10, 2020.

  1. MrLucid72

    MrLucid72

    Joined:
    Jan 12, 2016
    Posts:
    1,005
    These docs are super lacking. What to do with the certs and such for self-hosting? I've only used certbot with LetsEncrypt with Nginx. How to handle this? Surprised there's no integrated app to do this for you that comes with Accelerator.

    There's a bug with setup, too:
    If you setup with no encryption, it still tries to serve an https page (http will fail).

    PS: You guys also have 2 download bugs:
    https://forum.unity.com/threads/how...structions-are-dated-and-link-broken.1002790/
     
  2. gregoryh_unity

    gregoryh_unity

    Unity Technologies

    Joined:
    Oct 1, 2018
    Posts:
    50
    Currently the Accelerator really only uses TLS with the Collaborate source code caching, and there the certificate handling is all done automatically (and is backed by LetsEncrypt as well). For the Asset Pipeline V2 caching, there is early support for TLS, but there is no auth[nz] between the Editor and Accelerator right now, so it's a fairly odd story at the moment -- this will get better in the future.

    For now, if you are using only Asset Pipeline V2 caching, I'd recommend not running the Accelerator with TLS and just restricting access via networking, e.g. completely closed internal network or a vpn setup.

    For the download bugs and docs pages, I'll notify the right people handling those pages to get them updated. Definitely appreciate the bug reports.
     
    MrLucid72 likes this.
  3. MrLucid72

    MrLucid72

    Joined:
    Jan 12, 2016
    Posts:
    1,005
    I would also recommend you guys go to your GitHub cache server README and have a bold/red warning at the top that this is deprecated. I spent a long time trying to set this up, only to find it was incompatible. I originally found it from a blog post or Reddit at the top of Google.

    Thanks for the tips/updates