I am not entirely sure how to continue at the moment, as I have a site set up, but it does not appear to be working except through the alias or the IP address. The original IP worked until I used certbot to install the certificate, at which point the website just times out when I try to access it, this includes after I uninstalled and purged apache2 and certbot then reinstalled only apache2.
You are repeating yourself.
Let me do the same:
Yes, I know, that is the only domain name I need covered, and is the only domain name that no longer functions. The issue is not that I need more names secured, but that the one that is secured can no longer be connected to. If you would like to secure the alias (host.rpgrat.org) as a test run I am more than willing to do that, but I think there is a misunderstanding currently, I am not sure if it is on my part though, sorry.
hmm...
What does your browser screen show for?:
https://rpgrat.org/
Did you open 334 or 443?
[HTTPS = port 443]
I have tested on chrome and firefox, it just shows that it timed out after attempting to load the page for several seconds.
Port 443 is open in addition to 80, I mistyped earlier, sorry.
What shows?:
sudo ufw status
Status: active
To Action From
-- ------ ----
22/tcp ALLOW Anywhere
Apache Full ALLOW Anywhere
OpenSSH ALLOW Anywhere
32000 ALLOW Anywhere
32001 ALLOW Anywhere
32002 ALLOW Anywhere
32003 ALLOW Anywhere
32004 ALLOW Anywhere
32005 ALLOW Anywhere
25565 ALLOW Anywhere
80/tcp ALLOW Anywhere
443 ALLOW Anywhere
22/tcp (v6) ALLOW Anywhere (v6)
Apache Full (v6) ALLOW Anywhere (v6)
OpenSSH (v6) ALLOW Anywhere (v6)
32000 (v6) ALLOW Anywhere (v6)
32001 (v6) ALLOW Anywhere (v6)
32002 (v6) ALLOW Anywhere (v6)
32003 (v6) ALLOW Anywhere (v6)
32004 (v6) ALLOW Anywhere (v6)
32005 (v6) ALLOW Anywhere (v6)
25565 (v6) ALLOW Anywhere (v6)
80/tcp (v6) ALLOW Anywhere (v6)
443 (v6) ALLOW Anywhere (v6)
It is dangerous to leave these open to the entire Internet:
Please post a picture of the port forwarding.
I am currently not on the same network as the server, and am not sure how to remotely access the port forwards, but I am confident that the correct ports are in fact open. I have been meaning to secure OpenSSH for a while now but have not gotten around to it, but now that you mention it I probably should do that sooner rather than later. I can try to get someone on the network to send me a screenshot, but that could take a while.
Take your time.
My bet is that the port forwarding [for port 443] isn't going to the IP of your server.
[the port 443 forward IP setting should match the port 80 forward IP setting]
If you were in the internal network, could you SSH to the router/NAT device?
If so, then just SSH to your server.
And then from that SSH to the router.
[just a hop skip and a jump away]
It seems only Port 80 is Open to the general public Internet.
I am not sure, I have done a tiny bit of testing on that front and there is probably a way to, I am just not sure how. It is a Comcast business router, with the standard gateway address (10.1.10.1 I believe). if there is an easy way to do this that I have just missed I am not sure where all the documentation is.
You probably have to control that router via HTTP(S) - NOT SSH.
Best to wait for someone onsite and more knowledgeable about it.
Yeah, I believe you're right. Is there any way to access the admin panel through the command line via HTTP? I know I can just curl the gateway, but that's not particularly useful as curl does not exactly have a UI, and there isn't an API that I know of.
Here’s an online tool to assist in checking what Ports are Open from an external view.
Open Port Check Tool - Test Port Forwarding on Your Router
Alright, progress, I checked and 443 is indeed closed according to that tool, thank you! I just got in contact with someone on site and am working with them now to open that. Does this seem consistent with what has been happening? It just seems strange that this problem would only come up now that I tried to use certbot.