Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 30 days old, your post is exempt from this rule as long as you continue to engage in comments.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Hi. Thank you so much for this detailed response. I ran the dig commands you suggested, and they all show the correct IP. Njalla allows you to change the TTL, so I set that to 0s when I created the A record. So the problem must be with my routing or my web server, as you said. How can I troubleshoot those?
Sounds good.
Hmm next you probably should confirm ports 80 and 443 are actually reachable from the internet.
Use an online port checker like https://canyouseeme.org/
After that you should check your apache config like somebody else already suggested. I haven't used apache in a while but if I remember correctly:
Ensure it says: Listen 80 NOT: Listen 127.0.0.1:80
(and same with 443)
Also check your VirtualHost — it should look something like:
(and same with 443)
Okay, great. So I checked all the config files, and everything seems to be in order there. But when I used an online port checker (I used yougetsignal.com), it said ports 80 and 443 are both closed. So the problem must be with my router, right?
The problem could be anywhere in between the internet and your server.
Ofc. it could be your routet. But I think the following is more likely:
It might also be your internet service provider that doesn't allow those ports for inbound connections.
Or you're behind a CGNAT so your real external ip is different from the one you think it is. (look up online how to test this)
That was it! I was behind a CGNAT! Thank you so much. I created a Cloudflare tunnel, and boom. I am now able to access the domain from my phone without wifi. Thank you, thank you, thank you. I still have some configuration to do, but the main issue has been resolved. You are an angel.