Iāve this :
root@debian:/home/p-e# snap set nextcloud.enable-https letsencrypt
error: invalid configuration: āletsencryptā (want key=value)
root@debian:/home/p-e# snap set nextcloud.enable-https
error: the required argument <conf value> (at least 1 argument) was not provided
ec2-user@:~$ sudo nextcloud.enable-https -h
Usage:
nextcloud.enable-https -h
Display this help message.
nextcloud.enable-https <subcommand> [OPTIONS]
Run the provided subcommand.
Available subcommands:
lets-encrypt [OPTIONS]
Obtain a certificate from Let's Encrypt and automatically keep it
up-to-date.
self-signed
Generate and use a self-signed certificate. This is easier to
setup than Let's Encrypt certificates, but will cause warnings in
browsers.
custom [OPTIONS]
Use certificates generated by other means.
if there is no /snap/bin/nextcloud.enable-https there is something wrong with your machine.
or /snap/bin is missing in $PATH (checked with echo $PATH)
root@ip-172-31-52-96:~# which nextcloud.enable-https
/snap/bin/nextcloud.enable-https
root@ip-172-31-52-96:~# nextcloud.enable-https lets-encrypt
In order for Let's Encrypt to verify that you actually own the
domain(s) for which you're requesting a certificate, there are a
number of requirements of which you need to be aware:
1. In order to register with the Let's Encrypt ACME server, you must
agree to the currently-in-effect Subscriber Agreement located
here:
https://letsencrypt.org/repository/
By continuing to use this tool you agree to these terms. Please
cancel now if otherwise.
2. You must have the domain name(s) for which you want certificates
pointing at the external IP address of this machine.
3. Both ports 80 and 443 on the external IP address of this machine
must point to this machine (e.g. port forwarding might need to be
setup on your router).
Have you met these requirements? (y/n) nextcloud.enable-https
Now for the HTTPS, itās good, but in my server, what about the encryption ? How can i protect my files server sided and how can i access to them if they are encrypted ?
Thanks
that question goes to the snap programmers.
itās added normally here:
/etc/profile.d/apps-bin-path.sh:# Expand $PATH to include the directory where snappy applications go.
/etc/profile.d/apps-bin-path.sh:if [ -n "${PATH##*${snap_bin_path}}" -a -n "${PATH##*${snap_bin_path}:*}" ]; then
/etc/profile.d/apps-bin-path.sh: export PATH=$PATH:${snap_bin_path}
you can add it by putting export PATH=$PATH:/snap/bin at the end of /etc/environment