# Windows Server 2019 / Hyper-V
**URL:** https://meta.discourse.org/t/windows-server-2019-hyper-v/187228
**Category:** Support
**Created:** [April 17, 2021, 8:47pm UTC](https://meta.discourse.org/t/windows-server-2019-hyper-v/187228 "2021-04-17T20:47:27Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Natsu1](https://meta.discourse.org/u/Natsu1)
#### Post date: [April 17, 2021, 8:47pm UTC](https://meta.discourse.org/t/windows-server-2019-hyper-v/187228/1 "2021-04-17T20:47:27Z")
Hi there,
I just installed Hyper-v With ubuntu 18.04 and installed Discourse on it. ( [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md) )
The Ubuntu server has a static ip given by my router + port forward port 443 from there and pointed my domain to is.The instillation worked if i try to call the command “./launcher start app” it says that discourse is running correctly. But i cannot access it on my domain. It does say under ports : 0.0.0.0:443 should this be my internal ip of the machine?
if so how to fix it?
Thanks in advance.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 18, 2021, 2:09am UTC](https://meta.discourse.org/t/windows-server-2019-hyper-v/187228/2 "2021-04-18T02:09:09Z")
It needs a domain name, not an ip. It also needs to be publicly accessible for let’s encrypt to work, and requires extra steps to disable let’s encrypt.
---
### Author:  [@Natsu1](https://meta.discourse.org/u/Natsu1)
#### Post date: [April 18, 2021, 7:41am UTC](https://meta.discourse.org/t/windows-server-2019-hyper-v/187228/3 "2021-04-18T07:41:30Z")
it has a domain name : forum.blueskull.win
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 18, 2021, 12:03pm UTC](https://meta.discourse.org/t/windows-server-2019-hyper-v/187228/4 "2021-04-18T12:03:54Z")
You need to make sure that incoming traffic to ports 80 and 443 gets to the server.
Did you run discourse-setup? It tests to see that incoming traffic can get to the server (but can’t work if you have a reverse proxy)
---
### Author:  [@Natsu1](https://meta.discourse.org/u/Natsu1)
#### Post date: [April 18, 2021, 3:14pm UTC](https://meta.discourse.org/t/windows-server-2019-hyper-v/187228/5 "2021-04-18T15:14:29Z")
Yes i ran
./discourse-setup
and it did connect fine that’s why i am wondering why it does not work now
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 18, 2021, 5:42pm UTC](https://meta.discourse.org/t/windows-server-2019-hyper-v/187228/6 "2021-04-18T17:42:59Z")
Perhaps your server machine uses a different dns than your client. Getting that stuff working between all the layers of your router, the server os, the visualized vm and so on is tricky. It’s not likely that you’ll get that level of troubleshooting here.
That’s why it’s easier to spend $5 or $10 /month to digital ocean.