Questions setting up HTTPS for self-hosted server

Hi all,

I recently built out some web infrastructure for a small company, which is hosted on an on-prem server. The server has a linux VM with Xampp (apache) and uses port-forwarding to route the domain and sub-domains to the various sites and services built.

For the ecommerce site to accept payments through stripe we need to make the site run HTTPS with a cert. Currently we use Dyn for DNS service, so the ecommerce site can be publicly accessed even now at or the Dyn domain ( I am wondering how to go about setting up this cert chain, how to get certs for this stack, and how to make sure it works with our top-level domain provider.

iPage is the top-level domain provider for

Basically, we can either make HTTPS work with our current setup that relies on Dyn and port-forwarding which seems unlikely, or we can get rid of Dyn and port-forwarding and somehow have the top-level domain point straight to my apache virtualhost. this would simplify the cert chain.

Tell me what to do, ask any question. Help is appreciated so that this small business can start making sales through ecommerce.


Hi @GelLiNN

your setup can't work ( ):

These are your public visible ip addresses:

Host T IP-Address is auth. ∑ Queries ∑ Timeout A yes 1 0
AAAA yes A yes 1 0
AAAA yes


Domainname Http-Status redirect Sec. G 200 0.220 H 200 0.207 H 200 1.290 I 200 1.030 I 404 0.210 A
Not Found
Visible Content: 404 0.214 A
Not Found
Visible Content:

looks - first watch - good. But there is a frame


</HEAD><FRAMESET border='0' ROWS='*,1'> <FRAME SRC=''><FRAME SRC='blank.html'> </FRAMESET> </html>

so there is no content.

You can use dns-01 validation to create a certificate, then you don't need a running webserver. But with that setup you can't use http-01 validation.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.