Enable HTTP/2 on Nginx

  • @monsen,
    Can let us know the result, if you use it?


    Add the http2 keywords to your virtualhost configuration.


    Enabling really is this simple, just change your current ssl-line from this:

    Code
    server {
      listen        443 ssl;
      ...
    }to this:
    
    
    server {
      listen        443 ssl http2;
      ...
    }

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • @tinh_x7
    If i am really doing this i will let you know.
    Not sure if i should take the step right now. Every configuration outside of what is intended by OMV seems to be a pain in the ****
    (I actually like the idea of having a frontend to administer my NAS but i am unsure about the flexiblity of it until here.)


    I worry about the long-term issues resulting out of these manual changes. When the next updates come everything might go to pieces. Also i am still in the process of doing the base setup for me, so doing a lot in parallel.....


    besides, and about owncloud:
    What is really anyoing me about owncloud is the performance. It got a lot better with some tweaks but still is not good.
    So either i will try or might get rid of it.

  • OwnCloud is working fine for me.
    Just setup the memcache also help it too.


    I hope somebody in here can confirm whether http/2 is working or not for OMV, owncloud, Plex....

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    Einmal editiert, zuletzt von tinh_x7 ()

  • After some more screwing here and there here is my opinion: the owncloud idea ist good, the implementation is crap. I got enough of it! Hopefully Future Versions are ging to be better. I will then try again.


    I am happy with OMV though. I got a Little angry trying to get owncloud to run but figured it is not OMV causing the main issues.
    i will try to replace owncloud with other Services.
    therefore i am not trying to get http2 to run for now

  • We need a newer version of nginx. I have known this for some time. I wish Volker would upgrade the version even before we get to OMV 3.


    @votdev


    But Debian repos are to blame.


    • Offizieller Beitrag

    Pitty, omv3 still running with nginx 1.6.2 two years later

    Check your facts... OMV doesn't determine which version is used. OMV 3.x is Debian 8. So, it uses whatever Debian 8 has available. Looking here, 1.10 is in jessie-backports. And you have plenty of other options like using the docker plugin. There is no reason you have to use OMV's nginx. You could also use OMV 4.x

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!