Welcome, Guest. Please login or register.
Did you miss your activation email?
Saturday 23 November 2024, 04:50:30 pm

Login with username, password and session length

CLICK HERE for the The official Endian Roadmap and Issue tracker
14258 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  Installation Support
| | |-+  Cannot Access My Webserver
0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Cannot Access My Webserver  (Read 22179 times)
AussieBloke
Full Member
***
Offline Offline

Gender: Male
Posts: 37



« on: Sunday 26 February 2012, 09:52:15 pm »

I have just installed a fresh version of 2.5.1. Now I cannot access my webserver using the external domain name. eg: mydomain.com

This is the configuation I used on 2.4.1

----------

Uplink ANY    TCP+UDP/80    ALLOW    172.17.1.51 : 80
ALLOW from:    <ANY>

----------

I can access it from an external connection, but not an internal connection.

Endian replies with

--------------------------
he requested URL could not be retrieved
While trying to retrieve the URL: http://www.mydomain.com/

The following error was encountered:

Connection Failed

The system returned:
(110) Connection timed out

The remote host or network may be down. Please try the request again.

Your cache administrator is webmaster.

--------------------------------------------

I can access external websites but not my own.
Logged
Janis B
Jr. Member
*
Offline Offline

Gender: Male
Posts: 4


« Reply #1 on: Thursday 01 March 2012, 07:55:09 am »

You should check what your dns name is resolved to when you try to access it from internal connection and what ip it is resolved to on firewall. If you have enabled proxy on the firewall you should make sure that dns is either resolved to external ip or forwarded to internal ip directly.
Logged
AussieBloke
Full Member
***
Offline Offline

Gender: Male
Posts: 37



« Reply #2 on: Thursday 01 March 2012, 11:54:49 am »

The dns resolves correctly, so it is not a dns issue.
Logged
Janis B
Jr. Member
*
Offline Offline

Gender: Male
Posts: 4


« Reply #3 on: Friday 02 March 2012, 08:51:36 am »

Have you tried to turn of proxy server and see what happens?
Logged
AussieBloke
Full Member
***
Offline Offline

Gender: Male
Posts: 37



« Reply #4 on: Monday 12 March 2012, 02:52:22 pm »

Turning the poxy off does not fix the problem. It should work with the proxy on, it always did in the past.
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.078 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com