i’ve got the exact same problem
i’ve got a crashtest ubuntu 20.04 server (freshly installed … and often reinstalled …!) to try hestia v164 in different ways (i’m no IT) in which i kept the panel domain in the admin (though you told me it’s better in a user account, but it’s just for testing here)
i have CF cerf origin copied & pasted in HESTIA configuration menu, but when I save, it disappears. but that’s not all folk’s:
: hestia’s domain end up with a let’s encrypt cerf and i don’t get any error visiting the domain with different browsers at panel.domain.org:2083 but none would display panel.domain.org …
(it’s said that :8083 is not accepted by cloudflare, in confirm)
in WEB section in HESTIA
SSL is not even activated on the domain panel.domain.org
I’d truly be happy to understand my situation if one can help
cause it’s giving me a very hard time trying to understand what to do to have a simple and clean server working with hestia and cloudflare. i get gateaways, 403s, https not secured even with a cerf in hestia, younameit, well… all sorts of messages grinding my peace of mind ^^
I’ve read people have nice servers running with hestia, nextcoud … so far … i’m not there … yet - but i can’t understand why, cause i’m following the exact simple steps of different tutorials, documentation files, …
now, i want to ask you @falzo, what you mean by:
however after you did this you still need to tell hestia to pick it up for itself. you can do this from the console via the v-update-host-certificate command.
pick it up? copy paste is not enough?
v-update-host-certificate command would do what?
nothing in hestia’s doc, see …
where are the cerfs in the server by the way?
thanks at all responders