# Can't access site after installation
**URL:** https://meta.discourse.org/t/cant-access-site-after-installation/42200
**Category:** Self-hosting
**Created:** [April 7, 2016, 8:46pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200 "2016-04-07T20:46:53Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@Kyle\_C](https://meta.discourse.org/u/Kyle_C)
#### Post date: [April 7, 2016, 8:46pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200/1 "2016-04-07T20:46:53Z")
I installed Discourse per the instructions on github on a box with Ubuntu 15.04. Everything executed successfully however I did not purchase a domain name so I put my IP in the hostname field. Even after getting a success message when running “/.launcher start app” the IP refuses my connection. I’m worndering if it is okay for me to have used my IP as the hostname or if it must be different? I am perfectly happy with navigating to an IP rather than domain name.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 12, 2016, 12:10pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200/2 "2016-04-12T12:10:01Z")
Did you get this figured out?
If you’re getting a connection refused message then it’s more likely a problem with the port not being accessible from wherever you are.
You could check from a command line with
```
telnet ipnumber 80
```
If it works from the but not elsewhere it’s a problem with port mapping and firewall stuff.
---
### Author:  [@Kyle\_C](https://meta.discourse.org/u/Kyle_C)
#### Post date: [April 12, 2016, 6:25pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200/3 "2016-04-12T18:25:38Z")
When I run that I get:
root@ITRGAVAPOC011:~# telnet ipnumber 80
telnet: could not resolve ipnumber/80: No address associated with hostname
When bootstrapping/installing via Docker does it not bind to the port
automatically?
---
### Author:  [@frictionel](https://meta.discourse.org/u/frictionel)
#### Post date: [April 12, 2016, 6:41pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200/4 "2016-04-12T18:41:25Z")
> [@Kyle\_C](#):
>
> root@ITRGAVAPOC011:~# telnet ipnumber 80telnet: could not resolve ipnumber/80: No address associated with hostname
It looks like you didn’t replace `ipnumber` with the actual IP-number of your discourse install. 😉
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 12, 2016, 6:48pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200/5 "2016-04-12T18:48:33Z")
And if it “works” it’ll look like nothing is happening. You can then type
```
get /
```
And see some stuff that likely looks like gibberish. Then you’ll need to know that control-[ and then q enter will quit telnet. I think that’s it.
---
### Author:  [@Kyle\_C](https://meta.discourse.org/u/Kyle_C)
#### Post date: [April 12, 2016, 7:00pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200/6 "2016-04-12T19:00:05Z")
So I tried it with the actual IP and no luck, connection refused. Tried looking at IP tables but don’t see any blocking rules. (blocked out my domain). Would I need to create a new rule to allow port 80 specifically?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 12, 2016, 7:34pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200/7 "2016-04-12T19:34:34Z")
You can try
```
netstat -atn
```
To check for open ports.
Maybe you didn’t expose the port in the config file?
---
### Author:  [@Kyle\_C](https://meta.discourse.org/u/Kyle_C)
#### Post date: [April 12, 2016, 8:25pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200/8 "2016-04-12T20:25:15Z")
Is there a separate config file just for Discourse to set up the ports?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 12, 2016, 8:43pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200/9 "2016-04-12T20:43:47Z")
Did you follow these instructions?
> **[Install Discourse in Under 30 Minutes](https://blog.discourse.org/2014/04/install-discourse-in-under-30-minutes/)**
>
> A few key things came together recently:
---
### Author:  [@Kyle\_C](https://meta.discourse.org/u/Kyle_C)
#### Post date: [April 12, 2016, 9:19pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200/10 "2016-04-12T21:19:08Z")
I did, I’m wondering if it’s because I installed in a corporate lab setting. I did have to add proxies to the app.yml file to be able to reach out to the internet and install. Might be tied to that somehow.
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [April 14, 2016, 8:35pm UTC](https://meta.discourse.org/t/cant-access-site-after-installation/42200/11 "2016-04-14T20:35:05Z")
Yep, the proxies are probably what’s going on. The installation is properly listening on 80/443, but the outside world can’t get that far.