Is https protocol necessary for private clouds?

Hello everybody !

If you set up a private home cloud which is accessible only through your local network (wi-fi and cable) and it’s not open to the internet and not accessible from outside, is it necessary set up the https protocol or not ?

If you don’t use SSL, others inside your local network can sniff on your traffic. And if you connect to a local ip, and e.g. with your smartphone you in a different wifi, it tries to connect to your server (and hacker could set up a device that acts like a Nextcloud server).

In a local network, it is a bit more difficult with certificates, hostnames, etc (you can use local DNS, with a public domain name, you can get letsencrypt certs and authenticate through dns, or use self-signed ones).

If I wanted to test Nextcloud in my local network, and would just like to check the working of the clients, interfaces etc, I would probably not bother to set up SSL. For everything else, I probably would. And if you move it later to a setup accessible from everywhere, you must have SSL.

Ok, so how to configure a self-signed certification ?

Can you suggest me a good tutorial for that please ?

Here is a short advertisement on my own behalf (hopefully it won’t be deleted :wink:):

We have created a guide for SSL creation. Have a look at it:
Making NextCloud accessible from the Internet and an SSL certificate or https for our cloud and other web installations • Schächner (xn–

If you are looking for general information, here is some more:

Basically, you can always do SSL for free via Certbot.
There is also a good guide to this on the Certbot website.

Please note, however, that you need a domain for this (SSL without a domain will be difficult…)
However, I would definitely recommend a domain; there will certainly come a time when you need/want to access your files remotely or share them with other people (friends/family/work colleagues).

Hopefully I was able to help you,

You don’t have to buy a domain either - there are also various free providers such as No-IP.

DevOpsCube have a decent tutorial post how to generate self-signed certificates with OpenSSL.

It is a bit of a hassle at first, but it is not a rocket science.

Hi everybody !

Thank you very much for your help and sorry for my late response. :bowing_man:

What I have found easy for me about secure Nextcloud through https protocol are:

  1. this video (but not the entire video) about how to install Nginx Proxy Manager on CasaOS:

  2. this video about how to configure Nginx Proxy Manager and how to make it works:

About the second video there’s a problem (at around 10:03), because when I tried to configured the second service connected to Nextcloud and its subdomain like in the video is done, just it doesn’t work.

I’ve tried many things, even putting the exactly IP address and forward port, but nothing.

The best result I got has been: a long time of loading with a blue screen and then 504 Gateway Time-out.

How to fix it ?

I use CasaOS by the way.

Little update after different things:

  • Disabling the firewall, it gave the 502 Bad Gateway

  • Enabling the firewall, it gave the 504 Gateway Time-out

How to fix that, please ?

Update: looks like the problem is solved.

There was a problem with the port of the firewall who needed to not be blocked.

And it was necessary change something on Nginx Proxy Manager
Scheme: http (instead of https)
Forward Hostname: the real IP of the machine with the correct port

After that: the page was loaded in https

Had some problems. Just be careful with permissions of folders where Nextcloud and Nginx are located

Thank you anyway :bowing_man:

1 Like

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.