j12t wrote: ↑
Tue Apr 02, 2019 12:49 am
If you go for self-signed, whether you use Pagekite or not should make no difference. Your visitors will see a browser warning, however (because it is self-signed). Keep in mind, however, if you go through "createsite" that you will end up with a second site running a second instance of Nextcloud.
There isn't currently a dead-simple way of adding SSL after the fact; the easiest would be to add the tls / letsencrypt entry to your existing Site JSON.
Thanks for your help..... Unfortunately, I fear that this is starting to turn into a potential disaster for me.
I followed the instructions shown at https://ubos.net/docs/users/create-ssl-site.html
using the "self-signed certificate" instructions.
I didn't know what to use for the hostname question, and I couldn't find any documentation that provided any guidance, so I just made up one called "ubosbox". Was that bad? It would not allow me to use * as the response to the hostname question for some reason.
Then, when it asked for an "app" to install, I didn't know exactly what it was looking for, I assumed
that I should install nextcloud, so I entered "nextcloud". But then I got the mysterious error message you see in the attached screenshot. It suggested I run pacman-db-upgrade, but I did not, I did not know if that is something I should do. Should I?
So, I did not install any app.
Now, through my pagekite url, I can still access my nextcloud server, but it does NOT use the https protocol, it is still the http protocol. So for some reason this is not working.
So, I am very, very confused on what I should be doing. What have I done? Do I need to undo something I have done? (If so, how do I do that?) What should I be doing to use the https protocol at this point?