Results 1 to 7 of 7
Hello everyone. I seem to be having a problem with Apache2 in Ubuntu Server 10.04lts. To start with, here is some basic info. I have a barebones install of ubuntu ...
- 09-12-2010 #1Just Joined!
- Join Date
- Sep 2010
- Posts
- 4
Need help with Apache2 in Ubuntu Server 10.04 LTS
Hello everyone. I seem to be having a problem with Apache2 in Ubuntu Server 10.04lts. To start with, here is some basic info. I have a barebones install of ubuntu server configured with Open SSH (which I do my work from), Apache2 and Proftpd. I have a DYNAMIC IP ADDRESS (this isn't going to change so please take this as a condition that the problem must be solved with) and I'm using DYNDNS to keep track of the IP. I can connect to the dyndns address (lumberjackcomputers.dyndns.org), the global ip address, and the local ip address from inside of my network. I have a local static ip for the server of 192.168.1.100 with DMZ enabled for the address on the router. However, when trying to connect via proxy to see if I can connect outside of my network, it fails. I'm a bit inexperienced with Apache2, so any help here would be great. I really need to be able to SSH in and also connect to the page from outside of my network, as I'm on the go quite a bit. Thanks!
- 09-12-2010 #2
Go to Shields Up and make sure port 80 is not blocked by your ISP. If it is use the workaround offered by dyndns.
- 09-12-2010 #3Just Joined!
- Join Date
- Sep 2010
- Posts
- 4
----------------------------------------------------------------------
GRC Port Authority Report created on UTC: 2010-09-12 at 23:21:23
Results from scan of ports: 0-1055
2 Ports Open
181 Ports Closed
873 Ports Stealth
---------------------
1056 Ports Tested
Ports found to be OPEN were: 21, 22
Ports found to be CLOSED were: 0, 1, 2, 3, 4, 5, 6, 8, 9, 10,
11, 12, 13, 14, 15, 16, 17, 18,
20, 23, 24, 26, 27, 28, 29, 30,
31, 32, 33, 34, 35, 36, 37, 38,
39, 40, 41, 42, 43, 44, 45, 46,
47, 48, 49, 50, 51, 52, 53, 54,
55, 56, 57, 58, 59, 60, 61, 62,
63, 64, 65, 66, 67, 68, 69, 70,
71, 72, 73, 74, 75, 76, 77, 78,
79, 81, 82, 83, 84, 85, 86, 87,
88, 89, 90, 91, 92, 93, 94, 95,
96, 97, 98, 99, 100, 101, 102,
103, 104, 105, 106, 107, 108,
109, 110, 111, 112, 113, 114,
115, 116, 117, 118, 119, 120,
121, 122, 123, 124, 125, 126,
127, 128, 129, 130, 131, 132,
133, 134, 140, 141, 142, 143,
144, 145, 146, 147, 148, 149,
150, 151, 152, 153, 154, 155,
156, 157, 158, 159, 160, 161,
162, 163, 164, 165, 166, 167,
168, 169, 170, 171, 172, 173,
174, 175, 176, 177, 178, 179,
180, 181, 182, 183, 184, 185,
186, 187, 188, 189, 190, 191
so basically I'm stuck with either port 21 or 22? This doesn't make any since, as I use other ports on my windows machine all the time!
- 09-12-2010 #4Just Joined!
- Join Date
- Sep 2010
- Posts
- 4
i used the laptop that I run ssh off of for the test. Is that okay? Also, I really don't know which option I was supposed to choose, lol
- 09-12-2010 #5
You should understand Shields-Up shows you ports that are closed or stealth for incoming connections. Has nothing to do with connections which are initiated from inside.
Ports that are stealth are blocked by your ISP or your firewall.
Ports that are closed are not blocked but no service is listening.
Ports that are open can be connected to, 21 and 22 indicate your FTP and SSH servers are listening.
- 09-13-2010 #6Just Joined!
- Join Date
- Sep 2010
- Posts
- 4
Okay thanks for the info. My question still remains (im a noob, lol). How do i configure the server so I can accept incoming connections?
- 09-13-2010 #7If we hit that bullseye, the rest of the dominoes will fall like a house of cards. Checkmate! (Zapp Brannigan)
My new blog. It's probably not as good as I think it is.


Reply With Quote
