All websites when accessed using http show a default Apache2 webpage.
In CyberPanel, list websites also shows thumbnails of default Apache2 webpage.
Letsencrypt is failing because of above - fails http challenge.
https access shows correct site although the certificates are not secure.
Any suggestions for what causes ALL http requests to go to this default page?
Lets encrypt will issue a certificate only when the domain points to your IP address, otherwise it will issue a self-signed certificate.
Point the A-record of your domain to your ip address (or www if using it, or both). Wait till propagation is finished. Then issue SSL again from cyberpanel for your domain name.
@kowalski215 Thanks for the help. The A records are fine, https (using self-signed) is working. The problem is http access always goes to an Apache2 page which does NOT belong to the domain.
When letsencrypt stores its files for negotiation it does put them into the correct folder but http access cannot find them because it goes to the wrong place.
Can a little bit more direction be given on this? Isn’t Apache installed with Ubuntu by default? Why is it conflicting with Cyberpanel? I followed this advice (I uninstalled apache2) and now Power DNS is not working. For me, removing apache broke it even further.
Wrong. Unless your provider offers you an ubuntu server version with apache installed. You should have a clean install of Ubuntu os.Kindly uninstall all preinstalled software that may conflict with CyberPanel installation such as powerdns, ftp, apache2, mariadb/mysql. OR purchase an ubuntu server with none of the aforementioned software installe.d
Ok, I am figuring this out. I did purchase a clean VPS and installed everything from scratch. Apache was in there I’m sure as part of the process or instructions I was reading at the time.
You did mention Power DNS - I am wondering why this is in my Cyberpanel dashboard? [under manage services → service status] You can turn it on or off, but shouldn’t it be on? My sites are working perfect with it being off so maybe I should leave well-enough alone? I would like to know what it does though.
PowerDNS is running its a panel bug. You can restart lscpd service restart lscpd
PowerDNS manages our DNS with ways to provision zones records. All the features you see about creating domains, websites, default nameservers is powered by PowerDNS. Hell cloudflare instrastructure runs on PowerDNS
I don’t know why mine is showing it’s off. Of course my sites are all working - and I am using cloudflare to do all the heavy DNS work so that seems to be (after beating head against wall) the best combination! I was trying to direct my domain previously (directly to the VPS) using my defined ns1/ns2.atalantamail.com, and that allowed the control panel and all backend functions to work. I was excited beyond belief how smooth this interface is. But then I tried to create a site with www.atalantamail.com and this did not work. I ended up putting the domain on cloudflare, now it works beautiful - I think a lot more is done (glue records?) with cloudflare DNS. And now I must access the dashboard with [IP]:8090 rather than [domain]:8090 but who cares about that?! (not me)