# Ports 443/80 show as closed after installation

**URL:** <https://meta.discourse.org/t/ports-443-80-show-as-closed-after-installation/304600>\
**Category:** Self-hosting\
**Created:** [April 19, 2024, 10:06am UTC](https://meta.discourse.org/t/ports-443-80-show-as-closed-after-installation/304600 "2024-04-19T10:06:02Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [April 20, 2024, 9:05am UTC](https://meta.discourse.org/t/ports-443-80-show-as-closed-after-installation/304600/5 "2024-04-20T09:05:13Z")

</div>

> [@Marek\_Wojtaszek](#):
>
> the forum site won’t open saying that the service is not accessible

I think it’s true that Discourse only works when accessed through a domain, so do you have a setup whereby you can access your site using a browser and a domain? If you are entirely local to your own LAN you can perhaps do that with a hosts file, but I’m not sure. I think both the server and the client (and perhaps also the docker) need to be able to do a name lookup.

---

_[View the full topic](https://meta.discourse.org/t/ports-443-80-show-as-closed-after-installation/304600)._