So I just got Cyberpanel setup for the first time. I decided that I wanted to access Cyberpanel via domain rather than IP, so I created a website for it at panel.MYDOMAIN.com
I created an A record with my registrar (which is still managing the nameservers for now) of panel and set it equal to my server IP address
I then used cyberpanel to issue a hostname SSL for installation: panel.MYDOMAIN.com
I got the greenlight that the SSL was issued for the domain.
Now when I try to access cyberpanel via hostname: https://panel.MYDOMAIN.com:8090 my site/installation of cyberpanel is found, but the browser reports that location isn’t secure, and I have to go through the whole “your connection isn’t private” advanced approval stuff.
Well, I didn’t make any changes, and it’s working now. So I guess I managed to do it correctly after all. My guess is that it was either a propagation or caching issue on my desktop.
I might setup another one later just to confirm that I actually know what I’m doing and didn’t just get lucky. But whether it was luck or skill, it seems to be working as I intended now. So, I’ve got a lot of work to do getting everything moved over to my new server before I go testing and tinkering.
@jaceman - I am glad you got it sorted! Sometimes that is an issue, I usually use a 4G connection to quickly validate changes when it may be cached on the PC or network level.
I’ve got the same problem before:
Make sure the DNS has already been resolved and pointing to your server. Check it with whatsmydns.net. Only after that you generate the SSL
If above step didn’t work, mostly it’s because of your cache. Try to disable your browser cache and open it again.