# Nextcloud - Memories HTTP/2 or HTTP/3 is strongly recommended (http/1.1 detected) + Nginx

**URL:** <https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753>\
**Category:** Troubleshooting\
**Created:** [2 May 2023 08:58 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753 "2023-05-02T08:58:37Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Isti6github](https://dietpi.com/forum/user_avatar/dietpi.com/isti6github/32/3650_2.png) [@Isti6github](https://dietpi.com/forum/u/Isti6github)\
**Post date:** [2 May 2023 08:58 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/1 "2023-05-02T08:58:38Z")

</div>

### Creating a bug report/issue

Nextcloud - Memories HTTP/2 or HTTP/3 is strongly recommended (http/1.1 detected) + Nginx

#### Required Information

- DietPi version |  
G\_DIETPI\_VERSION\_CORE=8  
G\_DIETPI\_VERSION\_SUB=16  
G\_DIETPI\_VERSION\_RC=2  
G\_GITBRANCH=‘master’  
G\_GITOWNER=‘MichaIng’  
G\_LIVE\_PATCH\_STATUS[0]=‘not applicable’

- Distro version | bullseye

- Kernel version | Linux DietPi 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86\_64 GNU/Linux

- Architecture | amd64

- SBC model | Intel Compute stick (4gb ram) Native PC (x86\_64)

- Power supply used | (EG: 5V 1A RAVpower)

- SD card used | (EG: SanDisk ultra)

#### Additional Information (if applicable)

- Software title | Nextcloud - Memories app
- Was the software title installed freshly or updated/migrated? Freshly
- Can this issue be replicated on a fresh installation of DietPi? Yes  
 ← If you sent a “dietpi-bugreport”, please paste the ID here → 
- Bug report ID | `echo $G_HW_UUID`

#### Steps to reproduce

1. Install Memories app in nextcloud app store
2. Check administration settings (Memories)

#### Expected behaviour

- Everything green

#### Actual behaviour

- one warning: HTTP/2 or HTTP/3 is strongly recommended (http/1.1 detected)

#### Request

- How I can update HTTP protocol? Is it possible update with HTTP? (Not just with HTTPS) I use HTTP connection becouse I need local network connection too.

- I have one more question: Is it possible to use SSL/HTTPS in local network? My router dosen’t manage NAT.

---

<div class="post-metadata">

**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\
**Post date:** [2 May 2023 09:11 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/2 "2023-05-02T09:11:28Z")

</div>

> [@Isti6github](#):
>
> How I can update HTTP protocol? Is it possible update with HTTP? (Not just with HTTPS) I use HTTP connection becouse I need local network connection too.

What webserver do you use?

> [@Isti6github](#):
>
> I have one more question: Is it possible to use SSL/HTTPS in local network? My router dosen’t manage NAT.

SSL works on domains, so you would need to set up a domain in your local network. But why would you need SSL in LAN?

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [2 May 2023 09:17 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/3 "2023-05-02T09:17:01Z")

</div>

> [@Isti6github](#):
>
> I have one more question: Is it possible to use SSL/HTTPS in local network? My router dosen’t manage NAT.

Question is if you like to access your NC from intern only or as well from external?

---

<div class="post-metadata">

**Author:** ![Isti6github](https://dietpi.com/forum/user_avatar/dietpi.com/isti6github/32/3650_2.png) [@Isti6github](https://dietpi.com/forum/u/Isti6github)\
**Post date:** [2 May 2023 10:16 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/4 "2023-05-02T10:16:16Z")

</div>

Both, internal and external

---

<div class="post-metadata">

**Author:** ![Isti6github](https://dietpi.com/forum/user_avatar/dietpi.com/isti6github/32/3650_2.png) [@Isti6github](https://dietpi.com/forum/u/Isti6github)\
**Post date:** [2 May 2023 10:16 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/5 "2023-05-02T10:16:50Z")

</div>

because, I want to use 1 server addres to connect with mobile app and browser

---

<div class="post-metadata">

**Author:** ![Isti6github](https://dietpi.com/forum/user_avatar/dietpi.com/isti6github/32/3650_2.png) [@Isti6github](https://dietpi.com/forum/u/Isti6github)\
**Post date:** [2 May 2023 10:18 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/6 "2023-05-02T10:18:05Z")

</div>

I use Nginx, I installed everithing with dietpi-software

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [2 May 2023 13:23 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/7 "2023-05-02T13:23:09Z")

</div>

> [@Isti6github](#):
>
> HTTP/2 or HTTP/3 is strongly recommended (http/1.1 detected)

Where did you see that error message? With NC?

> [@Isti6github](#):
>
> Is it possible to use SSL/HTTPS in local network? My router dosen’t manage NAT.

Do you mean your router is not able to handle NAT Loopback? If not, you would have a challenge to access your DDNS from inside your local network. From external, there would be no issue to access NC using DDNS + https. However from internal, some other workarounds needed to manipulate DNS request inside your network.

Depending on actual situation we could move ahead step by step to activate HTTPS, DDNS and HTTP/2

---

<div class="post-metadata">

**Author:** ![Isti6github](https://dietpi.com/forum/user_avatar/dietpi.com/isti6github/32/3650_2.png) [@Isti6github](https://dietpi.com/forum/u/Isti6github)\
**Post date:** [2 May 2023 13:40 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/8 "2023-05-02T13:40:11Z")

</div>

> [@Joulinar](#):
>
> Where did you see that error message? With NC?

No, this message get from admin page of Memories at Performance tab (based on my information, this can speed up my APP)

> [@Joulinar](#):
>
> Do you mean your router is not able to handle NAT Loopback? If not, you would have a challenge to access your DDNS from inside your local network. From external, there would be no issue to access NC using DDNS + https. However from internal, some other workarounds needed to manipulate DNS request inside your network.

Yes, in that case I have HTTPS with Let’snncript and DDNS, I just want to speed up my performance with HTML/2 or HTML/3

 ![image](https://dietpi.com/forum/uploads/default/original/2X/7/79e02c222885e74e53274647777346bea3d2f984.png)

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [2 May 2023 13:47 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/9 "2023-05-02T13:47:10Z")

</div>

to enable HTTPS/2, you would need to adjust `/etc/nginx/sites-available/default`

Based on [Step-by-Step Guide: How to Enable HTTP/2 on Nginx](https://cheapsslsecurity.com/p/how-to-enable-http-2-on-nginx/) , you can add `http2` configuration within the SSL part. Should looks like this

```auto
    listen [::]:443 ssl http2 ipv6only=on; # managed by Certbot
    listen 443 ssl http2; # managed by Certbot

```

Tested on my demo system with Memories  
 ![image](https://dietpi.com/forum/uploads/default/original/2X/c/c0fc389c8e28caff0beac806402389379e93192f.png)

---

<div class="post-metadata">

**Author:** ![Isti6github](https://dietpi.com/forum/user_avatar/dietpi.com/isti6github/32/3650_2.png) [@Isti6github](https://dietpi.com/forum/u/Isti6github)\
**Post date:** [3 May 2023 06:27 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/10 "2023-05-03T06:27:09Z")

</div>

This is strange, I updated, but the message is same…  
I reboot-ed the system to and I used

> systemctl reload nginx.service

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [3 May 2023 06:44 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/11 "2023-05-03T06:44:53Z")

</div>

can you share your configuration file? Did you try different browser and/cleared cache?

---

<div class="post-metadata">

**Author:** ![Isti6github](https://dietpi.com/forum/user_avatar/dietpi.com/isti6github/32/3650_2.png) [@Isti6github](https://dietpi.com/forum/u/Isti6github)\
**Post date:** [3 May 2023 08:17 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/12 "2023-05-03T08:17:26Z")

</div>

I tried, chrome and edge with cleared cache and I added the html2 to port80 too and after that everithings good.

Thanks for your help!

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [3 May 2023 08:25 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/13 "2023-05-03T08:25:29Z")

</div>

> [@Isti6github](#):
>
> I added the html2 to port80 too

usually this should not be needed if you activate redirect from 80 to 443.

---

<div class="post-metadata">

**Author:** ![Isti6github](https://dietpi.com/forum/user_avatar/dietpi.com/isti6github/32/3650_2.png) [@Isti6github](https://dietpi.com/forum/u/Isti6github)\
**Post date:** [3 May 2023 08:32 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/14 "2023-05-03T08:32:15Z")

</div>

> [@Joulinar](#):
>
> usually this should not be needed if you activate redirect from 80 to 443.

I didn’t activate redirect, yet.

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [3 May 2023 08:50 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/15 "2023-05-03T08:50:47Z")

</div>

> [@Isti6github](#):
>
> I didn’t activate redirect, yet.

Something I recommend if you plan to access your system from extern, to ensure people get redirect to https 🙂

---

<div class="post-metadata">

**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\
**Post date:** [3 May 2023 23:01 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/16 "2023-05-03T23:01:25Z")

</div>

> [@Isti6github](#):
>
> I added the html2 to port80

It is “http2”, about the [HTTP](https://wikipedia.org/wiki/HTTP) (transport protocol), not the [HTML](https://wikipedia.org/wiki/HTML) (website document language) 😉.

And HTTP/2 is supported with HTTPS only, so adding it to port 80 at best is ignored or may break plain HTTP access. It is hence intentionally not part of the guide.

I wonder why Certbot is not adding it, or whether it can be forced to do so 🤔.

Oh wow, such a trivial task, requested since 2016 but not added until today: [HTTP2 support in Nginx plugin · Issue #3646 · certbot/certbot · GitHub](https://github.com/certbot/certbot/issues/3646)  
There is even a PR open since 2019 to add it as option, sadly it is incomplete: [Add HTTP2 Support by TheBrokenRail · Pull Request #7113 · certbot/certbot · GitHub](https://github.com/certbot/certbot/pull/7113)  
I think I’ll open a PR to just enable it by default. Zero reasons to not enable HTTP/2 on any webserver nowadays as of course it is backwards compatible.

And of course we can do that in `dietpi-letsencrypt` until then.

---

<div class="post-metadata">

**Author:** ![Isti6github](https://dietpi.com/forum/user_avatar/dietpi.com/isti6github/32/3650_2.png) [@Isti6github](https://dietpi.com/forum/u/Isti6github)\
**Post date:** [4 May 2023 10:28 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/17 "2023-05-04T10:28:10Z")

</div>

This is a very good idea, and its can speed up some app too 😊

---

<div class="post-metadata">

**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\
**Post date:** [4 May 2023 21:20 UTC](https://dietpi.com/forum/t/nextcloud-memories-http-2-or-http-3-is-strongly-recommended-http-1-1-detected-nginx/16753/18 "2023-05-04T21:20:04Z")

</div>

Done: [v8.17 · MichaIng/DietPi@b5d3eb7 · GitHub](https://github.com/MichaIng/DietPi/commit/b5d3eb7)
