wraith
@wraith@lemmy.ca
- Comment on Self hosting and HSTS preload domains 4 days ago:
I haven’t set up the VPN yet. I am getting as much info as I can before I start any work. For the sake of this discussion, it would be a box on my network.
- Comment on Self hosting and HSTS preload domains 4 days ago:
So I should just host it with an IP address instead of using the domain?
I hadn’t thought to do that, at least not for anything other than short lived internal-network-only projects and tests. An IT guy in the company I work for advised me to just get a domain and host with it/subdomains to make it easier to manage if I wanted to host multiple services.
- Comment on Self hosting and HSTS preload domains 4 days ago:
I will need it to be available via a VPN or other means, but it’s not going to be any more public-facing than it has to be.
- Comment on Self hosting and HSTS preload domains 4 days ago:
I think you meant to reply to me! I actually do need it to be accessible externally, via a VPN or other means.
- Comment on Self hosting and HSTS preload domains 4 days ago:
I am fairly new to self hosting and just wanted to know if this was a big enough deal that I should just get a domain that doesn’t require HSTS preload. It’s one thing to tinker with an IP address on a local network for some unimportant project; it’s just intimidating to try it for real using a domain and hosting my own data.
I’m just a little nervous tbh. Thanks for the help!
- Comment on Self hosting and HSTS preload domains 4 days ago:
Google requires HSTS preload for all of their domains. Charleston Road Registry (their subsidiary), enforces this by adding the TLD to the HSTS preload list.
- Comment on Self hosting and HSTS preload domains 4 days ago:
Google is the registry. They require all of the domains they control to have HSTS preload enabled.
- Submitted 4 days ago to selfhosted@lemmy.world | 22 comments